Browser-based app builders
Form-driven application builders for managed Android estates. Submit your requirements, download a deployable, signed APK or AAB. No code, no build tools, no fee.
205+ apps generated · 80+ web · 95+ kiosk · 20+ contacts · 5+ documents
Kiosk app generator
Replace the system home screen on dedicated devices with a tiled layout of just the apps your users need - themed, wallpapered, foldered. Signed APK or AAB output, distributable through any EMM. Built for Android Enterprise dedicated estates, but works anywhere a locked-down multi-app surface is desired.
Web app generator
Wrap any URL in a native WebView - configurable display mode, permission set, theme and icon, signed and ready to install. Distribute internal web apps to managed devices via EMM, or anchor a kiosk to a single web destination without the rest of the browser tagging along.
Contacts app generator
Sync internal contact files - VCF, CSV or JSON - into a dedicated, app-owned account on managed devices, surfaced in a searchable in-app directory and in the phone's own contacts. No Exchange, LDAP, CardDAV or vendor cloud; configured by your EMM or baked in at build time, signed and ready to distribute to Android Enterprise estates.
Document app generator
Bundle the documents an estate needs - PDFs, EPUBs, images, markdown, CSV, text and more - into a dedicated, branded library app. Files are baked in at build time or fetched from URLs and stored for offline reading, organised into folders and opened in a built-in viewer. No file server or vendor cloud; configured by your EMM or set at build time, signed and ready to distribute to Android Enterprise estates.
How it works
Choose a web app, a kiosk launcher, a contacts directory or a documentation library. Each one is a focused builder for a single job.
Customise the app and the content within it - branding, icon, theme, behaviour and the files or apps it carries. No SDK, no build tools, nothing to install.
A build unique to you is produced and a signed APK or AAB is presented, alongside its full MIT-licensed source. Yours to keep, no account required.
Side-load it or push it through any EMM. Most generators also read EMM managed configuration, so you can adjust app behaviour at runtime without rebuilding.
The generators gain new features and fixes regularly. Regenerate your app any time using its unique update code and keep the same package identity.
Good to know
These generators exist to close some of the most common application gaps in the Android Enterprise ecosystem. Working with so many customers and partners, I hear the same complaints over and over. They exist to provide a good, affordable, feature-complete alternative to proprietary EMM tools, expensive third parties, or the feature-sparse options many organisations have to put up with today.
Yes. No fee, no account, no per-app charge. Fill in the form and download your app.
A signed release APK or AAB (your choice of format), ready to distribute, plus the full MIT-licensed source of the app that was built. The app is yours to keep, modify and ship.
They don't stick around. Your build, its source and config are deleted five minutes after you download them, and anything left undownloaded is purged within a day. No account means nothing is tied to a profile.
That also means each time you rebuild you'll need to supply your uploaded assets again (sorry).
Every build is given a brand-new package name, unique to your app, written to a permanent registry and never issued to another generated app again. Stored alongside it is an update code: a one-off secret, like a password, that grants the right to claim that same package name later.
Supply the code when you regenerate and the new build keeps its original identity, so (as long as it's signed the same way) it installs straight over the existing app across your estate as a normal update, with nothing to uninstall first.
Only a hash of the code is ever stored, so it cannot be looked up or recovered later. Lose it and that package name is gone for good - the next build would mint a fresh identity your devices treat as a separate app. Treat the update code like a password and keep it safe.
Android requires an app to be signed before it can be installed. For release builds, a Bayton certificate is offered for signing so it's ready to deploy right away - the same convenience F-Droid and similar services offer.
Prefer to own the key? Upload your own keystore in the form, or take the source and sign it yourself. Just note, and this is not optional - never reuse a keystore that has signed any other app. You're effectively providing keystore credentials to a third-party service; if they were ever compromised, you'd only need to rotate them on the generated app.
Support is always offered for application bugs and product issues. For help using the generators, deploying them, or other in-life guidance, start with the documentation within each generator, or head on over to bayton.org/projects for more information.
If you'd still like a hand, or your internal policies require a vendor-supported product, reach out to explore commercial options through BAYTON consultancy. The app source is provided too, so your own developers can build on these projects at any point (which would naturally fall outside support from here).
There isn't one. These tools are funded through BAYTON consultancy. If you'd benefit from help with your Android estate, please reach out - and if you're simply happy with the service, tell others about it.