Native feature
A website header inside an app is the first thing reviewers notice. Pick your builder for the exact steps to hide the web menu, add a native tab bar and keep every tab URL loading in your stack.
From $109 one-time per platform, or let our team do it all from $698.
All four load a URL of your web app in the main WebView when tapped, so nothing about your routing changes. Pick one primary pattern per platform.
Set showNavFooter to true in Config.swift and describe three to five tabs in FooterBar.json: a label (name), an SF Symbol (sf_symbol) and the URL the tab opens (redirection_link), plus colour dark or light for the whole bar.
Set enableSidebar to true and fill Sidebar.json with the same fields. A floating button opens a native sliding menu, handy when you have more sections than fit in a tab bar. It works alone or next to the footer (sidebar docs).
ENABLE_NAVIGATION_FOOTER in Config.java adds a Material 3 bottom navigation bar. Its entries, icons and labels come from res/menu/menu_drawer.xml; Google recommends three to five top-level destinations. Dark and light mode follow the system automatically.
ENABLE_NAVIGATION_DRAWER adds a floating menu button that opens a Material drawer, driven by the same menu file. Bottom navigation and drawer can run together, for example main sections below and settings, help and legal pages in the drawer.
| Native bar (WebViewGold) | Tab bar built in the web app | Website header with hamburger | |
|---|---|---|---|
| Looks like | The system: SF Symbols on iOS, Material 3 on Android | Whatever you design, matched to your brand | A mobile website |
| Where you change it | FooterBar.json, Sidebar.json, menu_drawer.xml; ships with a store update | In your web app, live with every deploy | In your web app |
| Home indicator and safe area | Handled natively | Needs env(safe-area-inset-bottom) padding | Often hidden behind the home indicator |
| What a tap does | Loads the tab URL in the WebView (a page load) | Client-side route change; instant, keeps state | Opens a menu first, then navigates |
| Best for | Three to five stable top-level sections | Sections that change often, badges and counters | The website only; hide it inside the app |
No single feature is required. Guideline 4.2 asks whether the app offers more than a repackaged website, and 4.0 whether it follows iOS design conventions. A native tab bar is one of the clearest signals for both, especially next to push notifications and a proper offline screen, but it does not replace a mobile-friendly web app.
Not for the native bar: FooterBar.json, Sidebar.json and menu_drawer.xml ship inside the build. The pages behind the tab URLs update with every deploy. If your sections change often, build the tab bar in your web app instead and show it only inside the app.
Yes. Each tab loads its URL in the WebView, so your hosting must answer every route with the app (an SPA fallback to index.html) and your router must open the right screen on a direct load. Test it by pasting a tab URL into a fresh browser tab.
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
$109 per platform, one-time
The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.
See plans on the main page$349 per license, one-time add-on
No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.
How the Cloud Builder works Try the free demo$698 per platform $798
Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.
Full Service details Powered by
Winter Sale prices valid until December 31, 2026.
App Store & Google Play approval guarantee – or your money back within 14 days
Rather hand it over? Full Service: we configure, build and deliver within 72 hours, from $698 per platform. Questions? Chat with us 24/7.
Refunds are granted under the conditions listed in our FAQ: a non-content rejection by Apple and/or Google, claimed within 14 days after purchase.
