{"id":9477,"date":"2023-07-03T10:08:08","date_gmt":"2023-07-03T10:08:08","guid":{"rendered":"http:\/\/goldenmace.com\/blog\/?p=9477"},"modified":"2023-07-03T10:16:26","modified_gmt":"2023-07-03T10:16:26","slug":"avoiding-cold-starts-and-working-with-multiple-flavors","status":"publish","type":"post","link":"https:\/\/goldenmace.com\/blog\/avoiding-cold-starts-and-working-with-multiple-flavors\/","title":{"rendered":"Avoiding cold starts And Working with Multiple Flavors"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Cold starts<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tA cold start refers to an app\u2019s starting from scratch: the system\u2019s process has not, until this start, created the app\u2019s process. Cold starts happen in cases such as your app\u2019s being launched for the first time since the device booted, or since the system killed the app. This type of start presents the greatest challenge in terms of minimizing startup time, because the system and app have more work to do than in the other launch states.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tWhy we should avoid using Splash Screens on Android, arguing that they hurt the user experience, increase the size of the application, etc.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tThe key is creating a custom theme that overrides\u00a0android:windowBackground<\/strong>, then replacing that custom theme with your standard theme before calling super.onCreate().\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tAssuming you have a theme called AppTheme, your launcher theme would be:\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

themes.xml\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<style name=\u201dAppTheme.ColdStart\u201d><\/p>

<item name=\u201dandroid:windowBackground\u201d>@drawable\/splash_bg<\/item><\/p>

<\/style><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tPlace \u201csplash_bg\u201d inside drawable folder:\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

splash_bg.xml<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<layer-list<\/p>

xmlns:android=\u201dhttp:\/\/schemas.android.com\/apk\/res\/android\u201d<\/p>

android:opacity=\u201dopaque\u201d><\/p>

<!\u2013 The background color, preferably the same as your normal theme \u2013><\/p>

<item android:drawable=\u201d@android:color\/white\u201d\/><\/p>

<!\u2013 Your product logo \u2013 144dp color version of your app icon \u2013><\/p>

<item><\/p>

<bitmap<\/p>

android:gravity=\u201dcenter\u201d<\/p>

android:src=\u201d@drawable\/new_logo\u201d\/><\/p>

<\/item><\/p>

<\/layer-list><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tThe easiest way to transition back to your normal theme is to call setTheme(R.style.AppTheme) before super.onCreate() and setContentView():\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

MainActivity.java<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

public class MainActivity extends AppCompatActivity {
@Override
protected void onCreate(Bundle savedInstanceState) {
\/\/ Make sure this is before calling super.onCreate
setTheme(R.style. AppTheme);
super.onCreate(savedInstanceState);
\/\/ \u2026
}
}<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Flavors<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tFlavor is a very powerful feature available in the Android gradle plug-in that allows us to manage different \u201cflavors\u201d of an application.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tIt\u2019s important to understand why and when you might need multiple flavors. As an app developer, you would like to release a given app using a new brand name, logo and\/or theme, along with some minor feature differences. Using this to maintain app very quickly.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tThe other way to create separate projects for each version, which is far from ideal, and will lead to errors and projects not having the complete new changes and fetch issues.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tUsing multi flavors developer can easy way to build and maintain different version of app.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tAnother very important concept regarding building android apps, called \u201cbuild types\u201d. The default build types are debug and release.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tIf you have create two flavors, called free and promo, and two build types called debug and release, the Build Variants will be:\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t