Live data from Hacker News

Welcoming Fabric to Google

firebase.googleblog.com

21–30 of 133 posts

Re: Welcoming Fabric to Google

#21
post #13

I haven't heard of Fabric before. Fabric seems to have an ambiguous name and their marketing website is equally ambiguous. Something to do with mobile app analytics? I find this trend in developer tool marketing to be appalling.

They used to be called crashlytics. Best crash reporting tool . Just works. I guess they probably are a lot more interested in ranking for stuff like crash reporting than people chancing upon their website and trying to figure out who they are.

agreed

Re: Welcoming Fabric to Google

#22
post #16

So weird to see the mostly dead http://crashlytics.com and its iOS 6-era design (linen texture!) as it's been superseded by "Fabric" and now "Firebase". Seems like such a strong brand name to kill in favor of these very generic alternatives.

Actually, the entire platform is called Fabric while Crashlytics is only a part of the platform (albeit the main part...).

They've just kept the website as-is since being acquired by Twitter and integrated into the larger Twitter products portfolio.

It is confusing at first though.

Re: Welcoming Fabric to Google

#23
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.

Re: Welcoming Fabric to Google

#24

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.

Re: Welcoming Fabric to Google

#25
post #7

The title is a bit ambiguous. From my understanding, Google (Firebase) acquired Fabric from Twitter (not necessarily "joining"). Fabric is one of the top dev tools I use for iOS. I wonder what kind of change is in store...

Also a big user of Fabric, really hope this means only good things for Fabric users.

Re: Welcoming Fabric to Google

#26
post #20

Fabric was a much better analytics tool than Google Analytics. It's better because: Instant crash reporting reduces release time anxiety. iTunes and Google analytics need 24 hour collection period. Fabric can offer Fastlane and Beta -- Toolkits that help deal with distributing builds to testers and releasing apps. Google has nothing to compete with here. Whatever way Fabric seem to define active users and sessions th…

Well there is that, and also there is the superior accessibility of crash stats.

The Fabric app makes the crash stats very easily accessible to all the relevant people. You are one tap away from them on your phone.

With GA it takes so much more effort to navigate your way to the crash stats.

As a result you respond to issues much more quickly and decisively with Crashlytics. At least that was our experience.

Re: Welcoming Fabric to Google

#27
post #7

The title is a bit ambiguous. From my understanding, Google (Firebase) acquired Fabric from Twitter (not necessarily "joining"). Fabric is one of the top dev tools I use for iOS. I wonder what kind of change is in store...

Yes, you're right - it is an acquisition. Jeff Seibert clarifies in his tweet https://twitter.com/jeffseibert/status/821780349164388356

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).

Re: Welcoming Fabric to Google

#28
post #11
post #4

What does this mean for Twitter Digits? Will their free SMS authentications continue? It would be a perfect fit if they phased in Twitter Digits as a Firebase authentication provider - I suspect many developers (including myself) already use these 2 services in tandem.

I wonder what it costs to operate Twitter Digits. I can't imagine they are using Twilio as an SMS gateway.

Twitter has a bunch of longstanding SMS delivery agreements, so it's quite cheap.

Re: Welcoming Fabric to Google

#29
post #11
post #4

What does this mean for Twitter Digits? Will their free SMS authentications continue? It would be a perfect fit if they phased in Twitter Digits as a Firebase authentication provider - I suspect many developers (including myself) already use these 2 services in tandem.

I wonder what it costs to operate Twitter Digits. I can't imagine they are using Twilio as an SMS gateway.

Twitter used to be the biggest SMS sender in United States. Much larger than Twilio, even bigger than operators like Verizon and AT&T. Infrastructure that came from Cloudhopper acquisition with continuous care and improvement gave Twitter a reliable and super cost effective _world-wide_ SMS delivery platform.

(I was an employee 2012–2016)

Re: Welcoming Fabric to Google

#30

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.

Post reply on HN