Live data from Hacker News

Firebase gets better analytics, crash reporting and more

techcrunch.com

61–66 of 66 posts

Re: Firebase gets better analytics, crash reporting and more

#61
post #25

Earlier quoted context omitted.

Question: How do you deal with authorisation? I've still yet to come up with a solution I'm happy with unfortunately; I'm currently relying on a custom token generated server-side that grants given users particular claims that I then check in the database rules, but it feels... brittle, I guess.

Exact same thing that we are using for a realtime collaborative app. Generate token on server-side with access to certain keys. However, we had to redo our json structure once we started thinking authorisation. It sucked and in retrospect should have thought about it earlier, but it seems to work. Typically authorisation layers on top of existing data, but in this case, we had to redo data structure keeping auth in m…

> Typically authorisation layers on top of existing data, but in this case, we had to redo data structure keeping auth in mind. Is that why you feel its brittle?

That's pretty much exactly it, I guess. It honestly just feels less "secure" than I'd like, even if it's not!

Re: Firebase gets better analytics, crash reporting and more

#62
post #42
post #25

Earlier quoted context omitted.

Question: How do you deal with authorisation? I've still yet to come up with a solution I'm happy with unfortunately; I'm currently relying on a custom token generated server-side that grants given users particular claims that I then check in the database rules, but it feels... brittle, I guess.

> I'm currently relying on a custom token generated server-side I don't understand. Where's this server? I thought the point of Firebase was that you don't need a server.

For custom claims on tokens you need a server, unfortunately. I've not found a way around it yet, but I was hoping someone had an idea on how to get rid of it!

Re: Firebase gets better analytics, crash reporting and more

#63
post #46
post #2

I stopped looking at Firebase for a while since they seemed to have trouble with my multiple, simultaneous Google account logins. Pretty reasonable growing pains actually, and based on clicking around now, possibly fixed. No opinion on the current news, other than that it's nice to see continued signs of life.

The best way around that is to use Chrome's "Switch Person" feature.

Disagree. Google manages multiple logins just fine.

Re: Firebase gets better analytics, crash reporting and more

#64

I am a super happy Firebase user from day zero. I've built many production-ready apps with it and will continue to do so. So far the only features missing that will make it perfect and a complete back-end solution are: 1. Server code (something like parse server code or AWS lambda) to run event triggers (eg: run more complex data validation or trigger a mail/sms after a ref is created/updated) 2. Full text search. Wh…

On 3, there is https://github.com/firebase/backbonefire , which is our official library for the Firebase Realtime Database + Backbone. We'd be happy to work with you to add additional web features (Auth, Storage, etc.)

Backbonefire does not work with Firebase 3

https://github.com/firebase/backbonefire/issues/152

Re: Firebase gets better analytics, crash reporting and more

#65

I am a super happy Firebase user from day zero. I've built many production-ready apps with it and will continue to do so. So far the only features missing that will make it perfect and a complete back-end solution are: 1. Server code (something like parse server code or AWS lambda) to run event triggers (eg: run more complex data validation or trigger a mail/sms after a ref is created/updated) 2. Full text search. Wh…

Have you taken a look at the AWS managed elasticsearch service for your search/indexing?

Yes, it seems like a good solution. I've also rolled out my own: a simple nodejs app that listens to child added/changed events and updates a simple index which in turn can be queried through an API. For now that fits my needs.

Re: Firebase gets better analytics, crash reporting and more

#66

This is great news. My last few web projects have all been based on Firebase because I focus on the front-end these days and I don't have to worry about scaling, databases, API endpoints and other nonsense which consumes a lot of my day. The pain of even getting a VPS deployed with support for Node.js, database and then figuring out some kind of redundancy to keep Node and my database running can also consume your da…

I developed my first SWA with angular 2 + firebase database/hosting. In one hand, the dev process is really easy and fast (firebase deploy to upload your website).

In the other end, if you want to be fully serverless it's start to getting more complicated. Using external service to manage form (form.io), page pre-rendering (prerender.io), notification...

I don't know why analytic, crash report are only available on Android/iOS because when you are able to do your sdk on 2 platforms. 1 more shouldn't be that hard.

Post reply on HN