GrandWeb documentation
What ships with GrandWeb, what you need before building, and how its remote configuration model works.
What you receive
Your CodeCanyon download contains the Android application source together with the web-side files the WebView shell can serve, and a compiled APK for testing.
- Application source (.java and .xml files)
- Web assets (HTML, CSS and JavaScript)
- A compiled .apk build
- A .db database file
- The setup guide bundled with the download
Prerequisites
GrandWeb is codeless in the sense that its appearance and behaviour are driven by configuration rather than Android code — but you still build and sign the app yourself.
- Android Studio, with the Android SDK installed
- A responsive website to wrap, or a site you can bundle into the app's local assets for offline use
- An AdMob account, only if you intend to enable the built-in banner advertising
- A device or emulator running one of the listed Android versions (12.0, 11.0, 10.0, 9.0 and other)
Getting started
The path from download to a branded, running app is:
Unzip the download and open the project in Android Studio.
Let Gradle sync and resolve dependencies on first open.
Set your application package name and the URL of the site you are wrapping.
Configure appearance — theme colour (solid or gradient), full-screen behaviour, splash screen and error page.
Enable AdMob and add your ad unit identifiers, if you are using advertising.
Build and run, then test downloads, uploads and embedded video playback against your real site.
Configuration
GrandWeb reads its configuration remotely, which is the main reason to choose it over a hand-written WebView wrapper: theme, behaviour and content settings can be changed on a shipped app without submitting a new build to the Play Store.
The exact configuration keys and where they are hosted for this release are documented in the setup guide included in your download.
- Theme — solid or gradient colours
- Display — full-screen mode, desktop or mobile rendering
- Content — remote URL or a site bundled into local assets for offline use
- Advertising — AdMob smart banner placement
- Failure handling — your own custom error page
Updates
Updates are distributed through CodeCanyon and appear under Downloads in your Envato account for the licence you already hold.
Remote configuration changes take effect on installed apps without a store update. Changes to the Android source itself still require a new build and a store submission.
Common problems
The most common reports come from the wrapped site rather than the app shell:
- The site looks wrong in the app — check whether the app is set to request the page in desktop or mobile mode, and confirm the site is genuinely responsive.
- Video will not play inline — confirm the provider is one the WebView supports (YouTube, Vimeo and comparable embeds are supported).
- Links open in the wrong place — the external app launcher intentionally hands links off to an installed app that claims them.
- Anything else: check the bundled setup guide first, then raise it through support with your device model and Android version.
Still stuck?
Check the setup guide bundled with your download first — it is specific to the release you own. If that does not resolve it, support can pick it up from there.
Go to support