Mac.apk runs Android apps natively on Apple Silicon Macs, no emulator required

An Android runtime built directly on macOS

Mac.apk, an alpha-stage project published on GitHub and recently surfaced on Hacker News's front page, runs Android applications natively on Apple Silicon Macs — without an emulator, a virtual machine or a hidden Linux layer.

According to the project's documentation, Android apps launched through Mac.apk behave like ordinary Mac programs: they run as standard macOS processes, draw using the Mac's GPU and execute at native CPU speed. Each app gets its own Dock icon and window — including a back button placed next to the usual traffic-light controls — resizes and rotates like any Mac window, and follows the system's light and dark modes.

The distinctive part is what is absent. Nothing boots a copy of Android in the background, no Linux kernel runs beneath the surface, and no instructions are translated one at a time. Instead, the software implements the Android application environment directly on top of macOS. The repository holds a reimplementation of the Android framework, a native runtime, an arm64 loader paired with a Bionic shim, an ARM32 recompiler and the macOS application itself. It also bundles established open-source components to bridge gaps: ANGLE, MoltenVK and the Vulkan loader for graphics, Capstone, libpng, libvpx, stb_vorbis, Bouncy Castle and a JRE built from OpenJDK, alongside Android platform resources compiled from AOSP source.

Requirements and everyday use

The requirements are narrow: macOS 26.4 (Tahoe) or newer — macOS 27 is supported starting with build v1.0.1702 — and any Apple Silicon Mac. Intel machines are not supported. The tool itself takes about 280 MB of disk space, and each installed app occupies roughly 1.5 to 3 times the size of its APK.

Installation is conventional for the Mac: the release download is signed and notarized by Apple, so it opens normally. You drag it into Applications, install the bundled runtime from inside the app, associate the file types, and then double-click an APK in any supported format (.apk, .apkm, .xapk, .apks, .apkx). The first launch of an app can take up to a minute for a large package while Mac.apk prepares it; later launches are fast.

One trap is worth knowing about. An Android app's saved data lives inside its .app bundle, so dragging the app to the Trash deletes its saves. The project advises uninstalling through its own control panel instead.

Compatibility is the open question

The README is candid that this is early software: some apps work well, some work partially and some do not run at all yet. The project maintains a hand-tested compatibility list and a known-issues page for the current release, v1.0.2237, and says the situation improves with each build.

Two product decisions stand out. Mac.apk serves no ads and supports no in-app purchases, by design. And publishers who want to discuss a partnership — or would rather their app not run on the platform at all — are invited to contact the developer.

A security model closer to the Mac than the phone

The project's documentation is unusually direct on this point: an Android app running through Mac.apk executes as ordinary native code with the permissions of your macOS user account. There is no phone-style sandbox around it, so an APK can read and write your files just like any Mac program you launch yourself. Voltare, the entity behind the project, says it cannot test, audit or vouch for third-party APKs, and advises treating an APK exactly as you would any program downloaded and run from the internet.

Licensing

Mac.apk is open source under the GNU AGPL v3.0. A separate commercial license is offered to companies that want to ship or offer the software without the AGPL's terms; using the official app itself is free.

Why it matters

Running Android software on a Mac has historically meant emulation or virtualization, both of which carry overhead and sit awkwardly on the desktop — apps trapped inside a simulated phone screen with sluggish graphics. A runtime that treats Android apps as first-class macOS processes is the same trick Wine pulled off for Windows applications on Unix-like systems: skip the emulation, implement the platform, and let the apps integrate with the host. If Mac.apk's compatibility matures, it opens a very large software catalogue to Mac users who currently have no good route to it. Two caveats temper the promise: it is alpha software with hit-or-miss app support, and its security posture is deliberately looser than a phone's, shifting trust decisions onto whoever installs each APK.