kksimp/Mac.apk

Mac.apk is worth a look if a specific Android app has no Mac equivalent and you own an Apple Silicon Mac on a very new macOS. It works today for many of the 71 apps the author tested by hand, but it is explicitly alpha software with a hard OS floor and no Google Play services.

The problem

You want one Android app — a game only released on mobile, a store or launcher, or an Android TV app — on your Mac. The usual route is an emulator or a virtual machine, which means booting a whole Android system, sharing a GPU awkwardly, and running the app a layer removed from macOS. Mac.apk changes that step: you install the app, it becomes an ordinary macOS process, and it gets a Dock icon, windows with a back button, resizing and rotation, and light/dark switching. The first launch of an app is slow while Mac.apk prepares it, but later launches are fast.

What's different

Rather than running Android in a box, the project reimplements the Android framework, a native runtime, an arm64 loader and Bionic shim, and an ARM32 recompiler, so apps execute on the CPU and draw through the Mac's GPU. The README states there is no emulator, VM or Linux kernel underneath. That is what produces the native-feeling windows and keyboard support for Android TV apps.

The cost is compatibility. Google Play services and other Google infrastructure are not part of this; a commenter on the launch thread argued this would limit usefulness, with MicroG or custom-ROM-style workarounds suggested in replies, and the README points to app stores such as Aurora. The other cost is honesty about maturity: the compatibility list records 58 fully playable, 10 partly working and 3 not yet working out of 71 tested apps. That is a curated list, not a promise for the app you care about.

Who should try it

Good fit: an Apple Silicon user on macOS 26.4 or newer who wants one specific Android game or TV app and is comfortable checking the compatibility list and its known issues before installing. One commenter described using the Android version of Minecraft to join Bedrock players, which illustrates the niche case where a platform-exclusive mobile app is the whole point. Poor fit: anyone who needs Google-account-dependent apps to just work, anyone on Intel, and anyone who wants a set-and-forget environment. App data persists after you drag an app to the Trash; the documented Uninstall action in the Mac.apk window is what cleans it up while optionally keeping saves.

Requirements and limitations

The hard floor is macOS 26.4 (Tahoe) or newer on any Apple Silicon Mac; macOS 27 works from v1.0.1702, and Intel Macs are not supported. Budget about 280 MB for Mac.apk plus roughly 1.5 to 3 times each APK's size on disk, and expect the first launch of a large app to take up to a minute. The README calls the project alpha, with some apps running beautifully, some partially and some not at all, and it links to per-release known issues and a reporting path that includes app logs. The distribution is signed and notarized, and installation is a disk image from Releases; the wiki covers installation, app stores and managing apps. The project is AGPL-3.0 with a separate commercial license, and it carries a pump.fun token that the README says unlocks nothing in the app.

A 2026-10-20 comment by irskep complained that app data was stored inside the .app file; a reply the same day noted this had moved to ~/Library/Application Support/MacApk/<package> in the newest release, which matches the current README, so the complaint is already addressed.

HotRepo's take

The only dated signal is a weekly Java board rank of #15 with +2,404 stars for the week ending 2026-10-27; there is no daily-board history, so persistence cannot be judged from HotRepo's data. The 348-point, 194-comment HN thread on 2026-10-19 shows interest, not consensus. Before spending time, check your specific app against the compatibility list and the release's known issues.