Getting Started
What is WebToAppMaker?
Understand what the builder creates, what remains web-based, and which native capabilities can be added around your website.
Before you start
- A responsive website served over HTTPS
- Permission to publish an app for the website and use its branding
Configure and verify
Keep the website as the content layer
The generated app loads your live website in a managed WebView. Website content changes normally appear without rebuilding the app.
Configure the native shell
Use the dashboard to add branding, system bars, navigation, permissions, loading states, downloads, push, authentication, analytics, ads, and other native behavior.
Preview before compiling
Use Mock preview for fast layout checks and Flutter preview for a closer rendering of the generated shell. Use a real APK for device APIs and final WebView behavior.
Build release files
Android builds produce an APK for testing and an AAB for Google Play. iOS signing and IPA generation require a macOS worker with Xcode.
What changes without a rebuild
Website pages, server-side content, and most remote assets update immediately because the app loads the live URL.
What requires a new build
- Package or bundle identifier
- App icon and native splash assets
- Permissions and platform manifest entries
- External SDK dependencies and credentials
- Version name and version code
Android baseline
The current Android template uses minimum SDK 24, corresponding to Android 7.0 or newer. The target SDK follows the installed Flutter toolchain.
Test before release
- Website works on a narrow mobile viewport
- HTTPS certificate is valid
- Login, upload, payment, and download flows work in a mobile browser
- You control the final package or bundle identifier