Integrate Firebase into your team's development workflow

Taking an idea from prototype to production often involves collaborating with multiple team members with different roles. In this session, learn how to use Firebase tooling like the emulators, along with industry-standard tooling like GitHub Actions, to ensure that each person on your team has access to the right environment and the right information at critical stages of development.
Resources:
Firebase Local Emulator Suite → goo.gle/3O9Z6OL
Deploy to Firebase Hosting GitHub Action → goo.gle/37QSTqp
Blaze plan calculator → goo.gle/38QKfIU
Speaker: Jeff Huleatt
Watch more:
All Google I/O 2022 Sessions → goo.gle/IO22_AllSessions
Firebase at I/O 2022 playlist → goo.gle/IO22_Firebase
All Google I/O 2022 technical sessions → goo.gle/IO22_Sessions
Subscribe to Firebase → goo.gle/Firebase
#GoogleIO

[@b0otable]

Interesting video. The element I don't understand is how you deal with development changes to your firebase database with a specific preview url. You discuss having a Test-Database and a Production-Database, however the way you describe development seems to assume that every preview URL will utilize the exact same database structure. This is probably reasonable for more developed apps but perhaps not during initial development. I would be interested to know how you suggest handling multiple version of firebase databases that are linked with specific preview URLs as well as best practices for firebase firestore migrations between versions with production data.