Runs Android apps as Windows desktop applications

RoutineMiku/apkstart: Runs Android apps as Windows desktop applications

Nov 15, 2026, 7:32 AM UTC
•Anita Farkas
•5min read

Repos in this post

Advertisement
Advertise on LavX NewsSee options

ApkStart runs Android apps on Windows in separate desktop windows, with app icons, shortcuts and shared files, so you can use them from your PC desktop.

ApkStart is a Windows application launcher that installs Android APK files and opens each app in its own desktop window. It manages an Android runtime and adds familiar Windows entry points, including app icons, shortcuts and Start menu search.

Screenshot: the project’s README on GitHub

What it is

ApkStart runs Android apps on a Windows desktop. You can open an APK file for installation, then launch the app from its own desktop icon or Start menu shortcut. ApkStart gives each app a separate window with its name and icon, so it appears alongside the other software on your PC. This setup suits people who want to use Android apps on Windows without managing a separate emulator window for each launch.

The project handles the work between an APK file and a Windows app window. It reads package details, including the app name, icon and launch entry, then installs and starts the app in Android. ApkStart also creates shortcuts that point to the installed app. You can search for an app by name in the Start menu, or open its desktop icon to launch it without first opening ApkStart’s main screen.

How it works

ApkStart uses Android Emulator, Android system files and adb to run Android apps. The project manages those runtime components itself, downloads and checks them, and stores them under the Windows user profile. When you launch an app, ApkStart starts the runtime if it needs to, then asks Android to open the app’s launcher entry. It places the emulator window inside the app window and changes the title, icon and size to match the app.

The project keeps Android’s base system separate from each app’s writable data. Apps share the base system, while ApkStart maintains user data and quickboot snapshots for the Android environment. When you close the last app window, ApkStart can save the runtime state for a later session. It can also prepare Android in the background while ApkStart waits in the system tray, so the runtime has a chance to start before you open an app.

Diagram: Drawn by LavX News from the project’s README. Not an official diagram.

Key features

ApkStart can associate APK files with its installer, extract app icons and create Windows shortcuts. It also supports split Android packages, which it installs as a group. App windows keep a portrait layout by default, and you can resize them or switch to fullscreen. ApkStart remembers window dimensions for each app. The taskbar groups windows by app, which gives you a way to distinguish the Android apps you have open.

A shared folder connects Windows files with an Android directory. ApkStart syncs files between the two locations, so an Android app can create a file that you can open from Windows. The runtime uses the PC’s network connection through QEMU’s user-mode networking. ApkStart says this setup avoids adding a Windows network adapter. The project also grants requested runtime permissions and can retry an app after a crash, with a data reset when needed.

Getting started

You can choose an installer package that includes the Android runtime, or a portable package that fetches the runtime during its first launch. The installer expands the system image into your user folder on its first run. The portable option keeps runtime files and installed apps outside the program folder, so replacing the program does not remove them. ApkStart also offers adencies, start the app and package a portable copy

Who it is for

ApkStart targets Windows users who want Android apps in a desktop workflow. A shortcut can open an app as its own window, while Start menu search and taskbar grouping help users find and switch between apps. The approach can also help people who move files between Android apps and Windows: the shared folder syncs files across the two systems without requiring an Android app to mount a Windows folder.

Developers can build ApkStart fromready have an Android runtime can configure ApkStart to connect to it, though the project also manages a runtime of its own. People with apps that require ARM libraries can enable the project’s ARM compatibility setting. The README cautions that some apps may still fail when they check for hardware such as sensors or a baseband

What’s new

The release notes say the latest update adds orientation controls and a game or low-latency mode for FPS. Rotation changes the emulator’s display dimensions and restarts it. The notes also say ApkStart saves the selected orientation in settings, locks rotation to keep the image upright and switches the physical panel to landscape when you use fullscreen. The update removes a startup option that had overridden panel settings.

Limitations and roadmap

ApkStart builds on Android system components and QEMU rather than implementing its own hypervisor. The project focuses on connecting those components to Windows desktop behavior, including app windows, shortcuts and file sharing. Its shared folder syncs files between Windows and Android; it does not mount the Windows folder inside Android. That distinction matters if an app expects direct access to a mounted directory instead of files copied through the sync process.

Some Android apps may reject an emulated device or depend on hardware that the PC does not provide. The README says apps with ARM-only native libraries can use the ARM compatibility setting, while apps that check for real sensors or baseband hardware may remain unsupported. ApkStart can show an explanation when installation or startup fails, but those checks still limit which apps users can run.

Sources: RoutineMiku/apkstart · MIT · release v0.4.3

Figures come from the GitHub API, read at 07:20 UTC on 15 November 2026. Seven-day star counts are approximate.