Live
Each time the app opens, it checks your branch and downloads any newer commit. Good for content that changes: docs, menus, schedules, side projects.
Build a live appGitDroid packages the static site in your repository as a signed Android app. Push to your branch and installed copies update the next time they open.
Works with any static build
Three steps, all in the browser. No Android Studio, SDK or Gradle on your machine.
Paste a public repository and choose the branch and folder that hold your built site.
Give it a name, package ID and icon. Choose live or pinned content and a signing key.
Download an APK to try on your phone. Export a signed App Bundle when you’re ready for Google Play.
Choose per app. Changing the name, icon or permissions always needs a new build.
Each time the app opens, it checks your branch and downloads any newer commit. Good for content that changes: docs, menus, schedules, side projects.
Build a live appThe app serves one exact commit and ignores later pushes until you ship a new build. Good for client handoffs, demos and versioned releases.
Build a pinned appGenerate one and download the backup, or upload a keystore you already use.
Files from GitHub are stored on the device after the first download.
Keep using the framework you know. Nothing Android-specific to learn.
Upload a ZIP of your site or wrap a website URL.
Try it free. Pay once for a single app, or monthly if you build several.
Free
See your site running on a real device.
Create a test APK€49 per app
Everything you need to publish one app.
Export an app€19 / month
For people with more than one app.
Start BuilderLive content updates don’t count as builds. Apps you’ve exported keep working if you cancel.
Public GitHub repositories containing browser-ready HTML, CSS, JavaScript and assets. For React, Vue or another framework, commit its static production output first. GitDroid doesn’t run a Node.js backend or build your framework from source.
Not in live mode. The app checks its branch when opened and downloads updated web content without a new APK. Changes to the Android shell, like the icon, permissions or SDK version, require a new build. Pinned apps keep the selected commit.
GitHub mode needs a connection for the first content download. After that the files are stored on the device. Features that depend on remote APIs, sign-in or externally hosted assets still need a connection. ZIP mode bundles your files inside the APK.
Yes. App export includes a signed APK and AAB. Use the APK to install on a device and the App Bundle to submit to Google Play through your own developer account. Your app needs to meet Google Play’s policies.
No. Pulling new web content from GitHub doesn’t compile anything. The Builder allowance only counts successful Android builds.
Apps you’ve exported keep working, including live updates from GitHub. You keep your code and signing keys. Cancelling only ends access to the workspace and its build allowance.
You do. You choose the package ID, and either upload your own keystore or download the generated one after building. Keep the key and password safe: Android requires the same key for every future update.