71–80 of 133 posts
Earlier quoted context omitted.
Yeah, that moment of panic when you think something Google acquired is something you use.
In the case of fabric/fabfile this wouldn't matter, as fabric/fabfile looks dead anyway. No Python 3 support, no road map, last Github activity 5 months ago.
I'm happy that Crashlytics will live on, as that was something I was concerned about in light of Twitter's recent poor performance. However, I'm really not looking forward to the eventual Firebase-ifying/Google-ifying of the UI/design. The Firebase/Google Console interfaces are terrible. Just awful. I cringe thinking about what could happen to the Crashlytics UI.
Firebase engineer here -- what don't you like about the Firebase Console? Any specific things that we could improve?
"By default, your Firebase Analytics data will enhance other Firebase features and Google products. You can control how your Firebase Analytics data is shared in your Firebase settings at any time. Link your AdMob app(s) to Firebase and we'll share your data from the free Firebase Analytics tool with AdMob to improve app monetization and user engagement. You understand that this linkage may also allow AdMob Data to be shared with Firebase for enhanced reporting purposes."
I guess it means something like "Link you Admob account to Firebase" but it sounds kind of scary.
Knowing Google's reputation with abandoning developer tools and services, can anyone offer suggestions as to possible alternatives? Or counterpoints as to why I shouldn't fear this service degrading over the next year or two? We're currently using Fabric and Crashlytics for our iOS app where I work and this news has prompted us to research alternatives.
> We're currently using Fabric and Crashlytics for our iOS app where I work and this news has prompted us to research alternatives. 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.
Knowing Google's reputation with abandoning developer tools and services, can anyone offer suggestions as to possible alternatives? Or counterpoints as to why I shouldn't fear this service degrading over the next year or two? We're currently using Fabric and Crashlytics for our iOS app where I work and this news has prompted us to research alternatives.
> We're currently using Fabric and Crashlytics for our iOS app where I work and this news has prompted us to research alternatives. 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.
Earlier quoted context omitted.
Yeah, that moment of panic when you think something Google acquired is something you use.
In the case of fabric/fabfile this wouldn't matter, as fabric/fabfile looks dead anyway. No Python 3 support, no road map, last Github activity 5 months ago.
One of the goals in the roadmap is to move part of Fabric's functionality into another library (Invoke), which does have recent activity and supports Python 3.
For crash reporting the best alternative I found (superior to Crashlytics IMO) is Sentry[0]. It's been awesome so far and allows you to easily federate crash reporting over multiple platforms. I have no association with the company.
[0]: https://sentry.io/
Knowing Google's reputation with abandoning developer tools and services, can anyone offer suggestions as to possible alternatives? Or counterpoints as to why I shouldn't fear this service degrading over the next year or two? We're currently using Fabric and Crashlytics for our iOS app where I work and this news has prompted us to research alternatives.
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?
Earlier quoted context omitted.
> We're currently using Fabric and Crashlytics for our iOS app where I work and this news has prompted us to research alternatives. 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.
Bravo on Sentry - it's a terrific platform. I'm especially fond of the breadcrumbs, they're a great feature.
Having experienced some rather concerning keychain issues with Digits a few months back and seeing the writing on the wall with Twitter and their stockholders calling for blood I dropped all of my Fabric dependencies in November. For crash reporting the best alternative I found (superior to Crashlytics IMO) is Sentry[0]. It's been awesome so far and allows you to easily federate crash reporting over multiple platform…