Building Scalable and Secure Apps with Flutter and Firebase: Best Practices and Pricing Strategies
summary
Demo Flutter app uses Firestore with the Firebase emulator, client-side caching and indexing, and a Cloud Function / Cloud Storage workflow automated by the bundle builder extension to publish Firestore bundles; loading bundles into client cache cuts reads from ~3,750,000 to ~2,250 (a 99.94% savings in billable reads). Security rules run against the emulator with Mocha tests, app check and Firestore→BigQuery streaming are recommended; the demo implementation works end to end.
AI-written summary · about
chapters (16)
- 0:00Introduction and speakers
- 1:08Flutter and Firebase overview
- 3:17Firebase pricing and scalability concerns
- 8:15Using Firebase emulator for development
- 10:24Firebase extensions introduction
- 12:31Demo ice cream shop app
- 18:01Scalability pricing scenario breakdown
- 22:35Client-side caching for reads
- 29:30Firestore bundles for data sharing
- 36:54Firestore bundle builder extension
- 45:23Loading bundles in Flutter app
- 54:13Optimizing cache and performance
- 1:07:22Security rules for data protection
- 1:13:44Testing security rules with emulator
- 1:27:17App security and Firebase App Check
- 1:35:04Q&A and closing remarks
related talks
32mSecurity in Flutter: Our Priority
36mSecuring Flutter Apps
43mDangerous Flutter... Or Not?
13mSecure your Firebase app from the start
01h 19minteroperable healthcare apps in Flutter
25mFive tips to secure your app
31mThe cloud built for developers
52mFirebase and Google Cloud Functions: your apps without servers / serverless