Supabase + Riverpod: Real-Time Data Without the Boilerplate

Supabase + Riverpod is popular because Postgres + ref.watch is a clean mental model. FlutterInit removes the boring part: initialize Supabase, wire AuthService (signInWithPassword, onAuthStateChange), and hook Riverpod auth controllers. Realtime table subscriptions are not a fake generated feature — you add them on the shared client once auth works.

What the scaffold gives you

• Supabase.initialize via SUPABASE_URL / SUPABASE_ANON_KEY
• AuthService with auth state stream mapped to user maps
• Riverpod repository + controller providers under your architecture
• SETUP.md for keys

Combo deep dive: Riverpod + Feature-First + Supabase.

Auth stream → Riverpod

Supabase emits onAuthStateChange. Session providers/Blocs in the scaffold listen through the repository/service so screens don’t subscribe ad hoc.

Adding realtime (your code, their client)

Once AppConfig.supabase exists:

Keep the stream in data, map to domain models, expose with StreamProvider or equivalent. Don’t open channels inside widgets.

RLS and keys

Anon key in the client is normal. Row Level Security is mandatory for anything serious — FlutterInit can’t invent your policies.

Related

• Firebase Auth wiring
• Backend comparison

Generate Supabase + Riverpod on /create, ship auth, then add one realtime table.

// Example pattern — add in a repository, expose via Riverpod StreamProvider
supabase
  .from('todos')
  .stream(primaryKey: ['id'])
  .map((rows) => rows.map(Todo.fromJson).toList());