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

Firebase Crashlytics graduates from beta

firebase.googleblog.com

Post reply on HN
Print view View original

11–17 of 17 posts

Re: Firebase Crashlytics graduates from beta

#11

Post by itcmcgrath »

welanes wrote: post #5

Firestore next please. For the 'indie' developer, Firebase is a gift. By way of example, I (re)started building an app that tracks anomalies in cryptocurrency volume at the weekend. By building on Firebase (Auth, FireStore, Functions) it's all but ready. That lack of friction between idea and reality didn't exist too long ago. (Firebase ain't the only ones, Zeit are also doing slightly-different-but-equally-incredibl…

PM for Cloud Firestore here -> thanks for the feedback, we're working on getting to GA.

Feel free to email(dan + mcg at google), Twitter DM, etc more details about your cost concerns.

The quota change issue is complex, but yes we'd like to make it faster :)

Re: Firebase Crashlytics graduates from beta

#12

Post by welanes »

justaguyhere wrote: post #10
welanes wrote: post #5

Firestore next please. For the 'indie' developer, Firebase is a gift. By way of example, I (re)started building an app that tracks anomalies in cryptocurrency volume at the weekend. By building on Firebase (Auth, FireStore, Functions) it's all but ready. That lack of friction between idea and reality didn't exist too long ago. (Firebase ain't the only ones, Zeit are also doing slightly-different-but-equally-incredibl…

Is your application ready? Would like to check it out, also any write-up on the tech details of it.

Almost. The preview page is here - https://mooon.club - and should be live before the end of the week.

Tech-wise it's Vue.js and Highcharts on the front-end, Firestore on the back, and Zeit now/Firebase functions doing the grunt work on the APIs.

Once it's ready to go I'll pop it on show HN and go into more detail on how it works.

Re: Firebase Crashlytics graduates from beta

#13

Post by welanes »

itcmcgrath wrote: post #11
welanes wrote: post #5

Firestore next please. For the 'indie' developer, Firebase is a gift. By way of example, I (re)started building an app that tracks anomalies in cryptocurrency volume at the weekend. By building on Firebase (Auth, FireStore, Functions) it's all but ready. That lack of friction between idea and reality didn't exist too long ago. (Firebase ain't the only ones, Zeit are also doing slightly-different-but-equally-incredibl…

PM for Cloud Firestore here -> thanks for the feedback, we're working on getting to GA. Feel free to email(dan + mcg at google), Twitter DM, etc more details about your cost concerns. The quota change issue is complex, but yes we'd like to make it faster :)

Thanks for engaging, and hats off for a solid product.

Regarding costs, the quota was hit pretty quickly due to the trial and error of deciding the best way to structure my data so likely a once off spike in DB reads. But good to know I can reach out.

Tbh, I'd trade all my concerns for a timeline on when we'll see collection group queries ;)

Re: Firebase Crashlytics graduates from beta

#15

Post by zeeg »

kylehotchkiss wrote: post #2

Wish I could get this same reporting for Javascript and get out of Sentry. Maybe one day! Firebase Functions being able to debug to Crashlytics would be cool.

I’m genuinely curious why you would want this?

For context I’m the founder, CEO, and original author of Sentry. We provide an immense amount of data for every platform and hear the exact opposite of this sentiment (“id love to use Sentry for my mobile apps”).

We’re long past the days of one vendor being able to accomplish every problem (there’s evidence everywhere that this is bad) and while I appreciate competition in the space that’s far different from expecting whichever provider you choose to be a one stop shop.

That’s besides the point that Sentry is open source and we’re the only option out there for a lot of people.

If it’s simply you think Firebase can do a better job than us I want to know why. If it’s consolidation then ask yourself why shouldn’t Google work with others instead of trying to own every space in every market? There’s a lot more value in specialization than there is in checkboxes, especially if it means working with a wider ecosystem.

I mean this as no slight to Firebase as I’ve quite enjoyed prototyping things on the platform, but I can’t get behind the idea that Google or anyone else should hold a monopoly over our ability to write software and build businesses.

Re: Firebase Crashlytics graduates from beta

#16

Post by ritoune »

welanes wrote: post #12
justaguyhere wrote: post #10

Earlier quoted context omitted.

Is your application ready? Would like to check it out, also any write-up on the tech details of it.

Almost. The preview page is here - https://mooon.club - and should be live before the end of the week. Tech-wise it's Vue.js and Highcharts on the front-end, Firestore on the back, and Zeit now/Firebase functions doing the grunt work on the APIs. Once it's ready to go I'll pop it on show HN and go into more detail on how it works.

Any reason you chose highcharts over charts.js or plotly.js ?

Re: Firebase Crashlytics graduates from beta

#17

Post by welanes »

ritoune wrote: post #16
welanes wrote: post #12

Earlier quoted context omitted.

Almost. The preview page is here - https://mooon.club - and should be live before the end of the week. Tech-wise it's Vue.js and Highcharts on the front-end, Firestore on the back, and Zeit now/Firebase functions doing the grunt work on the APIs. Once it's ready to go I'll pop it on show HN and go into more detail on how it works.

Any reason you chose highcharts over charts.js or plotly.js ?

I tried a few charting libraries including Chart.js, Taucharts and D3.

Much of Taucharts is undocumented, Chart.js requires a lot of configuration for something like a mixed chart with stacked bars, and D3, yikes. Its API documentation is thicker than Ulysses.

Highcharts required minimal configuration, had an intuitive and clear API and - most importantly - handled all sorts of messy data I threw at it. It just worked, out-of-the-box.

Post reply on HN