Firebase Authorization – User Accounts

I am very new to Firebase but one thing I am very excited about is their authorization schemes.  If it’s the way I think it is it’s pretty awesome.

From a user perspective it’s very convenient.  Basically, if you log into gmail (or one of the other supported apps like twitter, facebook, github) you’re logged into my app.

That’s very cool, because you don’t have to remember another user name an password.

From a developer perspective it’s nice because I don’t need to store user names and passwords.  I don’t need to support people forgetting their user credentials.  I don’t need to worry about salts or hashes… gmail handles all of that.

That’s the good stuff.

The bad stuff is that users get confused.  They think that my app might have their gmail password.  They think that I might have access to their gmail…  It’s confusing from a user’s perspective.

Another bad thing is that if Google changes things (well when) it will break my app.

Another bad thing is that setting it up is a moving target and it’s hard to document exactly how to do it because after a bit of time the documentation will be wrong.

For me it good way out weighs the bad because if I don’t have to build a login system that saves me time.  I can roll out a new app in way less time.  What might have taken me a week if you build it yourself or two now takes a few minutes.

Then you can uniquely identify users by their gmail user name.

Leave a Reply