Flutter Flavors Setup

Automate Flutter flavors setup for dev, staging, and production environments.

11|2|Updated Oct 15, 2025
One-click install
npx skills add https://github.com/Kandil7/prprompts-flutter-generator --skill flutter-flavors-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Flutter Flavors Setup
Source: https://github.com/Kandil7/prprompts-flutter-generator/tree/main/.qwen/skills/development-workflow/flutter-flavors
Command: npx skills add https://github.com/Kandil7/prprompts-flutter-generator --skill flutter-flavors-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the complex setup of Flutter flavors, allowing you to easily manage different app versions (development, staging, production) with distinct API endpoints, app names, icons, and configurations. It eliminates manual configuration errors and ensures a consistent, robust multi-environment setup, saving hours of tedious platform-specific configuration.

Core Features & Use Cases

  • Multi-Environment Configuration: Set up separate environments for dev, staging, and production with unique API URLs, analytics settings, and logging levels.
  • Platform-Specific Setup: Configures both Android (product flavors, build variants) and iOS (Xcode build configurations, schemes, Info.plist) automatically.
  • Automated Build Scripts: Generates shell and batch scripts for consistent building and running of each flavor, simplifying CI/CD integration.
  • Use Case: Quickly set up your Flutter project to have a "MyApp Dev" version pointing to a test API, and a "MyApp" production version pointing to the live API, both installable on the same device, without manual Xcode or Gradle edits.

Quick Start

Set up standard dev, staging, and production flavors for your Flutter project. @claude use skill development-workflow/flutter-flavors

Frequently Asked Questions about Flutter Flavors Setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Flutter flavors for multiple environments?

Flutter flavors automate configuration of dev, staging, and production builds with distinct API endpoints, app names, and bundle IDs. This Skill configures Android product flavors, iOS Xcode schemes, and generates build scripts to manage all three environments from a single codebase, eliminating manual platform-specific setup.

Can I run different Flutter app versions on the same device?

Yes. Flavors create separate app identities with unique bundle IDs and display names, allowing dev, staging, and production versions to coexist on one device. Each flavor points to its own API endpoint and configuration, enabling parallel testing without uninstalling.

What does Flutter flavor configuration include for iOS and Android?

iOS configuration applies Xcode build schemes and modifies Info.plist per flavor. Android setup creates product flavors and build variants tied to Gradle. Both platforms receive environment-specific API URLs, analytics flags, logging levels, custom icons, and entry points (main_dev.dart, main_staging.dart, main_production.dart).

How do Flutter flavors integrate with CI/CD pipelines?

Automated build scripts for each flavor simplify CI/CD integration, enabling consistent builds across environments. Scripts handle platform-specific compilation and packaging, reducing manual intervention and configuration drift in deployment workflows.

Do I need to manually edit Xcode and Gradle for each flavor?

No. This automation eliminates manual Xcode and Gradle edits by programmatically generating schemes, build configurations, product flavors, and variants. Configuration is centralized and version-controlled, reducing setup errors and maintenance overhead.

What prerequisites does Flutter flavor setup require?

You need an existing Flutter project with iOS and Android platforms configured. Basic knowledge of Flutter structure, Gradle (Android), and Xcode (iOS) helps, though the automation handles most platform-specific complexity.