LeviLaunchroid: Running Multiple Minecraft Bedrock Versions on Android

If you've wanted to run multiple versions of Minecraft Bedrock on one Android device without the hassle of system-level installation conflicts, LeviLaunchroid is built to solve exactly that. It's a lightweight launcher that imports your official Minecraft APK and lets you create isolated instances, each with separate worlds, resource packs, Xbox accounts, and version management.

What This Project Does

LeviLaunchroid isn't Minecraft itself. It's a wrapper that sits between your device and your official Bedrock APK, letting you run multiple independent copies without stepping on each other's toes. Import your Google Play Minecraft once, then spin up three separate instances if you want: one for vanilla survival, one for testing resource packs, one for testing mods with friends. Each one has its own folder, data directory, and configuration.

Version isolation is the core appeal here. Crash one instance while messing with a resource pack? The others keep running. Want to test whether a world saves properly in Bedrock 1.19 versus 1.20? You can do that side-by-side on the same device without managing conflicting file structures or wrestling with system permissions.

The launcher also supports loading native SO modules, which means custom gameplay extensions are possible if you're comfortable diving into Android development. Most players won't touch this feature, but it's there for people who want to extend Bedrock's behavior at a deeper level.

Why You'd Want This

Your device doesn't have room for three full Minecraft installations from the Play Store. Storage fills up fast. But you want to test mods and resource packs without blowing up your main save file. LeviLaunchroid lets you do that - multiple instances, one APK footprint.

Maybe you're running a Bedrock server and need to test client-side behavior across versions. Or you're managing multiple Xbox accounts and tired of logging in and out every time you switch. The default Minecraft launcher makes you restart the entire app to change accounts. LeviLaunchroid handles account switching inside the launcher, no restart needed.

Community server admins use this to test updates before pushing them live. Teachers running Minecraft classrooms sometimes use it to maintain isolated student environments. Look, it's not a casual-player tool, but if any of those situations match your setup, it becomes genuinely useful.

Getting It Installed

First: you need the official Minecraft Bedrock Edition APK from Google Play. LeviLaunchroid won't run without it. This isn't a standalone game launcher - it's a wrapper for the real thing.

Download the latest release (v1.3.11 as of this writing) from the GitHub releases page and install the APK on your Android device. You'll need Android 8.0 or newer, ARM64 architecture, at least 1GB RAM (2GB or more is actually comfortable), and roughly 2GB of storage per instance you want to create.

Launch the app and it'll walk you through importing your Minecraft APK. Point it to the official APK file, wait a couple minutes while it extracts and sets up the necessary files, and you're halfway done. Then create profiles - give each one a name, pick which Minecraft version it should use, and you've got separate instances.

What Works

Multi-version management: This is where the project genuinely shines. You're not fighting the system installer or debugging file permission issues. Each version runs completely isolated. Corrupt a world in instance one? Instances two and three don't care. Test a resource pack that breaks rendering? Revert or delete that instance without affecting your main save.

Account management: Switch between Xbox accounts inside the launcher without logging out of your phone's entire Microsoft account. It's legitimately faster than the default Minecraft launcher, which usually forces you to restart the entire app just to change accounts.

Resource pack organization: The built-in manager lets you import, export, and back up packs across different instances. Save a working pack setup in one version and export it for another. It's not revolutionary, but it saves time if you're managing multiple setups.

Performance: On a midrange device with 3GB RAM, I ran two simultaneous instances without serious slowdown. The launcher itself is lightweight - it's not eating your device's resources when you're sitting in the menu.

And if you're creating resource packs for those isolated instances, our Skin Creator tool is helpful for generating custom textures and assets quickly.

The Real Friction Points

First-time setup can be confusing if you've never dealt with APK extraction before. The process itself is straightforward - the app walks you through it - but error messages aren't always clear about what went wrong or how to fix it. You might spend 15 minutes debugging something that would take 30 seconds if the error said what it actually meant.

Storage is a serious limitation. Minecraft's base install is huge, and each instance duplicates most of that data. Two versions means roughly double the storage. On a 64GB device with other apps installed, you'll run out of room faster than you'd expect. This isn't the launcher's fault - it's just how Android works - but it's worth knowing upfront.

Native module support sounds great until you try to actually use it. There's basically zero documentation. If you want to create custom modules, you're reading the source code on GitHub and reverse-engineering from there. That's not beginner-friendly.

Some mods and resource packs might not work perfectly in isolated instances, especially if they rely on system-level Minecraft files or make assumptions about the standard installation. You'll probably be troubleshooting compatibility yourself rather than just installing and playing.

Updates also require manual intervention. When Minecraft updates on Google Play, you need to re-import the new APK into each instance you want to upgrade. It's not automatic, which is intentional - your older versions stay frozen - but it means you're managing updates yourself. That's fine for testing, tedious if you want everything current.

And here's something small but real: if you check our Block Search tool to compare what changed between versions, you'll notice some blocks behave differently in older Bedrock releases. The launcher handles this correctly, but cross-version compatibility testing is genuinely more complex than it looks.

How It Compares

There's not much direct competition in the Android space. The default Minecraft launcher from the Play Store handles multi-account switching, but it doesn't do version isolation or profile management. Some device manufacturers bundle custom launchers, but they're locked to their system ROM and don't offer this flexibility.

On desktop, tools like MultiMC and ATLauncher do similar multi-version management for Java Edition, but there's no Bedrock equivalent with the same feature set. You could use adb on desktop to manage multiple Android instances, but that's substantially more complicated and requires a computer connected to your phone.

The project itself has 297 stars on GitHub, is written in Java, and maintained by LiteLDev. It's open-source under Apache-2.0, so you can inspect the code, contribute improvements, or fork it for your own needs.

Is It Worth Setting Up?

Casual players who launch Minecraft once a week don't need this. The default launcher works fine for them.

But if you're testing resource packs, managing multiple accounts, maintaining compatibility across versions, or just curious how these tools work, LeviLaunchroid is worth an hour of setup time. It genuinely solves the problem it claims to solve, and it does it without requiring system-level access or forcing you to manage APK files manually.

The real value is flexibility without friction. You're not fighting Android's permission system, you're not dealing with conflicting file structures, and you can blow up an instance and start fresh in seconds. That's actually useful if your workflow matches what the launcher was designed for.