Your Android™ apps. A little more at home.

Bring supported Android™ apps to your Linux or macOS desktop.
No virtual machine. No full Android™ system.

Latest release v0.348.0Preview

Package your APK locally. Your files stay with you.

Still experimental.

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

Built for
Linux mobile.

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

A shelf for
your Mac.

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.
37 seconds, with sound and captions. Recorded from a development build on an Apple Silicon Mac. The F-Droid catalog lists apps you can download, not apps known to run.

Under the surface

Android™ on the inside.
Linux or macOS underneath.

Keep the app. Translate what it needs.
Scroll through the pieces that make it possible.

The Shiraz stack, simplified. Light enters at the app and lands on your desktop.
  1. 01Your APKApp code · resources · native libraries
  2. 02ARTAndroid™ Runtime
  3. 03Android™ API layerFramework · resources · services
  4. 04Native bridgesJNI · Bionic compatibility · SDL · EGL/GLES
  5. 05Your Linux or macOS desktopWindows · graphics · input · files
01 / The app

Start with an APK.

An Android™ package carries the app’s code, assets, and sometimes native libraries. Shiraz starts with that original package.

Package handling
02 / Execution

ART runs the code.

ART 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 setup
03 / Compatibility

Speak the app’s language.

Apps 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 code
04 / Translation

Connect it to the host.

JNI 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 code
05 / At home

A window on your desktop.

Linux 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 presentation

Different paths to Android™ apps

Choose the approach
that fits your desktop.

A translation layer, a container, or a virtual device.
Each makes a different tradeoff.

Swipe or scroll sideways to see the full comparison.

Android™ app execution approaches compared
ProjectApproachAndroid™ environmentWhat to keep in mind
ShirazThis projectAPI translationART + native Linux and macOS bridgesNo full Android™ imageSDL / EGL / GLESAppImage packaging and browser access on Linux; experimental Apple Silicon macOS port. Experimental API coverage; no Android™-style app sandbox.
Waydroid ContainerShares the Linux kernelFull Android™ systemLineageOS-based imageA full Android™ environment integrated with Linux. Requires container setup and suitable host support.
Droidloom Namespaced userspaceShares the Linux kernelFull Android™ userspaceART · Binder · Zygote · system_serverSeparate Wayland windows with GPU acceleration. Includes Teto for ARM64 apps on x86_64; requires Binder and compatible Wayland protocols. Early preview.
ATL Android™ Translation LayerAPI translationShiraz’s architectural starting pointAndroid™ APIs on LinuxApp-focused compatibilityA related translation approach. Check its project documentation for supported apps and build requirements.
Android™ Emulator Virtual deviceSimulated Android™ hardwareAndroid™ system imageConfigured through an AVDDesigned for development and testing across device profiles, Android™ versions, and simulated sensors.
Anbox Archived projectContainerShares the Linux kernelFull Android™ systemA 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!

Your APK.
A Linux app.

Package a supported Android™ app into an AppImage, right here.
Your APK stays on your device. The AppImage is built in your browser.

AppImage build options
Linux device architecture
Checking release…

The matching runtime downloads only when you build.

Use a local base AppImage

Ready. Select an APK to begin.

Packaging runs locally in your browser using WebAssembly. App compatibility and Linux phone support remain experimental. Only run APKs you trust.

Linux & macOSGTK-freeOpen source · GPLv3
Build from source

With the runtime dependencies prepared:

make build
make appimage APK=/path/to/app.apk
Development guide

Get an app from F-Droid

From 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
How the checks work

سعدی
Vakil Mosque, Shiraz · Photo by Faruk Kaymak / Unsplash