be deployed § Personal projects § developer's workstation § Industrial projects with end users § Development environment § Testing environment § Production environment PAGE 4
flavor is a product for itself § Each flavor has different environments § Set different URL for api calls, icons and names § The concept of flavors is from Android apps § Flavors are also possible for iOS apps PAGE 5
Mainly for deployment § The behavior and the visualization don’t change Flavor § One source code with multiple apps § Use different app's name, icons and package name § Each flavor can be an own product PAGE 6
AppConfig class to store the configuration, such as flavor name, API endpoint … § Create main.dart file for each flavor § main_cactus.dart § main_leaf.dart § Adjust the main_common.dart with appConfig parameter PAGE 12
are the same for all flavors § Different app ids for different flavors § Add app icons for each flavor § Run Flutter § flutter run -t lib/main_dev.cactus --flavor cactus § flutter run -t lib/main_leaf.dart --flavor leaf PAGE 16