How to Implement Google Play In-App Updates: Flexible vs Immediate Workflow

Why Traditional Update Prompts Fail

Displaying custom alert dialogs prompting users to visit the Google Play Store disrupts the user experience. Users often dismiss dialogs, resulting in fragmented user distributions running outdated API contracts. The Google Play In-App Updates API lets users download and install updates without leaving your app.

Flexible vs. Immediate Updates: Which One to Choose?

• Immediate Flow: A full-screen blocking UI used for critical security patches or breaking backend API migrations. The user cannot use the app until the update installs and restarts.
• Flexible Flow: Background downloading used for standard feature rollouts. The user continues interacting with the app while the update downloads, and a snackbar prompts them to restart when ready.

Implementation Code in Kotlin

class MainActivity : AppCompatActivity() {
    private lateinit var appUpdateManager: AppUpdateManager
    private val UPDATE_REQUEST_CODE = 5001

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        appUpdateManager = AppUpdateManagerFactory.create(this)
        checkForAppUpdate()
    }

    private fun checkForAppUpdate() {
        val appUpdateInfoTask = appUpdateManager.appUpdateInfo
        appUpdateInfoTask.addOnSuccessListener { appUpdateInfo ->
            if (appUpdateInfo.updateAvailability() == UpdateAvailability.UPDATE_AVAILABLE
                && appUpdateInfo.isUpdateTypeAllowed(AppUpdateType.FLEXIBLE)
            ) {
                appUpdateManager.startUpdateFlowForResult(
                    appUpdateInfo,
                    AppUpdateType.FLEXIBLE,
                    this,
                    UPDATE_REQUEST_CODE
                )
            }
        }
    }
}

Implementing In-App Updates significantly reduces legacy version fragmentation across your user base.