In a brand new Android Studio project, the default configuration is called the default flavor, but you can define multiple flavors. Each results in creating a unique APK file. There are many reasons for creating multiple flavors: one flavor might be for more recent versions of Android, one might be a full version of the app, and one a demo version of the app; or one version might have code that’s unique to the Google Play store, and another version might use an API that’s unique to Amazon.
- [Instructor] In a brand new Android Studio project,…the default configuration is sometimes referred to…as the default flavor.…You can define multiple flavors,…and each flavor results in creating a unique APK file.…Flavors are defined in the app modules gradle build script.…If you know the syntax, you can…define the flavor right here.…But it's a lot easier to use the project structure dialogue.…As before, you can follow along with…any Android Studio project.…From the menu I'll select file, project structure.…
Then I'll select the app module,…and click on the flavors tab.…And again, default config shows up…as the one and only flavor.…Each flavor defines the properties listed…on the right side of the screen.…There's a minimum sdk version,…an application ID, a target sdk and so on.…Now, there are a number of different reasons…you might have to create multiple flavors.…For example, you might have one full version of an app…and one demo version.…Or one version might have code that's unique…to the Google Play store, and another might…
Author
David Gassner
Released
12/20/2016- Packaging apps in APK files
- Building a signed APK file
- Distributing through Google Play
- Adding app graphics
- Setting pricing
- Publishing the app
- Submitting an app to Amazon
- Tracking app use in Google Play and Amazon
