APK Builder

Upload an Android project as a .zip. Every build runs in its own isolated branch — safe to use alongside anyone else, at the same time. Not sure your zip is set up right? See how to prep it.

TAP TO SELECT PROJECT.ZIP

or drag and drop it here

Any Android/Gradle project zip works — even if it's never been set up for CI before. It's auto-detected and converted.

Push

Queue

Build

Ready

> OK ERR Preparing…

⬇ Download APK

📦 How to zip your project

Almost any Gradle/Android project zip works now — this is auto-detected and fixed up, not just checked. Here's what happens automatically, and the one thing to actually avoid.

1

Any nesting depth is fine. The zip's settings.gradle (or settings.gradle.kts) is found wherever it is — one top-level folder, a few levels deep, doesn't matter.
2

No Gradle wrapper? No problem — a runner-installed Gradle is used instead. Have one? It's used as-is, and common issues (missing execute permission, Windows CRLF line endings in gradlew) are fixed automatically.
3

A leftover local.properties pointing at your own machine's SDK path is removed automatically — it would otherwise break the build on the CI runner even though your project is fine.
4

Have a custom CI workflow? Include your own .github/workflows/*.yml with a workflow_dispatch trigger and it'll be used automatically. Otherwise a workflow that adapts to whatever your zip contains is generated for you.
5

Leave out build output — build/, .gradle/, *.apk — it's regenerated fresh and skipped automatically if included.

Works fine MyApp.zip
└ MyApp/
  ├ settings.gradle
  ├ build.gradle
  └ app/
…nested further, wrapper or no wrapper.

Avoid A zip with no settings.gradle anywhere in it — that's the one thing that can't be auto-detected.