No installation required. Open flutterinit.com and generate.
FlutterInit is a web-based scaffolding engine for Flutter.
You visit flutterinit.com, pick your architecture, state management, backend, and navigation style — and FlutterInit generates a production-ready Flutter project as a downloadable zip.
No templates to clone. No CLI to install. Open the dashboard, configure, download, build.
- Open flutterinit.com
- Name your project and choose your options:
- Architecture: Clean Architecture, MVVM, Feature-First
- State Management: Riverpod, Bloc, Provider, GetX, Signals
- Backend: Firebase, Supabase, Appwrite, or none
- Navigation: go_router, auto_route, or none
- Design: Material 3, dark mode, ScreenUtil
- Extras: localization, logging, permissions, image picker, etc.
- Click "Generate Project"
- Download the
.zip - Unzip →
cdinto the folder → runflutter pub get→flutter run
Every generated project includes:
- Folder structure matching your chosen architecture
- Routing pre-configured with your chosen navigation package
- State management boilerplate set up and ready to extend
pubspec.yamlwith all chosen dependencies declared- Environment config (
.envsupport viaflutter_dotenv) - Logging, error handling, and base network layer (if Dio selected)
- Material 3 theme with dark mode support
- AI context files:
CLAUDE.md,AGENTS.md,.cursorrules— pre-written for your exact stack so AI editors have full project context from day one
No installation required.
- Go to flutterinit.com
- Configure your stack using the visual dashboard
- Click Generate Project and download your
.zip - Unzip and run:
cd your_project_name
flutter pub get
flutter runThat's it. Your project is ready.
- Flutter SDK
^3.5.0(install guide)
No other tools required. FlutterInit runs in your browser.
- Node.js
^20.0.0or Bun^1.1.0 - Flutter SDK (for running
dart analyzeon generated output during testing) - See CONTRIBUTING.md for full setup
You configure all of these options directly in the dashboard — no config files, no flags.
| Category | Supported Options |
|---|---|
| Architectures | Clean Architecture, MVVM, Feature-First |
| State Management | Riverpod, Bloc / Cubit, Provider, GetX, Signals |
| Functional | FPDart (Either, Option, Task), runTask Wrapper |
| Backend / DB | Firebase, Supabase, Appwrite, Hive, Shared Preferences |
| Networking | Dio (Interceptors), Http, Cached Network Image |
| Navigation | go_router, auto_route |
| Design / Motion | Flutter Animate, Skeletonizer, ScreenUtil, Native Splash |
| Icons | Iconsax Plus, Remix Icons, HugeIcons (Stroke/Solid) |
| Infrastructure | DotEnv, Logger, Easy Localization, App Version Update |
| Utilities | Picker (Image/File), Permissions, Share Plus, Geolocator |
Every generated project includes pre-written AI context files tailored to your exact stack:
CLAUDE.md— for Claude CodeAGENTS.md— for Codex and other agent workflows.cursor/rules/flutter-project.mdc— for Cursor
These files give your AI editor full context about your architecture, state management pattern, folder structure, and conventions — without you having to write a single prompt.
FlutterInit ships a built-in blog at flutterinit.com/blog — a file-based MDX publication powered by Next.js, with two content types:
| Kind | Purpose |
|---|---|
| Updates | Release notes, announcements, and changelogs |
| Guides | Deep-dive technical guides for every supported stack combination |
Every guide shows the exact stackConfig it covers (Architecture · State · Backend · Navigation), a "when to choose this stack" recommendation, an interactive file tree of the generated output, and a Table of Contents sidebar.
Blog content lives under content/blog/ as .mdx files. The file path is the URL slug — no CMS or database required.
→ See the Blog Implementation Guide for authoring instructions, frontmatter schema, and MDX component reference.
New to FlutterInit? Start with the Getting Started Guide.
| Guide | Description |
|---|---|
| Getting Started | From download to first successful flutter run |
| Configuration Reference | Every project option explained in detail |
| Generated Output Reference | Understanding the scaffolded folder structure |
| Architecture Overview | Under the hood of the Next.js / Handlebars engine |
| Handlebars Language Guide | Logic patterns for template contributors |
| Testing Guide | 2-layer validation strategy and tiered CI/CD pipeline |
| Blog Implementation Guide | Writing posts/guides, frontmatter schema, MDX components |
| Contribution Guide | How to add your own patterns |
We use GitHub Projects to track what's in progress and what's coming next.
👉 View the FlutterInit Roadmap
Want to contribute? Pick up any open issue labeled good first issue.
If you want to contribute to FlutterInit's engine or templates, you'll need to run it locally.
Clone & install:
git clone https://github.com/Arjun544/flutter_init.git
cd flutter_init
bun installStart the development server:
bun run dev
# or
npm run devOpen http://localhost:3000 to use the local dashboard.
Run tests:
# Unit + integration (Layer 1)
npm run test:layer1
# Dart validation on generated output (Layer 2)
npm run test:layer2
# Full pre-flight check
npm run test:preflight
# Generate guide file trees
npm run generate:guide-treesSee CONTRIBUTING.md and the Architecture Overview for how the Handlebars templating engine works.
The engine powering FlutterInit:
| Layer | Technology |
|---|---|
| Framework | Next.js 16 (App Router) + React 19 |
| Styling | Tailwind CSS 4 + shadcn/ui |
| Templating | Handlebars.js for dynamic Dart generation |
| Blog / Content | next-mdx-remote + Shiki + gray-matter |
| Animations | Motion (formerly Framer Motion) |
| Icons | HugeIcons & Lucide |
| Runtime | Bun (high-speed package management) |
| Testing | Vitest |
Arjun Mahar
Founder & Lead Architect
© 2026 FlutterInit Project. Released under the MIT License.