Firebase Auth in FlutterInit: What Gets Wired Up Automatically
FlutterInit wires Firebase Auth email/password, AppConfig init, AuthService, and repository hooks — you still add google-services and API keys.
Stack Configuration — what FlutterInit generates for this guide
When to choose this stack
Choose Firebase when you want Google’s auth + ecosystem (Analytics, Crashlytics, FCM) and FlutterInit’s email-password scaffold as the starting point.
Select Firebase as the backend and FlutterInit doesn’t stop at a firebase_auth dependency. It initializes Firebase in app startup/config, swaps in a real AuthService, and connects repositories so login/signup/forgot-password screens already call something real.
What gets wired
- Dependencies —
firebase_core,firebase_auth(and related bits per template) - AppConfig / main — Firebase initialization path for your platforms
- AuthService — email/password login, signup, reset, logout, auth state
- Repository → presentation — Clean/Feature-First/MVVM state objects call the repo, not the SDK from widgets
- SETUP.md — where to drop
google-services.json/GoogleService-Info.plist
You still create a Firebase project and add platform config files. The scaffold doesn’t magically know your project ID.
What AuthService looks like (pattern)
Firebase auth methods run inside runTask and return Either-style results — same shape as Supabase/Appwrite services — so swapping backends later doesn’t rewrite every screen.
What you add next
- Google / Apple sign-in providers
- Phone auth
- Security rules / Firestore data (auth alone isn’t your database)
Related stacks
- Full Clean walkthrough: Riverpod + Clean + Firebase
- Beginner MVVM path: Provider + MVVM + Firebase
- Compare backends: Appwrite vs Firebase vs Supabase
Generate Firebase auth on /create, then follow SETUP.md before flutter run.
Ready to build?
Generate this project in seconds
FlutterInit scaffolds the entire structure described in this guide — wired up, typed, and ready for flutter run.