It compiles app resources and source code and packages them into APKs for testing, deployment, signing configuration, dependency management, and distribution. This can be achieved using the Android build system. We all need our Android project code resources well configured, organized, and accessible to the users without modifying the core source files. In the code, it is the same as to how to pulling in the string resources, here is the example of setting a TextView with a string from the strings.xml, it will get the appropriate strings.xml according to the selected build variant.In this article, we are going to learn about the Android build System-Gradle, and how it helps to configure different aspects of your build i.e Build types, build variants, Product flavor, dependencies, and more. Let’s create a strings.xml in each of the following path with different values assigned to the string variable build_type and api_domain. ProguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' StoreFile file('/path/to/the/android/project/folder/app/debug.keystore') update this path to your keystore file path Here is the an example configuration for defining different build types, debug, dev, staging and release.

This can be done by defining different build types in the Android app build gradle file. During development, we might need to configure the code to use different api endpoint, or other environment variables for dev, staging and prod builds.

Android build variants