Updates, guides, and deep-dives on Flutter development.
FlutterInit now includes a VS Code–style live code preview. Browse the generated file tree, open tabs, and watch your scaffold update as you change wizard options — before you ever download a ZIP.
DESIGN.md is FlutterInit’s design-system brief for agents: theme, colors, typography, spacing, and motion — so UI changes stay on-token.
FlutterInit vs very_good_cli vs Mason: when to use each Flutter scaffolding tool — honest trade-offs for teams picking a starter.
FlutterInit uses Handlebars templates, not an LLM, to emit Flutter scaffolds. Same inputs always produce the same architecture, deps, and AI context files.
Bloc + Clean Architecture + Appwrite delivers predictable events/states, Clean layers, and a backend you can self-host. The enterprise Flutter stack, explained.
Enable Dio in FlutterInit and you get AppConfig.dio with logging interceptors plus a DioService wrapped in runTask / Either — opt-in, not silent magic.
FlutterInit projects ship Cursor rules plus AGENTS.md and DESIGN.md. Here’s how to use that context so agents extend your stack instead of rewriting it.
flutter create gives a counter demo. FlutterInit adds architecture, auth wiring, routing, theme tokens, and AI context files — then you own the code.
MobX + Clean + Firebase: reactive observables on Clean layers with Firebase Auth. Less common than Riverpod — still a valid FlutterInit stack.
FlutterInit can emit go_router or AutoRoute from one template. Here’s how they differ in a Clean Architecture app — and when to pick each.
FlutterInit ships CLAUDE.md, AGENTS.md, DESIGN.md, and Cursor rules with every scaffold so AI agents know your stack before they touch a file.
Provider + MVVM + Firebase: ChangeNotifier ViewModels, data/ui folders, and Firebase email-password auth for beginners and small teams.
Firebase, Supabase, and Appwrite all work with FlutterInit. Compare auth, database, self-hosting, and when each fits a Flutter team.
FlutterInit’s MVVM is practical: lib/src/data for repos, lib/src/ui for screens and providers — ViewModels without Android textbook baggage.
Riverpod + Feature-First + Supabase keeps feature folders and Supabase auth without paying Clean Architecture ceremony you may not need yet.
FlutterInit scaffolds Supabase auth and Riverpod providers. Realtime channels are the next step on that base — here’s the honest split.
In FlutterInit, Feature-First and Clean share feature folders today. Choose based on team mental model and docs — not imaginary file trees.
MVVM with Provider and Appwrite is FlutterInit’s low-ceremony stack: data + ui folders, ChangeNotifier-style auth, and Appwrite sessions.
FlutterInit wires Firebase Auth email/password, AppConfig init, AuthService, and repository hooks — you still add google-services and API keys.
Clean Architecture in FlutterInit means lib/src/features with data, domain, and presentation — not a textbook diagram. Here’s the real tree.
Bloc for events/states, Feature-First folders, Supabase auth — what FlutterInit generates and when this stack beats Clean + Firebase.
The FlutterInit CLI lets you scaffold a production-ready Flutter project without opening a browser. One command, an interactive wizard, and your project is ready to run.
Riverpod, Clean Architecture, and Firebase — when to choose this Flutter stack, what FlutterInit generates, and how the layers connect.
FlutterInit is now live. Generate a fully-structured Flutter project with your chosen architecture, state management, and backend — all from a web UI, no CLI required.