Hi Arjun,
I recently came across FlutterInit, and I’m genuinely impressed by the concept and overall direction of the project. I think the Flutter ecosystem really needs a way to simplify and standardize Flutter project setup.
Your project actually inspired me to experiment with building a CLI-first workflow around FlutterInit, mainly to make the generation/setup process work directly from the terminal without depending on the web UI flow.
So I built a FlutterInit CLI package that currently supports:
doctor command for Dart/Flutter + generator health checks- interactive
create workflow similar to the web flow
- scaffold ZIP generation + safe extraction/apply pipeline
- conflict-aware apply system with staging + overwrite planning
- automatic pubspec sanitization/fixes
- asset/env folder generation helpers
- gitignore correction helpers
- scaffold caching
- automated tests for validators, extraction logic, pubspec fixes, env/assets handling, etc.
The goal was to make FlutterInit usable as a complete local-first developer workflow while keeping compatibility with the existing generator approach. So, Platform is what I thought the current FlutterInit generator is missing, which is why I implemented it at the package level only, just to keep your actual generator flow safe.
I’d genuinely love to collaborate and contribute to the project if you think this direction aligns with your vision for FlutterInit. Even if parts of the implementation need restructuring or redesign, I’d be very happy to adapt things properly to fit the project architecture and roadmap. You can see a quick demo of the CLI package here
Really appreciate the work you’ve already done here — the concept is seriously promising.
Would love to hear your thoughts.
Hi Arjun,
I recently came across FlutterInit, and I’m genuinely impressed by the concept and overall direction of the project. I think the Flutter ecosystem really needs a way to simplify and standardize Flutter project setup.
Your project actually inspired me to experiment with building a CLI-first workflow around FlutterInit, mainly to make the generation/setup process work directly from the terminal without depending on the web UI flow.
So I built a FlutterInit CLI package that currently supports:
doctorcommand for Dart/Flutter + generator health checkscreateworkflow similar to the web flowThe goal was to make FlutterInit usable as a complete local-first developer workflow while keeping compatibility with the existing generator approach. So, Platform is what I thought the current FlutterInit generator is missing, which is why I implemented it at the package level only, just to keep your actual generator flow safe.
I’d genuinely love to collaborate and contribute to the project if you think this direction aligns with your vision for FlutterInit. Even if parts of the implementation need restructuring or redesign, I’d be very happy to adapt things properly to fit the project architecture and roadmap. You can see a quick demo of the CLI package here
Really appreciate the work you’ve already done here — the concept is seriously promising.
Would love to hear your thoughts.