A Flutter utility to automate the creation of app flavors for Android, iOS, and macOS with configuration files.
Flutter Flavorizr is a Dart package that automates the creation and management of multiple flavors (build variants) in Flutter applications. It generates platform-specific configurations for Android, iOS, and macOS from a single YAML file, eliminating the need for manual setup of application IDs, bundle identifiers, icons, and third-party service integrations like Firebase.
Flutter developers building applications that require multiple environments (e.g., development, staging, production) or branded variants (e.g., white-label apps) across Android, iOS, and macOS platforms.
Developers choose Flutter Flavorizr because it drastically reduces the time and complexity of setting up flavors manually, provides a consistent configuration across all platforms, and offers extensible processors for custom integrations like Firebase and Huawei services.
A flutter utility to easily create flavors in your flutter application
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Generates consistent flavor configurations for Android, iOS, and macOS from a single YAML file, eliminating the need for error-prone manual setup across platforms.
Offers over 30 customizable instructions for assets, Firebase, icons, and IDE configs, allowing granular control over the flavorization process as documented in the README.
Seamlessly integrates Firebase and Huawei AppGallery Connect configurations per flavor, with clear YAML examples for multi-service apps in the documentation.
Creates dummy icons, launch screens, and adaptive icons for each flavor by default, streamlining development and reducing manual asset management.
Requires installation of Ruby, Gem, and Xcodeproj for iOS/macOS support, adding complexity and potential setup barriers, especially for teams not using these tools.
The README explicitly states it works better on new projects and may throw errors on existing ones due to assumptions about file structure, limiting retroactive adoption.
Due to a Flutter SDK bug, macOS flavors cannot be run from the terminal without applying a workaround build setting, adding friction to the development workflow.