How to Achieve Near-Instant Android App Launch: Cold Start Optimization Guide

Background

During recent development we observed a noticeable waiting time when launching the app from the home screen, especially on low‑end devices. Cold‑start optimization became essential, so we investigated and applied solutions.

Buyer show (gif):

Taobao show (gif):

Android App Launch Process

The launch flow can be visualized as follows:

A complete cold‑start consists of:

Zygote Fork Process 
-> Application:attachBaseContext()
-> Application:onCreate()
-> MainActivity:onCreate()

These lifecycle callbacks are where most business code runs.

Cold‑Start Optimization Points

1. Reduce Time‑Consuming Operations Inside Lifecycle Methods

Application:attachBaseContext()

On Android 5.0 (API 21) and below, large DEX files can cause slow startup, ANR, or ClassNotFound errors. Splitting the DEX is a common solution, but it is not covered here.

Application:onCreate()

This method often initializes third‑party SDKs, which can block startup with Disk I/O or network requests. The following screenshots show the initialization time in debug and release builds.

Debug:

Release:

Notice the large discrepancy: ~1000 ms in debug vs ~300 ms in release. Always test performance in release mode.

Typical solutions:

Load non‑essential SDKs lazily.

Initialize SDKs that support multithreading on background threads.

MainActivity:onCreate()

Avoid heavy work or complex layouts here. One example of a costly line is shown below.

Instead of artificially delaying 1 second in the splash screen, move the navigation to onResume(), which runs when the activity is visible and interactive, saving about 500 ms.

2. Avoid Cold Start When Possible

App launch can occur in three ways:

ColdStart : Process is killed; the system must fork a new process and run full initialization.

WarmStart : Process remains in memory; the app is brought to the foreground, avoiding most initialization but still showing a blank screen until the first activity renders.

HotStart : Fastest, similar to returning to an app via the back button.

To reduce cold starts, prevent the app from exiting when the user presses the back button on the root activity. Adding the following code to the bottom‑most activity (usually MainActivity) achieves this:

The call moveTaskToBack(true) moves the task to the background instead of finishing the activity, mimicking the Home button behavior.

3. Optimize WindowBackground for Seamless Visual Transition

When the app process starts, Android first displays a background window (the “blank screen”) before the first activity draws. Using a custom windowBackground as a splash or branding image can mask this delay.

Steps:

Define a theme with a non‑transparent windowBackground and optional windowFullscreen.

Apply this theme to the launcher activity.

After the launch activity starts, switch back to the app’s regular theme.

With these steps the app appears to launch instantly.

Recommended Testing Tools

The total time from launcher click to first activity render measured on our device is 888 ms.

Time to Full Display

Android 4.4 (API 19) and above log the time needed to render an activity. Search for the log tag Displayed at verbose level to see your own and other apps’ launch times.

Hugo

Hugo prints execution time annotations. Add the annotation to any class or method to log its duration, including lifecycle callbacks.

Stetho

Stetho is a powerful debugging bridge for Android developers.