I Built an Open-Source Tool That Turns Websites Into Android Apps
I Built an Open-Source Tool That Turns Websites Into Android Apps Hey everyone! I’ve been working on a project called InteeBuild. The idea is pretty simple: Give it a public website or HTML and get an Android proje
I Built an Open-Source Tool That Turns Websites Into Android Apps
Hey everyone!
I’ve been working on a project called InteeBuild.
The idea is pretty simple:
Give it a public website or HTML and get an Android project/APK/AAB without having to manually set everything up.
GitHub:
https://github.com/Fluxionics/InteeBuild
What can it do?
InteeBuild currently supports things like:
- Website → Android app
- HTML → Android app
- APK / AAB builds
- Custom app name and package
- Custom icons
- Android permissions
- Background audio
- Native bridges
- GitHub Actions builds
- Build artifacts
- Build logs
- API access
- Webhooks
- APK inspection/decompilation
- Security checks for URLs and webhooks
One of the parts I spent the most time on was the permission system.
Instead of simply adding permissions to the manifest, InteeBuild keeps information about whether a permission requires runtime access, special Android settings, dependencies, minimum SDK versions, etc.
Security
Since the server can receive URLs and APK files, I also added protections against things like:
- SSRF
- localhost/private IP access
- cloud metadata endpoints
- malicious ZIP/APK structures
- oversized inputs
- API abuse
- invalid webhooks
- rate-limit abuse
There are also automated tests for many of these cases.
Why did I make it?
I wanted something that could take a website and make the Android side much less annoying.
There are already many tools that do something similar, but I wanted InteeBuild to be more transparent about what is actually generated and what still requires native implementation.
For example, adding a permission to Android's manifest doesn't magically make the website capable of using that hardware.
So the project tries to distinguish between:
declared → supported → generated → actually usable
What's next?
Right now I'm focusing more on stability and security instead of just adding more features.
I want the core pipeline to be reliable:
URL/HTML → Analyze → Configure → Audit → Build → APK/AAB
I'd love to hear feedback from other developers.
GitHub:
https://github.com/Fluxionics/InteeBuild
What would you improve or add to a tool like this?
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.