Firebase Auth in FlutterInit: What Gets Wired Up Automatically

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

1. Dependencies — firebase_core, firebase_auth (and related bits per template)
2. AppConfig / main — Firebase initialization path for your platforms
3. AuthService — email/password login, signup, reset, logout, auth state
4. Repository → presentation — Clean/Feature-First/MVVM state objects call the repo, not the SDK from widgets
5. 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.