61–70 of 133 posts
Earlier quoted context omitted.
I think you're right but it's weird how this post is coming from the Firebase blog not a main Google products blog (is there one..?). I guess it makes sense...
I would think the "main Google products blog" is https://blog.google/
While Firebase is still awesome, there was a definite downgrade in support when Google integrated them. Hopefully this will go better.
Anything specific you'd like to let us know about? Definitely agree that it hasn't been the smoothest transition--it's super hard to provide 24/7 support to hundreds of thousands of developers. Any feedback you can provide will help us refine that process.
Twitter just lost one of their crown jewels; Fabric is probably the biggest mobile analytics platform out there.
It is also a bizarre buy. Google has been building a competitor to fabric crash reporting. 6 months ago it was an MVP, but the version unveiled recently is pretty close to fabric. I am not sure what they are buying here, it seems that google could sherlock everything that fabric does, especially since fabric is not that great in my experience. Maybe it just illustrates that I am missing some info on why Google would…
Earlier quoted context omitted.
I think they're saying "joining" because > Fabric will join Google's Developer Product Group, working with the Firebase team.
I think you're right but it's weird how this post is coming from the Firebase blog not a main Google products blog (is there one..?). I guess it makes sense...
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.
From the article > [...] 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...
Unlikely that we'll see improvements in Fabric services for a while... presumably, engineering resources will be focused on integrating with Firebase :( Anyone recommend alternatives for Crashlytics and Digits?
Silly me - I was concerned they somehow acquired the Fabic python library. http://www.fabfile.org/
Yeah, that moment of panic when you think something Google acquired is something you use.
Earlier quoted context omitted.
More specifically, Twitter is carving out (i.e. divesting) Fabric and selling it to Firebase, which is a wholly owned subsidiary of Google (or perhaps selling it to Google directly).
Firebase is really just a Google brand at this point, not a separate company.