Get to the bottom of your bug!
May 09, 2016
Get to the bottom of your bug!
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Apteligent
We use Crittercism to help mostly with crash reporting and to analyze our stack traces when there is a crash. It is extremely helpful to use a monitoring tool to check for crashes that could be device specific based on device (iPhone, iPad, etc). It is also helpful to know if a crash was a result of a user not updating to the latest version of the app with bug fixes.
- Crash Reporting
- Network Insights
- Crash Trends
- Pointing to exact line number of the crash
- A more explicit navigation bar (a little confusing for the user)
- Third-party API specific crash reporting (instead of just listing the endpoint)
- Allow us to release iOS versions quicker to the app store
- Help us solve bugs and view bread crumb trails on money-making actions within the API
- Points us to problems in the stack trace with a direct correlation to our route creation aspect in the app
- Twitter Fabric
I use both for different purposes. Twitter Fabric integration was easier for setup purposes and documentation was a lot clearer than Crittercism and geared towards Swift more so than Objective-C. Twitter Fabric is also better with real-time emails pointing to exact line number for a bug. Crittercism is better for bread crumb trails and stack traces to see the user flow and how a problem ending up becoming a problem in the first place.