Start with an APK.
An Android™ package carries the app’s code, assets, and sometimes native libraries. Shiraz starts with that original package.
Package handlingBring supported Android™ apps to your Linux or macOS desktop.
No virtual machine. No full Android™ system.
Package your APK locally. Your files stay with you.
Shiraz is an experimental project. App compatibility is growing, and some features may be incomplete or unsupported.
The Apple Silicon macOS port is earlier still: an app’s native libraries load and talk to its Java code, but full apps are not yet supported on macOS.
Run only APKs you trust. Apps run with your user’s permissions, without an Android™-style sandbox.
Shiraz Web
Your Android™ apps, a browser away. Shiraz Web runs supported APKs on a Linux host and streams the app to your browser over WebRTC.
Designed with Linux phones in mind, with touch and keyboard controls. The app runs on the host; your browser is the window.
Set up Shiraz Web Experimental · App compatibility is still growing.Shiraz Launcher
Keep your APKs in one window on an Apple Silicon Mac. Drop a file in to add it; Shiraz reads its name and icon and leaves the original untouched.
Set screen size, orientation and logging for each app, then launch, stop or restart it. A running app shows its own icon in the Dock and its output in a console. Loading an app’s native libraries is a per-app switch, off by default.
Build the launcher Experimental · macOS 27 on Apple Silicon · Built from source with Xcode. An APK that imports can still fail to start.Under the surface
Keep the app. Translate what it needs.
Scroll through the pieces that make it possible.
An Android™ package carries the app’s code, assets, and sometimes native libraries. Shiraz starts with that original package.
Package handlingART is Android™’s runtime. Its standalone host build for Linux and macOS executes the app’s DEX bytecode, with ahead-of-time compilation where supported.
Runtime setupApps expect Android™ APIs for views, resources, and services. Shiraz implements a growing subset of those APIs, so supported app code can keep making familiar calls.
Java framework codeJNI connects Java code to native C/C++ bridges. Bionic compatibility helps Android™ native libraries run; SDL and EGL/GLES provide window, input, and graphics paths. On Apple Silicon Macs, a guest ELF loader and bionic ABI adapters do the same job. On x86-64 Linux, optional translation built on Digitalis can run supported ARM64 app code from a source build.
Native bridge codeLinux or macOS supplies the host environment. The app gets a desktop window and host input, without booting an Android™ image or running a virtual machine.
Window presentationDifferent paths to Android™ apps
A translation layer, a container, or a virtual device.
Each makes a different tradeoff.
Swipe or scroll sideways to see the full comparison.
| Project | Approach | Android™ environment | What to keep in mind |
|---|---|---|---|
| ShirazThis project | API translationART + native Linux and macOS bridges | No full Android™ imageSDL / EGL / GLES | AppImage packaging and browser access on Linux; experimental Apple Silicon macOS port. Experimental API coverage; no Android™-style app sandbox. |
| Waydroid | ContainerShares the Linux kernel | Full Android™ systemLineageOS-based image | A full Android™ environment integrated with Linux. Requires container setup and suitable host support. |
| Droidloom | Namespaced userspaceShares the Linux kernel | Full Android™ userspaceART · Binder · Zygote · system_server | Separate Wayland windows with GPU acceleration. Includes Teto for ARM64 apps on x86_64; requires Binder and compatible Wayland protocols. Early preview. |
| ATL Android™ Translation Layer | API translationShiraz’s architectural starting point | Android™ APIs on LinuxApp-focused compatibility | A related translation approach. Check its project documentation for supported apps and build requirements. |
| Android™ Emulator | Virtual deviceSimulated Android™ hardware | Android™ system imageConfigured through an AVD | Designed for development and testing across device profiles, Android™ versions, and simulated sensors. |
| Anbox Archived project | ContainerShares the Linux kernel | Full Android™ system | A historical container approach. The original repository is archived; distinct from Anbox Cloud. |
Architecture comparison, not a performance ranking. Compatibility depends on the app, device, and configuration. Project names link to their own documentation.
APK Shiraz runtime AppImage
Don’t believe it? Try it now!
Package a supported Android™ app into an AppImage, right here.
Your APK stays on your device. The AppImage is built in your browser.
With the runtime dependencies prepared:
make build
make appimage APK=/path/to/app.apkFrom a source checkout. Shiraz checks the signature on F-Droid’s index, then checks each download against the SHA-256 that index lists. Replace the package name with the app you want.
python3 -m shiraz fdroid sync --cache fdroid
python3 -m shiraz fdroid fetch org.example.app --cache fdroid --output app.apk