Is user email confirmation finally supported by Firebase? Last time I checked it wasn't.
If you try it out, ping me at alfongj at google dot com and let me know what you think!
201–210 of 214 posts
Is user email confirmation finally supported by Firebase? Last time I checked it wasn't.
If you try it out, ping me at alfongj at google dot com and let me know what you think!
Earlier quoted context omitted.
You can use any Google Cloud product with Firebase so you have access to Cloud Functions. https://cloud.google.com/functions/
I've been eyeing this. Can we kick off a Cloud Function via Firebase Cloud Messaging?
Short answer is no (well.. not without an intermediate proxy of some sort), but we're in the process of providing direct integration with Cloud Functions across many of the services that fall under the Firebase umbrella. So stay tuned!
Earlier quoted context omitted.
> We spend months to migrate our product to PostgreSQL Which means you presumably saved months initially by using Azure, and got your product to market sooner. Everyone should be aware of the dangers of lock-in, and should carefully consider the value of it vs. the liability they're taking on. But I wouldn't say never use products like this. The value-add can be significant, even taking into account the fact that you…
That MIGHT be true, but it's not apparent from their statement. Just because it costs N to build a product on technology X and costs M to migrate an existing product to technology Y does not mean that it would have cost N + M to implement the product on technology Y in the first place.
Earlier quoted context omitted.
I've been eyeing this. Can we kick off a Cloud Function via Firebase Cloud Messaging?
Hey.. PM for Cloud Functions here. Short answer is no (well.. not without an intermediate proxy of some sort), but we're in the process of providing direct integration with Cloud Functions across many of the services that fall under the Firebase umbrella. So stay tuned!
Firebase is an incredibly powerful tool, and in a sense is a "democratizing force" in web development. Now anyone can build a complete web application without needing to know anything about setting up servers, content delivery networks, AWS (which is still quite difficult to use), and scaling. I teach kids as young as 10 years old to build iOS apps and websites with Firebase - they can develop locally and push to Fir…
Earlier quoted context omitted.
The difference is actually between a product and a service . A service is something that another party provides, and that may - actually, they most definitely will - at some point stop providing, for various reasons. You want to minimize your dependence on any services - especially ones that are not trivially replaceable or that don't come with contractual agreements to cover your costs in case of the service being s…
I totally respect your perspective, but SaaS is gaining popularity because software customers are making an informed decision about the tradeoffs of product vs service as a delivery model, not because service providers are forcing the SaaS model on them. Many customers see value in shifting the operations and support burden to the software vendor. I think it's ultimately good that users have more choice in how they c…
I'm not making a value judgement; I'm pointing out that SaaS is often picked for only its short-term benefits.
As a current Firebase customer, I'm pretty thrilled about all this (especially since I was afraid Google would pull a Facebook here). However, there's quite a bunch of API changes and absolutely no info about how long the old JS library, endpoints, etc etc are to keep working. Should I get stressed out?
(Firebase engineer here) The old SDKs will continue to work! We worked extremely hard to make sure everything was backwards compatible with them. We most certainly do not want to break any existing customer apps. Check out the migration guides [1] to get your app updated to the new SDKs. We understand migrating is not easy or always convenient. If you run into issues or something that used to work seems to be no long…
Earlier quoted context omitted.
Yeah, the challenge is that it seems to rely on Google services (not just libraries) at the app layer in a way that screams lock-in.
Downvote? Is it not reliant on Google services?
Earlier quoted context omitted.
Downvote? Is it not reliant on Google services?
HN crowd is pro-Google, I feel. I get pounded with downvotes, the moment I speak against the darling of the Bay Area (?)
Never liked the downvoting idea, but if it must be, then it would be nice if people were at least required to comment while downvoting and open themselves to downvotes for their whacked, baseless downvotes.
For Firebase/Google Cloud Platform engineer: does it mean Google Cloud Endpoints is being phased out? if i'm already using Google Cloud Endpoints, should i move to Firebase? what's the advantage?
Hi -- PM for Endpoints here. Endpoints is going strong and will have a release later this year that adds support for hosting APIs on more of our compute offerings (Compute Engine, Container Engine, App Engine Flexible Environments). We'll also be adding features, reporting, etc.