Glonce

Mac.apk runs Android apps natively on Apple Silicon Macs, in alpha

toolsThe Glonce editorsHacker News🔥75Glonce rating75Impact60Novelty70Relevance80Surprise70Players20Credibility60
Mac.apk runs Android apps natively on Apple Silicon Macs, in alpha

Mac.apk is an alpha-stage macOS app from Voltare that, according to its GitHub README, runs Android apps natively on Apple Silicon Macs. The README's pitch is blunt: no emulator, no virtual machine, no Linux underneath. Instead, Mac.apk implements the Android application environment directly on top of macOS. Nothing boots Android in the background, no Linux kernel runs beneath it, and nothing is interpreted instruction by instruction.

The README says Android apps launch as ordinary macOS processes, draw through the Mac's GPU and execute on the CPU at native speed. They appear in the Dock, get their own windows with a back button next to the traffic lights, resize and rotate like any Mac window, and follow the Mac's light and dark mode.

The project is candid about its state. It is labelled alpha, "early software under active development", where some apps run well, some run partially and some do not run yet. The README calls it stable enough to use and says it improves with every build.

Setup has four steps. Download the disk image from the Releases page and drag Mac.apk into Applications (it is signed and notarized by Apple, so it opens normally). Open the app and click Install next to Runtime in the top left. In Settings, under File types, click Make Default and approve the macOS prompt. Then double-click any .apk, .apkm, .xapk, .apks or .apkx file, or drag it onto the Mac.apk window. The first launch of any app is slow, up to a minute for a large one, while Mac.apk prepares it; later launches are fast.

The repository holds everything that makes the app work: the Android framework reimplementation, the native runtime, the arm64 loader and Bionic shim, the ARM32 recompiler and the macOS app itself. Build and contribution instructions are in BUILDING.md and CONTRIBUTING.md, and the README says app reports are as useful as code. Bug reports go to an email address at voltare.us or the issue tracker, with the Mac.apk version, macOS version, the app and where it came from, what happened, and the log from ~/Library/Logs/macapk/.

On terms: Mac.apk serves no ads and supports no in-app purchases, by design. App publishers who want to discuss a partnership, or who would rather their app not run on Mac.apk, are invited to email. The software is open source under the GNU AGPL v3.0, with a commercial licence available for companies that want to ship or offer it without the AGPL's terms. Using the official app is free. The name and logo are covered separately in TRADEMARKS.md.

The README is also direct about security. An Android app under Mac.apk runs as ordinary native code with the macOS user account's permissions, and there is no phone-style app sandbox: it can read and write the user's files like any Mac app. Users are told to install only APKs they trust. The software is provided "as is" with no warranty, and Voltare says it cannot test, audit or vouch for any third-party APK. One practical warning: an app's saved data lives inside its own .app, so dragging it to the Trash deletes its saves; uninstalling should be done from the Mac.apk control panel.

Key facts

  • Mac.apk, from Voltare, is an alpha app that the README says runs Android apps natively on Apple Silicon Macs with no emulator, virtual machine or Linux underneath.
  • It reimplements the Android application environment on top of macOS; apps run as ordinary macOS processes, draw through the GPU and execute on the CPU at native speed, per the README.
  • Open source under the GNU AGPL v3.0, with a commercial licence for companies; using the official app is free, and it has no ads or in-app purchases.
  • Supports .apk, .apkm, .xapk, .apks and .apkx files; the first launch of an app can take up to a minute for a large one.
  • Android apps get no phone-style sandbox and run with the user's macOS permissions, so the README says to install only APKs you trust.

Why it matters

Running Android apps on a Mac usually means an emulator or a virtual machine. Mac.apk says it does neither: it reimplements the Android application environment on top of macOS, so apps run as ordinary macOS processes at native CPU speed. If that holds up, Android apps sit in the Dock and behave like Mac windows, without a booted Android system behind them. The whole stack is open source: the framework reimplementation, native runtime, arm64 loader, Bionic shim and ARM32 recompiler.

Who it affects

Owners of Apple Silicon Macs who want Android apps on the desktop are the target. Android app publishers are addressed directly too: the README invites them to email about a partnership, or to ask that their app not run on Mac.apk. Companies that want to ship or offer the software without the AGPL's terms can ask about a commercial licence. Contributors can help with code or with app compatibility reports.

How to use it

Download the disk image from the Releases page and drag Mac.apk into Applications. Open it and click Install next to Runtime. In Settings, find File types, click Make Default and approve the macOS prompt. Then double-click an .apk, .apkm, .xapk, .apks or .apkx file, or drag it onto the Mac.apk window. Expect a slow first launch, up to a minute for a large app. Uninstall apps from the Mac.apk control panel, not by dragging them to the Trash, because their saved data lives inside the .app. Using the official app is free. For bug reports, include the Mac.apk and macOS versions, the app and its source, what happened, and the log from ~/Library/Logs/macapk/, and look the log over before posting it publicly.

How solid is it

Everything here comes from the project's own README. The project calls itself alpha: some apps run well, some partially, some not yet. The speed and no-emulator claims are the authors' own. No version number or release date is given, and no benchmark figures beyond the claim of native-speed CPU execution. The README points to a compatibility list of apps tested by hand and a Known issues page, but their contents are not in the text. No independent reviews, user numbers or reactions are included.

Risks and caveats

The main risk is security. Android apps run as native code with the user's macOS permissions, with no phone-style sandbox, so they can read and write the user's files. The README says to treat an APK like any program you download and run yourself, and to install only APKs you trust. Voltare says it cannot test, audit or vouch for any third-party APK and disclaims liability for damages, data loss, malware, security incidents and copyright disputes. The software comes "as is" with no warranty. Trashing an app by dragging it deletes its saved data. Compatibility is uneven at this stage, and the AGPL v3.0 licence may matter to companies wanting to build on it.

“There is no phone-style app sandbox around it: it can read and write your files the same way any Mac app you run can.”

— Mac.apk README