iOs

Single Codebase, Two Apps with Flutter and Firebase (Google I/O ’17)

Google+ Pinterest LinkedIn Tumblr +

Video is ready, Click Here to View ×


Create an app for both iOS and Android, without building it twice! In this presentation, you’ll watch how a single developer, live on stage, uses Flutter and Firebase to build two real native apps from a single codebase. This is real! Along the way you’ll learn how to build beautiful cross-platform UIs with Flutter, how you can paint your app to life with Flutter’s sub-second hot reload dev experience, and how to use the Firebase SDK with Flutter.

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

Subscribe to the Firebase channel:

#io17 #GoogleIO #GoogleIO2017

Share.

About Author

21 Comments

  1. damn it google, flutter started 2 years ago and it just looks like java swing for UI, yuck , dump android, build a new platform with flutter as primary framework

  2. Okay, i understand that this is a very clean framework. But, I'm sticking to RN. I like the level of UI control RN offers and more over, i don't need another programming language 🙂

  3. I see a notification from @pouip zxvzxc that they have replied to my message. I click on it and it plays the video for me. I can't find the comment despite looking for it up and down the expanded comments list. If it was deleted by user, why do I still have notification for it? If it still has notification in my notification drop down, why doesn't it tell me it has been deleted?

    These are the number of f*cks google product developers give about User Experience! (hint: 0) … This is why Google will NEVER beat any serious effort in language and UI design. This is why Wave failed. This is why Glass failed. This is why no one uses Google Plus.

    Most google activities are essentially self absorbed masturbation to high technology. They are far removed from the concerns of the actual users. This is just one example of a terrible culture of shining the chrome and not giving a shit about the end user.

    Stick to search. You're good at it.

  4. it would be great not to check style at runtime but rather compile two different apps with two different targets from the same code-base

  5. Interesting idea overall. But, actually, this would look much more readable in Kotlin than Dart. By writing a simple DSL (similar to Anko), you could get rid of large amount of boilerplate that's present in Dart's code. So what's the point of introducing Dart here?