Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Welcoming Fabric to Google

firebase.googleblog.com

Post reply on HN
Print view View original

111–120 of 133 posts

Re: Welcoming Fabric to Google

#111

Post by alex4Zero »

redindian75 wrote: post #43
jayrhynas wrote: post #9

Earlier quoted context omitted.

They do say > During the transition period, Digits, the SMS authentication services, will be maintained by Twitter. but it's unclear what will happen long term

Long-term it will be with Google. It says so here: As part of this acquisition Digits will be transitioning to Google over the coming months but will be maintained and operated by Twitter in the interim

The main thing is that Digits is free. We are using it in our products. I hope Google doesn't have plans to earn money here

Re: Welcoming Fabric to Google

#113

Post by stevepotter »

danielhooper wrote: post #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.

HockeyApp is great. Owned by Microsoft, who has doubled down on mobile tools with Xamarin. For beta distriubtion, HockeyApp is a superior product. And it has an API (so you can, say, auto register iOS devices). Fabric is just more known and considered cooler (they do have nice CSS transitions :).

Re: Welcoming Fabric to Google

#114

Post by julien_c »

the_mitsuhiko wrote: post #78
nstj wrote: post #73

Earlier quoted context omitted.

Bravo on Sentry - it's a terrific platform. I'm especially fond of the breadcrumbs, they're a great feature.

Thanks so much. It's always great to hear when people enjoy what we're doing :)

Love it as well and I am recommending it to everyone I know who's shipping iOS apps

Re: Welcoming Fabric to Google

#115

Post by stevepotter »

I'm an active user of Fabric and have found it rather convoluted and limited. For example, there is no way to easily get device UUIDs from Beta testers. Given they also sponsor Fastlane, I'm blown away they haven't provided a way to automatically register UUIDs. This is possible with HockeyApp through their API and some Fastlane scripts.

Crashlytics is their killer feature. The rest is mediocre. Hopefully Google will improve it. I'm not holding my breath.

Re: Welcoming Fabric to Google

#116

Post by luckydata »

s_dev wrote: 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…

They are two completely different tools, they can't be compared, serve different purposes.

Re: Welcoming Fabric to Google

#117

Post by pier25 »

nstj wrote: post #76

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…

Can confirm, Sentry is awesome. It's been very easy to integrate in our web apps and the results are helpful.

Re: Welcoming Fabric to Google

#118

Post by chrisstott »

stevepotter wrote: post #115

I'm an active user of Fabric and have found it rather convoluted and limited. For example, there is no way to easily get device UUIDs from Beta testers. Given they also sponsor Fastlane, I'm blown away they haven't provided a way to automatically register UUIDs. This is possible with HockeyApp through their API and some Fastlane scripts. Crashlytics is their killer feature. The rest is mediocre. Hopefully Google will…

You might be interested in buddybuild's beta distribution which does automatic UDID management.

It basically makes it so neither the developer nor the tester ever have to worry about UDIDs ever again. Instead you can send a build to a new tester & trust they can immediately install it.

[Disclaimer, I built that feature at buddybuild]

Re: Welcoming Fabric to Google

#119

Post by pier25 »

mbleigh wrote: post #56
orbitur wrote: post #55

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?

My main problems with the console are:

1) Lack of in depth analytics on storage and the database. You give us some vague bandwidth and space metrics which aren't that useful.

2) No way to search, filter, or query the database. The database manager is really only a JSON editor which isn't that useful. I'm guessing this is a consequence of the database API being very limited.

3) Editing rules using a JSON or even Bolt becomes unmaintainable once you reach a certain complexity. Specially if you want to create role based permissions. There should be a UI to manage rules. Even better, there should be a role based permissions system built in.

Re: Welcoming Fabric to Google

#120

Post by manigandham »

danielhooper wrote: post #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.

What have they abandoned?
Post reply on HN