I spent the last few months working on getting iOS Support going in Sentry (sentry.io). Would love to hear feedback. Not only do we provide a hosted solution but it's also 100% Open Source which should give you the confidence that it will continue working for you no matter what happens.
> [...] we expect that Crashlytics will become the main crash reporting offering for Firebase [...]
They will be integrating Crashlytics into their core developer offering, Firebase. Looks like if you are just using Fabric's Crashlytics service you will be ok. But there is more room to worry if you are using some of Fabric's other tools.
We plan to stick with Crashlytics at my company.
[1] https://techcrunch.com/2014/10/21/google-acquires-firebase-t...
[2] https://scotch.io/bar-talk/a-look-at-the-new-firebase-a-powe...
I'm pretty sure that this was the strategic thinking when started to invest to app developer tools (Crashlytics, Fabric, Digits, MoPub). It's interesting to speculate why they are selling Fabric, is their business model focus moving away from mobile ads?
I don't think Fabric was ever used for Twitter ad targeting just by reading their TOS unlike the Google/FB world and their analytics products but I could be wrong. Seems like a case where Twitter didn't realize the full potential of Crashlytics and Answers.
As an alternative, suggesting Countly (open source) - http://github.com/countly/countly-server - with crash reporting, push notifications and analytics.
Raygun provides Crash Reporting & Real User Monitoring. Across both mobile, backend and desktop (and all mobile, including Xamarin stacks). Love to have you check it out.
We've been picking up a bunch of customers who have been getting nervous with Twitter being in a bad shape and worrying about Fabric previously.