Skip to content
WebViewGold Vibe Coding to App Store
English
Get WebViewGold

Bolt + offline

Offline behavior for your Bolt app

Reviewers switch on airplane mode. Users ride the subway. A Bolt app that shows a white page offline looks broken; a native offline screen with a retry button looks like an app. WebViewGold gives you three levels of offline support, and the right one depends on your stack (React or Next.js with Vite, Tailwind CSS, often Supabase for auth and data; Bolt can also deploy straight from the editor).

From $109 one-time per platform, or let our team do it all from $698.

  • Approval guarantee – or money back within 14 days
  • No coding needed
  • One-time payment, free updates
  • 24/7 human support
  • Made in Germany since 2014 · ISO 27001

The three levels

1. Native offline screen

Default. When the device has no connection, WebViewGold shows a branded offline screen with a "Try again" button (offlinetitle, offlinemsg, offlinebuttontext) and reconnects automatically (offlinescreenautoretry). Zero work in Bolt.

2. Cache and error states

The WebView caches your app's assets so repeat launches are fast. Add friendly error states in Bolt for requests to Supabase, Firebase or your own API that fail mid-session, and keep form input when a request fails.

3. Local HTML fallback

Ship a static build (or a lightweight offline version) inside the app: offlinelocalhtmlswitch on iOS, FALLBACK_USE_LOCAL_HTML_FOLDER_IF_OFFLINE on Android. The app loads the remote URL when online and the local folder when offline. Ideal for content apps, manuals and catalogs.

Prompt for Bolt

Paste this into Bolt to implement the web-app side. Review the result, publish, then test inside the WebViewGold app.

Prompt to paste into Bolt
Improve the offline behavior of this app for the native mobile version. Add an OfflineBanner component that listens to the online and offline events and shows "No connection, retrying..." at the top of the layout. Wrap all Supabase data fetching in a helper that catches network errors and renders an ErrorState component with a short message and a Retry button that re-runs the fetch. Keep the last successful list results in memory so navigating back while offline still shows data. Finally, create public/offline.html (inline CSS only, no external assets) with our logo, the text "You seem to be offline" and a button linking to reconnect:// so I can copy it into the native app's fallback folder.

I am very happy I bought this app! Extremely easy and great documentation. Was in contact with the customer service, they replied very quickly and very friendly. They solved my question within a day. 10/10 would recommend.

Nelis Geiger · CodeCanyon

A good offline setup for a Bolt app

Level 1 takes two minutes; level 3 an afternoon.

  1. Brand the offline screen

    Set title, message, button text and background color in the config (or Cloud Builder). Mention what the user can do ("Reconnect to see your orders").

  2. Add error states in Bolt

    Every data fetch to Supabase, Firebase or your own API needs a failure state with a retry button, not an empty list. Time out after a few seconds instead of spinning forever.

  3. Cache the last state

    Show the last loaded dashboard numbers or list with a "last updated" note while offline; a service worker or local storage in your web app is enough.

  4. Optional: bundle an offline version

    Export a static build of the parts that make sense offline (help, catalog, saved items) into the local-html folder and switch the fallback on. Keep the remote URL as the primary source so updates stay instant.

  5. Test in airplane mode

    Launch cold, launch with a cached session, lose the connection mid-session, reconnect. This is exactly what the reviewer does.

Frequently asked questions

Will my Bolt app work fully offline?

Only with a local HTML folder (level 3) or a PWA designed for offline data. Apps that depend on Supabase, Firebase or your own API show the offline screen until the connection is back, which is what reviewers expect.

Do service workers work inside the app?

The system WebView supports standard caching; WebViewGold's own offline screen does not depend on them. For guaranteed offline behavior, use the local HTML fallback.

Is the offline screen customizable?

Yes: text (in up to three languages), colors and the retry behavior are settings in the WebViewGold project.

Three ways to get your app into the stores

Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.

Do it yourself

$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

Cloud Builder

$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

Full Service

$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 WeSetupYourWebViewApp

Winter Sale prices valid until December 31, 2026.

Ready to ship your Bolt app?

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.