Design Decisions

Design Decisions

A few things about Mac.apk surprise people. This page explains the reasoning behind them.

No emulator, no virtual machine

Emulators and VMs do work, but you pay for them. A whole Android system boots in the background, there's a disk image to look after and a separate desktop to switch into, and the app's code runs on a simulated processor. Mac.apk skips all of that and provides the Android app environment directly on macOS. An Android app becomes an ordinary Mac process: it starts quickly, runs at full speed and acts like a Mac app. How Mac.apk Works goes into more detail.

Apple Silicon only

Android apps are built for ARM processors, and so is Apple Silicon. Mac.apk runs their ARM code directly on the Mac's ARM chip. On an Intel Mac the only option would be emulating ARM, which is exactly what Mac.apk exists to avoid.

macOS 26.4 or newer

Native Android code relies on a platform capability that macOS only has from 26.4 on. Without it, apps don't fail cleanly. They crash now and then, corrupt their own data, or do strange things that look like bugs in the app. We'd rather refuse to run than ship that, so Mac.apk checks for the capability at startup and won't run native Android code without it.

Fix Mac.apk, not the app

Mac.apk doesn't patch or crack the apps it runs. When an app misbehaves, we treat it as a gap in Mac.apk's version of Android and fix it there, so Mac.apk acts the way a real Android device would. Because the fix is in the platform and not in one app, it usually helps every app that does the same thing. That's why a single release often gets several apps working at once.

It says what it is

Mac.apk tells apps it's a Mac.apk device. It doesn't claim to be a certified Android phone, and it doesn't forge anything that's meant to prove what a device is.

• Licence checks go to Google with your own account, and Google's signed answer reaches the app untouched. Mac.apk has no way to fake a "licensed" result.
• Play Integrity and similar hardware attestation aren't provided, because Mac.apk can't truthfully pass them.
• We don't work around anti-cheat, such as Epic's.
• No ads are faked, and nothing can be bought. For Developers and Publishers explains why.

That does cost some compatibility, mostly certain sign-in buttons and a few games. We think it's the right trade.

Not a sandbox

An Android app on Mac.apk runs with your macOS account's permissions, like any other Mac app you download. Mac.apk applies Android's permission rules to an app's Java code, but it isn't a security boundary and doesn't pretend to be. Only install APKs you trust.

Decisions explained elsewhere

Some choices are easier to explain next to the feature they affect:

• Why every store install asks for Touch ID: App Stores
• Why an app's saves live inside the app: How Apps Are Installed
• Why apps use your real Pictures, Downloads and Documents folders: Files and Privacy
• Why there are no ads or in-app purchases: For Developers and Publishers