WebToApp

WebToApp

WHAT IS IT?

WebToApp is an APK workshop that runs entirely on Android. You hand it a URL, an HTML folder or a Node, PHP, Python or Go project, and it hands back a signed APK, with no PC and no remote build server. V1/V2/V3 signing and Play Store AAB export both happen on the phone through apksig.

WHY IS IT INTERESTING?

  • Real server runtimes on-device: Node.js 18.20, PHP 8.4 with Composer, Python 3.14, Go 1.26 and WordPress 7.x over SQLite are fork+exec'd as native binaries. The generated APK hosts a local server, where classic wrappers stop at a WebView pointed at a URL.
  • Self-contained build chain: binary AXML/ARSC patching, pruning of unused permissions from the template manifest, V1/V2/V3 signing toggled independently, and AAB export with targetSdk rewritten to the level the Play Store requires. Nothing leaves the phone.
  • Detailed network stack: DNS-over-HTTPS across seven providers, static, PAC and SOCKS5 proxies, CORS bypass for static SPAs that call external APIs, and automatic failover to mirror URLs when the primary target goes dark.
  • Extensible after the build: JS/CSS modules, Tampermonkey-style userscripts with a GM_* bridge, and an MV3 Chrome extension runtime with in-app Chrome Web Store search.
  • Two rendering engines: the system WebView by default, or GeckoView downloaded on first use for Encrypted Client Hello.
  • Optional hardening: PBKDF2 plus AES-256-GCM encryption of packaged resources, with anti-debug and DEX tamper checks once encryption is on. Browser fingerprint disguise covers 50+ vectors, and the README states these features are for technical demonstration and require the end user's informed consent.

USE CASES

  • Package a static Vite or React build into an APK served from an embedded localhost
  • Ship an installable WordPress demo with PHP and SQLite bundled inside the APK
  • Produce a signed Play Store AAB without a desktop build toolchain
  • Bundle several sites into one app laid out as tabs, cards, feeds or a drawer