Firebase Overview - Google I/O 2016

By: Firebase

481   11   77298

Uploaded on 05/19/2016

Firebase just unveiled many significant and exciting new features. This session will give you an overview of what we’ve introduced and how you can use Firebase to build better apps and grow your business. James Tamplin and Francis Ma - product leads of Firebase, give you the full picture. After this session you’ll be equipped with the tools needed to build and grow the next great app!

Watch more Firebase talks at I/O 2016 here:
See all the talks from Google I/O 2016 here:

Get started using Firebase today

#io16 #GoogleIO #GoogleIO2016 #Firebase -

Get started using Firebase today

#io16 #GoogleIO #GoogleIO2016 #Firebase

Comments (4):

By anonymous    2017-09-20

I've used a lot of Firebase and a bit of DynamoDB. Both are respectable choices.

I'll give you my biased view of why I chose Firebase over DynamoDB, and will let others give you the other angle:

  • DynamoDB is great if all you want to do is put and get values based on keys. However, it is quite limited when it comes to querying and searching. Firebase excels in this, in terms of usability and speed. For example, if you have a database of users, you could query based on their child value (lastLoggedIn), and choose the users who just logged in today. If this query is done frequently, you could index on this key and speed up this query. Read more here:

  • Firebase allows you to define security rules for each table/database easily. You can define IAM roles in AWS for DynamoDB too, but I doubt they have as much flexibility as Firebase.

  • Firebase allows for transactions that supports concurrent modifications:

  • If you're developing a mobile app, push notifications are easy to set up.

  • Offline capabilities are seamlessly integrated into your app without much setup:

I used to have doubts about Firebase, but ever since Google acquired Firebase in 2014, and talked about it so fervently in 2016 at Google I/O (, I gained faith in it.

Oh, and did I say that the Blaze plan on Firebase is cheaper than DynamoDB for both storage and computation?

Original Thread

By anonymous    2017-09-20

So, you want to allow some users to register, but not others? I'm also assuming you want to use Google's built in registration system.

First Method

The fastest but probably hardest way to achieve this is to use firebase functions to whitelist a set of users in advance. Firebase functions can catch the request for sign-up then simply ignore it if it doesn't match your whitelisted addresses.

Of course you could use it to perform all sorts of other features too like sending it a request that allows sign-up for a short period of time. Anything that is possible through javascript.

Otherwise you'll be stuck creating your own sign-in method.

That, I think is the only way to prevent them from registration.

Second Method

If instead you wanted to allow signup but not allow access to the database you should be able to set the rules to "auth = (uid)" which will only allow those uids to write.

Again the same process can be achieved with firebase functions by allowing writing and such based on your set of uids.

Another method is firebase remote config conditions and to achieve a similar effect. (I wouldn't suggest this however because it can create an unsafe client side authentication, or unnecessary steps to check for auth).

Something that I use which is similar is allowing full access to the database but using firebase functions to prevent deletion. This method allows users have full access but I can easily change their ability to write, move, or delete nodes whenever I want. Essentially, if it turns out that the firebase functions method is best suited for your situation, I can update my response to include a sample from my code.

Third Method

Some users of firebase instead use the database to store users and their credentials along with their profile data. So that when a user signs up, it instead will add a node to the database which can easily be accepted or denied by simple moving it, deleting it, or creating a key which dictates their permissions.

Good luck with firebase. Its features can often be somewhat hidden and hard to find. It might be useful to watch the full Google I/O presentation on youtube which explain its expansive repertoire in detail. It can be found here. I highly suggest this because it helped me better understand the features and (to be honest) all the ways I should have been using firebase (but wasn't).

Original Thread

Recommended Books

    Popular Videos 1413

    Submit Your Video

    If you have some great dev videos to share, please fill out this form.