Observability teams often ask why we don’t show monolithic traces for issues like slow startups. While they theoretically reveal all services involved, they’re hard to interpret, and distract from what’s critical: the mobile experience context.
The Embrace team is attending this year's ObservabilityCon! Join us there, connect with the team, and attend our talk to learn about engineer concerns and the Embrace and Grafana integration.
Embrace's ANR resolution tool now shows engineers a list of ANRs that's near-identical to what the Google Play Console reports. Plus, they can use our industry-leading analytics features to properly resolve these ANRs – for good.
Our recent roundtable with GamesBeat and SuperPlay discusses the intricacies of mobile gaming, the multitudes of player experiences, and the importance of the right tooling for game engineers.
Embrace's new Performance Tracing feature allows mobile engineers to instrument and monitor key flows within their app with a huge level of detail and granularity, empowering them to truly optimize every element of their end user experience.
When crash tagging is combined with GitHub codeowners, engineers can see exactly who owns each line of code within a given stack trace. Here's how mobile teams benefit.
If you're looking to help your mobile team work efficiently, then certain collaboration features are key. Find out which ones to look out for in this post.
Embrace's Mobile Crash Owners feature lets engineers upload their own codeowner rules directly to Embrace. These rules are used to tag any captured crashes with the correct owner, making it quick and easy to identify which issues individual engineers, teams, or organizations are responsible for solving.
