Tried hard to get the FCM working for 2 days and just gave up. The playground app sample seems to be broken too. Keep getting auth error. Anyone else here give that a shot yet?
Report
I would rather code in python than java. It seems like Java is the only option for Android app in firebase!
Report
"Without Dynamic Links, if a mobile web user installs your app by opening an app install link, they have to re-navigate to where they were. With Dynamic Links, you can ensure that after a web user installs your app, they can continue where they left off."
How do they do it on iOS? :O
Report
Sounds great! Firebase seems like a powerful ally for app and game development with Google's backing.
I'm definitely going to try this out. Although now that I'm over my PPD (Post Parse Depression), I've already completely switched to AWS...
Report
Wondering if it can replace solutions like AppsFlyer / Adjust or it's not designed for mobile attribution usage? Looks like it!
Report
Firebase powers our online video creation at http://rendrfx.com . We use it on the backend, frontend... all the ends.
Just use Firebase, trust me, I am a professional.
Report
I'm thinking to use this platform instead of a traditional mongodb database. Any advise?
Report
I love firebase. So easy compared setting up your own database.
We're building, and almost live, with a mobile app based Chat product built on Firebase Realtime DB. Firebase definitely made it super easy to build for our use case and we were super happy with having multiple solutions for a mobile app scenario covered from analytics to crashes to auth. However the most critical aspect Auth has given us a lot of trouble. Phone auth in specific, when undertaking OTP via SMS seems to block out numbers it tags as malicious - the problem with this is that more often that not its blocking numbers that are perfectly fine but have logged in too many times. This is just broken and what seems to be an optimisation for cost, is causing a whole lot of troubles during dev and for use cases where multiple logins are required.
If someone from the firebase product team still see this page, please help solve this. This is literally the only thing making us dislike and no trust the platform/
Pros:
Firebase Realtime DB and Admin SDKs are super
Cons:
Phone Auth via OTP fails tremendously. In trying to be "smart" the code fails for false positives almost always blocking non-malicious no's.
Replies
Sounds great! Firebase seems like a powerful ally for app and game development with Google's backing.
Corkdork
Business News for Kids
We're building, and almost live, with a mobile app based Chat product built on Firebase Realtime DB. Firebase definitely made it super easy to build for our use case and we were super happy with having multiple solutions for a mobile app scenario covered from analytics to crashes to auth. However the most critical aspect Auth has given us a lot of trouble. Phone auth in specific, when undertaking OTP via SMS seems to block out numbers it tags as malicious - the problem with this is that more often that not its blocking numbers that are perfectly fine but have logged in too many times. This is just broken and what seems to be an optimisation for cost, is causing a whole lot of troubles during dev and for use cases where multiple logins are required.
If someone from the firebase product team still see this page, please help solve this. This is literally the only thing making us dislike and no trust the platform/
Pros:Firebase Realtime DB and Admin SDKs are super
Cons:Phone Auth via OTP fails tremendously. In trying to be "smart" the code fails for false positives almost always blocking non-malicious no's.