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.
No GitHub workflows to set up. No Actions, no CI, no new APK for every change. Just git push.
Package any static site as a signed Android app, no Android Studio required. Push to your branch and installed apps update automatically.
Works with any static build
Live apps follow your branch and download new commits when they open. No GitHub Actions, no CI, no release pipeline to maintain. Or pin a commit to freeze a release.
Each time the app opens, it checks your branch and downloads any newer commit. Good for content that changes: docs, menus, schedules, side projects.
No GitHub workflows to set up. No Actions, no CI, no new APK for every change. Just git push.
The 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 appThree steps, all in the browser. No Android Studio, SDK or Gradle on your machine.
Every export is a signed APK for testing and an Android App Bundle for the Play Store.
Generate one and download the backup, or upload a keystore you already use. GitDroid never gets access to your GitHub account.
Live apps pick up new commits from your branch. No reinstall for content changes.
Files from GitHub are stored on the device after the first download.
Keep using the framework you know. No Android Studio, SDK or Gradle: builds run on our servers.
Upload a ZIP of your site or wrap a website URL.
When your site asks for the camera, microphone or location with the standard web APIs, GitDroid will detect it and show the native Android permission prompt. No Java, no plugins, no extra code in your site.
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.
Coming soon. GitDroid will detect when your site calls the standard web APIs, such as getUserMedia() or navigator.geolocation, add the matching Android permissions to your app, and show the native Android permission prompt when your site asks. Today, built apps support everything that doesn’t need a device permission.
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.