Manage your flavor in flutter

Exciting News : My First Flutter Package is Live on pub.dev! :tada:
After a lot of late nights and learning moments, I’m proud to share my first open-source Flutter CLI t


ool:

:package: flutter_flavor_manager

It’s a production-ready tool that helps developers set up and manage multiple environments (flavors) in Flutter projects the clean, automated, and scalable way.

:wrench: What It Does
With just a few CLI commands, it automatically:
Configures Android flavors in build.gradle or build.gradle.kts
Sets up iOS schemes and build configurations
Generates Dart entry points for each flavor
Adds VSCode launch configurations
Detects and merges existing flavors
All following SOLID principles and clean architecture
No more manual flavor setup headache just run the wizard and watch your project structure come to life.

:light_bulb: Why I Built It
As a Flutter developer, I realized that setting up multiple environments (dev, qa, prod, etc.) can be time-consuming and error-prone.
So I built flutter_flavor_manager to make this process automatic, reliable, and type-safe,Save time by automating Android & iOS flavor setup something every Flutter project can benefit from.

:handshake: Open Source & Contributions Welcome
It’s fully open source, and I’d love for the Flutter community to join in!
:open_file_folder: GitHub: GitHub - Abdallahabusnineh/flutter_flavor_manager: A comprehensive tool for setting up and managing flavors (environments) in Flutter projects for both Android and iOS. check the package on pub dev https://pub.dev/packages/flutter_flavor_manager
If you want to:
Simplify your multi-environment setup
Learn how to build a Flutter CLI tool
Or contribute to open-source development
Then check it out, test it, and let’s build something amazing together :blue_heart:

Congratulations, Abdallah!
That’s a fantastic milestone — your flutter_flavor_manager tool looks really promising and practical for production setups.
It explains how to safely default to a production flavor at build time and keep dev/staging code fully excluded from release builds.

Kudos again on your first open-source package — keep building amazing tools for the Flutter community! :rocket:
I still stick to my older approach for managing flavors, but you might find this reference helpful too:
:backhand_index_pointing_right: Stop Guessing: A Scalable Strategy for Flutter Environment Management - Hire Flutter™

Most developers still don’t fully utilize the --flavor flag or techniques like
import 'package:flutter/services.dart' show appFlavor;,
so this might give a few more ideas for keeping builds clean and environment-safe. :rocket:

1 Like

Thank you so much for your kind words! :folded_hands:

I’m glad you found flutter_flavor_manager practical for production setups. One of my main goals was indeed to make it easy to default to production safely while keeping dev and staging code fully isolated from release builds.

I really appreciate the reference you shared — the “Stop Guessing: A Scalable Strategy for Flutter Environment Management” article looks like a fantastic resource. I agree, many developers underutilize the --flavor flag and techniques like appFlavor, so it’s always great to see different approaches and ideas for keeping builds clean and environment-safe.

Your encouragement means a lot — I’m excited to continue building tools that make Flutter development smoother for the community!