I have been running some conversion and retention tests around Mojo Launcher, an Android launcher project lately, and our team has run into a frustrating bottleneck during the initial onboarding flow. A noticeable chunk of new installs abandon the app right at the system permission prompt where users are asked to set it as their default home screen, which heavily skews our early engagement metrics.
To make matters more complicated, newer OS updates seem to aggressively kill background processes unless users manually whitelist the app in their battery settings. This creates unexpected glitches and occasionally resets users back to their native system layout, leading to friction and negative early impressions. For anyone working with utility or system customization tools, what onboarding strategies have you used to clearly guide users through these mandatory platform hurdles without completely destroying your first-session completion rates?
For context, Mojo Launcher is built for running Minecraft Java Edition on Android phones and tablets. It is based on PojavLauncher and supports mods through Forge, Fabric, and OptiFine, plus customizable touch controls. I would be curious whether the same onboarding friction applies to game-focused launchers, where users need to understand both home-screen setup and game-specific configuration before they can get value.