A simpler way to build for Android

Android projects.
APKs, made simple.

Your project. Your next Android app. We’re building a browser-based way to compile Android Gradle projects into debug-signed APKs, without a local Android toolchain.

  • Android + Gradle
  • Built for sideloading
Zip2APK: Android robot with a blue source archive and a green APK
ANDROID PROJECT.zip / .tar.gz→ .apkFrom your code to your phone.

Made by Larsen Code Labs.

Builds are opening soon.

We’re getting Zip2APK ready for its first builds. In the meantime, get your project ready for a smoother start.

UploadBuildDownload
  • Bring an Android Gradle project

    Include your build files and source code.

  • Package it as ZIP or TAR.GZ

    Keep signing keys and secrets out of the archive.

  • Make room for your next app

    The planned output is a debug APK for your device.

Check your project

Uploads and builds are not available yet. This site does not accept project archives.

ProjectAndroid + Gradle
Planned outputDebug APK
StatusPre-launch
Skip the local setup

A build workflow in your browser.

Your source, your app

Designed around Android Gradle projects.

Made for testing

Debug-signed APKs for sideloading.

The plan, from files to phone

Three steps. One APK.

A look at the workflow we’re preparing for launch.

  1. Upload your project

    Start with a ZIP or TAR.GZ of an Android Gradle source project. Its structure is checked before a build can begin.

  2. Follow the build

    Once builds open, follow your project’s progress through the queue and compilation.

  3. Download your APK

    Get a debug-signed APK for testing on your Android device. Store release signing remains your own process.

Prepare your project

A good build
starts here.

A few practical details about source archives, signing, and your files.

Talk to Larsen Code Labs
What kind of project is Zip2APK for?

Standard Android Gradle source projects packaged as ZIP or TAR.GZ. Include your settings file, module build files, manifest, and source code. A website-only archive or an existing APK is not an Android source project.

How should I prepare my archive?

Keep your project’s folder structure intact. Include the Gradle build configuration and application source. Remove local caches, generated build output, credentials, signing keys, and machine-specific local.properties files. Keep a backup of your project.

Will private dependencies or NDK projects work?

The initial scope is standard Android Gradle projects using public dependencies. Private dependency repositories and native NDK builds are outside the initial supported scope.

Can I publish a debug APK to Google Play?

A debug-signed APK is intended for sideloading and testing. It cannot be published directly to Google Play. A store release needs your own release signing and publishing process.

Can I upload a project today?

Builds are not open yet, and this site does not accept source files. We’ll update the site when the build service is ready. Until then, use the guide to prepare your project.

Questions, ideas, or a hello

Let’s talk Android.

Contact Larsen Code Labs