Firebase Crashlytics vs. Singular

Crashlytics is almost a defacto standard in the Android world for tracking crashes in the field. I've used it on the last 4 Android projects I've been on. It's not as helpful on iOS' stacktraces but I'm not sure if anything would be better because iOS stack traces are from ObjC code which is not as useful as Java stacktraces.

Incentivized

Singular is perfect for companies that have limited BI developer resources. If you work with more than a few media partners, Singular aggregates all pre-install metrics and automatically connects it to your BI data / MMP provider. This use is perfect for executives/directors that want to have a quick snapshot of their marketing spend. Singular also works well for media buyers that want to export Singular report as a base for creating optimization reports.

Incentivized

• Can get the device detail an actual state like RAM, Storage, Display Size, etc.
• Can get the class name and line number where crash occur.
• Its work in realtime so we can reduce the time of issue finding and resolution.

• Creative reporting is one of the features of Singular (formerly Apsalar), which I love the most.
• Tracking the user journey right from the click to purchase.

Incentivized

• Sometimes UI of Firebase Crashlytics is quit difficult to understand for new users.
• There can be a proper discretion for all the features that is offered.
• There can be api crash report also.

Incentivized

• Providing a clear solution to cross-device attribution and measurement: no vendor does this well currently.
• Ability to toggle advanced attribution models: first-last touch, time decay, etc.
• Comprehensive deep linking solution (similar to Branch).

Incentivized

Because its fulfilling our basic and necessary requirements that can be an only and enough reason to renew the subscription.

When we report about a bug or a problem the support usually responds quickly and try to provide a solution/fix in a timely manner. I wish that they had a monitoring tool to notify me about bugs before I spot them myself.

Incentivized

As mentioned previously, the only realistic competitor to Crashlytics is Instabug (backed by Y Combinator in the W16 class). While Crashlytics is focused on actual crashes, Instabug's main innovation is in collecting feedback from users for non-crash bugs. While non-crash bugs are a substantial category of bugs, Instabug's pricing is quite steep. As soon as you go beyond the most basic features your monthly bill spikes to $124 - $499 per month, whereas Crashlytics is 100% free (for all usage levels and all enterprise features). Based on this, I've never tried Instabug because the ROI just wasn't there.

Incentivized

As this is my first job after completing my graduation, therefore I do not have any prior experience of working with corporates and organizations. Hence I have only used Singular (formerly Apsalar).

Incentivized

• Allows us to easily share crash data with clients.
• Provides confidence to our developers and project teams by having trust in the data that is being reported.
• Allows us to quickly and efficiently address fatal crashes.

Incentivized

• Reduced time to manage reporting on a daily basis—going from weekly reporting to daily cadence.
• Ability to manage and optimize creative performance, allowing us to test and react to performance quickly.
• Reduced error rate (and therefore troubleshooting) of reporting.

Incentivized