[depoll]

I was an early Parse engineer (4th engineer to join the company) and now am the SDK engineering lead for Firebase.

The experience of working on Firebase at Google is vastly different from Parse at Facebook, and it shows in Google’s continued commitment to building and expanding Firebase, integrating it with its Cloud Platform products, and otherwise pouring huge amounts of effort into making Firebase great for developers. Open sourcing our SDKs gives us even more ways to engage with the developer community and allows us to be more transparent with the progress we’re making.

This announcement is just a first step down the path toward more transparency with our SDKs, but we hope to foster community and build trust in the tools we’re developing, and welcome your contributions!

[salimmadjd]

That's great! But it does make sense why google and FB would be taking different paths here.

As much as I was disappointed with FB's decision on Parse, I can also understand the reasoning behind it and I actually think it was the right decisions for the company. In contrast, Google is playing in the cloud service vertical and investing in the future of Firebase is totally aligned with that objective.

[daxfohl]

Though it does seem kind of odd that facebook isn't playing in that space. I'd be curious to know their reasoning for not launching a competing product there.

[dirtylowprofile]

I'm just wondering if there is a feature on your future pipeline to include username as a sign up/sign in your SDKs besides only email and password?

[salqadri]

Firebase actually announced phone number authentication on Wednesday as yet another alternative to only having email/pw.