LiteLDev/LeviLaunchroid

If you play Minecraft Bedrock on Android and want several game versions, accounts or modded module setups side by side, LeviLauncher is aimed at exactly that workflow. It is not for people happy with a single Play Store install.

The problem

On Android, the Play Store gives you one Minecraft Bedrock installation, one active account and one data set. Players who want to test a new version without losing a world, keep separate accounts, or load native SO modules usually end up reinstalling, juggling backups, or moving files by hand. LeviLauncher changes the entry point: you import an official APK into the launcher, and each managed version runs with its own configuration and game data. Worlds and resource packs can then be imported, exported and backed up from the launcher rather than through a file manager.

What's different

The core mechanism is installation-free launching from an imported official APK, combined with version isolation. That separation is the practical benefit: experimenting with a different game build or a module loadout does not have to overwrite the setup you play on. A second feature, loading external native SO modules, is what lets people extend or tune Minecraft without editing the base installation, and the README frames this as extending features and performance. The launcher also keeps multiple Xbox accounts switchable in one place, which matters to households or players with separate profiles.

The trade-off is that this is a wrapper around the official game, not a replacement for it. You still need a licensed copy from Google Play, and the prerequisites say the official app must be installed for the launcher to work properly. Isolation also means duplicate game data: the README asks for at least 2 GB free storage, and recommends 5 GB, so keeping many versions and module sets is a storage decision as much as a convenience one.

Who should try it

A good fit is an Android player who already owns Bedrock and wants two or three versions available at once, or who wants to try SO modules without disturbing a main world. It is also reasonable for someone managing several Xbox accounts on one device. A poor fit is a casual player with one account and one version who just wants to launch the game; the added import step and storage overhead buy little. Anyone on a 32-bit device or below Android 9 is outside the documented requirements regardless of interest. The manual route is downloading the release APK and enabling installation from unknown sources; developers who want to build it need Android Studio, JDK 21 and SDK API 28 or higher, per the development setup.

Requirements and limitations

The README is explicit: Android 9.0 (API 28) or higher, ARM64 (v8a), at least 1 GB available RAM with 2 GB or more recommended, and 2 GB free storage with 5 GB suggested for stability. A licensed Google Play copy of Minecraft is mandatory, and the official app is listed as an installation prerequisite. The launcher is installed from the releases page with unknown sources enabled, so it sits outside Play Store updates and you are responsible for keeping it current.

Upkeep is the part to think about before adopting: multiple isolated versions mean multiple sets of game data to back up and clean up, and imported APKs need re-importing when you move to a new game build. SO modules come from outside the project, so their compatibility with a given Minecraft version is something you have to track yourself. The README does not detail how module conflicts or version migrations are handled.

HotRepo's take

HotRepo's stored coverage begins on 2026-10-24, and the only comparable signal is a weekly Java board position of #13 with +22 stars on 2026-10-25. With no daily-board history, persistence of interest cannot be judged. The project is a focused niche tool for licensed Bedrock players, and the thing worth verifying before committing is how its documentation handles version migration and module compatibility across updates.