The App1 in the string tag is the app name of the first flavor. In the values folder create a file called strings.xml with the contents as below. In the new folders App1 and App2 create folder named res and within it theįolder named values. To have different App Names for different flavors, in /android/app/src/main/ change from android:label=”your App Name” to App1 and App2 folders in /android/app/src/, use the below image for reference. Go to adle file inside /android/app/ director and add the following configuration shown in the below image.

With regards to android, the product flavors are defined in the app gradle module.

They address the issue of having a separate project code base for each version of the app.They make the code much easier and faster to navigate through as everything related to the specific product flavor would be kept in their corresponding folders.But in addition, admin users need to have access to the statistics page and be able to see the app with different colors and resources while making sure that your admin app’s analytics are not mixed with its custom app. A scenario in which the admin user app should have all the functionalities as that of the customer app.When you wish to address the issue of having a separate project code for each version of the app while still having one project code.Suppose you have a paid and a free version of the app, you can limit the features in the free app and expose all the other features in a paid version for the app.Let’s look into more information about how developers from App Development Company in Bangalore enable flutter flavours in their codebase. Flavors allows us to create multiple versions or variants of our app with the same codebase making it easy to create and test features without the risk of destroying the production data.

When developing apps, it is very important to separate out development and production environments.

Build variant in android studio