Flutter Firebase Boilerplate: the complete Firebase wiring done right

Why "Firebase done right" is harder than adding the packages

Anyone can run flutter pub add firebase_core. The real work is what comes after: initializing Firebase before runApp, gating UI on auth state without flicker, structuring Firestore reads as streams instead of one-off gets, securing Storage uploads, deploying Cloud Functions that your app actually calls, and handling FCM tokens across cold start, foreground, and background. The Flutter Kit ships all five services already connected through a single get_it container, so FirebaseAuth, Firestore, Storage, Functions, and Messaging are injected — not scattered as global singletons you call from inside widgets. Each service sits behind a repository, and your BLoC/Cubit talks to the repository. That one layer of indirection is what lets you swap Firebase for Supabase later without touching a screen.

• firebase_core initialized correctly before runApp with platform options
• AuthRepository exposing a authStateChanges() stream your AppBloc listens to
• Firestore reads modeled as typed streams, writes as repository methods
• Storage upload/download helpers with progress and content-type handling
• A Cloud Functions client wired to a deployed sample function you can call on day one

The five services, and exactly what's pre-wired

Firebase Auth ships with email/password, Google, Apple, and anonymous sign-in, plus the auth-state listener that drives routing through go_router. Firestore comes with a repository pattern, model serialization, and example collections (profiles, plus a sample data feature) so you see real reads and writes, not a hello-world doc. Cloud Storage handles avatar and file uploads behind a typed repository. Cloud Functions includes a deployable sample function and the callable-function client so your secure server logic is reachable from Dart immediately. FCM push is wired for local and remote notifications with a diagnostics screen that surfaces your token, permission state, and last-received payload — the part most starters skip, and the part that eats a full day when push silently doesn't fire.

• Auth: email, Google, Apple, anonymous — with pre-built profile and settings screens
• Firestore + Storage: repository-backed, model-mapped, with working example features
• Functions + FCM: a deployable sample function and push diagnostics for foreground, background, and cold start

When you should NOT use a Firebase boilerplate

Be honest with yourself about the backend before you buy. If your app is read-heavy with complex relational queries, joins, or row-level security needs, Firestore's document model fights you and Supabase (Postgres) is the better fit — and The Flutter Kit's repository pattern means the Supabase variant is a swap, not a rewrite, but you'd still rather start from the right side. If you already own a REST or GraphQL backend, you don't need Firebase at all; you need the architecture, auth UI, and RevenueCat layer, and you'll delete the Firestore code. And if you're a Flutter learner who genuinely wants to understand how FirebaseAuth's stream drives a router, wiring it by hand once is a worthwhile afternoon. A boilerplate is for the second, fifth, and tenth app — when re-typing the same five services is just tax.

What the Firebase wiring saves you on every new app

The value isn't the first hour saved; it's that you never pay the Firebase setup tax again. No more copying firebase_options.dart between projects, re-deriving the auth-gate, re-debugging why FCM works in the foreground but not the background, or re-writing security-rule-aware repositories from memory. Because AI is a feature-flagged module, you can ship a pure Firebase CRUD app with the AI/OpenAI layer turned off, then flip it on later. RevenueCat sits alongside Firebase for paywalls and entitlements, GA4 handles analytics with GDPR/CCPA consent, and Material 3 design tokens let you retheme from one file. You own the full Dart source, so the Firebase code is yours to extend, audit, or rip out.

The Flutter Kit vs. wiring Firebase from scratch

Frequently Asked Questions