Embrace has historically been a pretty nifty tool for understanding and reproducing user issues but having pages full of metrics can certainly be daunting for any developer. After all, it's significantly easier to be told what problems exist rather than going on a scavenger hunt for bugs.

The Problem

Outside of network and crash alerting, how do we actively surface issues such that developers don't have to scour through every corner of our dashboard?

Introducing: The Issues Page and Workflow

The approach is two-sided: consolidate issues for developers and create a workflow giving teams full control over new and existing issues. Teams will be able to prioritize issues by instances or affected users, with filters for dates, app version and issue state.

We're hiding the crash groupings but hopefully you get the idea. Not only do we proactively surface issues, developers and PMs now have the ability to Resolve, Snooze and Ignore issues as they occur. For resolved issues that reappear in future versions, Embrace automatically resurfaces the problem so that you don't have to manually reopen it (although we still give you that option). Full details can be found in our docs.

This is especially unique for crashes on iOS. Unlike other crash reporters in the market, we retroactively symbolicate crashes that we received before the dSYM was uploaded. This means that rather than having multiple open issues for the same crash, we're able to provide one consistent grouping.

For now, you'll only see crashes but in the following weeks, we plan on adding support for additional insights around networking, logging and session events. We're continually striving to improve the experience for all the teams we work with and your feedback is incredibly important to us. Let us know what you think!