WebViewGold Documentation · Android
🇺🇸 English
Get WebViewGold

Splash Screen

Customize the splash/launch screen of your Android WebView app with your own graphics.

Customize the splash screen behavior by configuring the following variables in Config.java:

Option
Type
Description
SPLASH_SCREEN_ACTIVATED
true or false
Set to true to activate the splash screen
SPLASH_TIMEOUT
number (milliseconds)
Delay before showing the loading indicator if the home URL is still loading
REMAIN_SPLASH_OPTION
true or false
When true, keeps the splash screen visible until the home URL has fully loaded (overrides SPLASH_TIMEOUT)
SPLASH_MIN_TIME
number (milliseconds)
Minimum display duration when REMAIN_SPLASH_OPTION is true; ignored if the actual load time exceeds this value
SPLASH_FADE_OUT
number (milliseconds)
Fade-out animation duration after all timers; set to 0 to disable the fade effect
SCALE_SPLASH_IMAGE
percentage [0–100]
Scale the splash image relative to the device's smallest dimension; 0 hides the image


Replacing the Splash Screen Image

  • Replace splash.gif in your assets with your own square GIF (e.g., 128×128, 512×512, or 1024×1024 px)
  • Ensure the image dimensions are equal (width = height) for optimal display
  • Set the background color in colors.xml


The steps to add a custom splash screen to your android app are shown in the video below:

SDK-style implementation notes

Treat this feature as a native capability exposed to your web layer: keep your production website or PWA as the source of truth, then use the documented WebViewGold configuration flags, URL commands, and JavaScript bridge calls to opt in to native Android behavior only where it adds value. This approach keeps your codebase maintainable because the same web application can serve browsers, WebViewGold for Android, and the other WebViewGold platforms with minimal conditional logic.

For reliable results, prefer HTTPS endpoints, stable route names, explicit success/error states in your UI, and small JavaScript helper functions that wrap native calls. For example, a web app built with jQuery Mobile, Lovable, Base44, Bolt, WordPress, Bubble, a custom React/Vue/Angular stack, or static HTML can expose a single button or event handler that triggers the native WebViewGold API while still showing a graceful browser fallback.

  • Recommended integration pattern: detect the app context, call the WebViewGold API, then update your web UI after the native callback or route change.
  • Testing checklist: validate the feature on a real device or packaged build, verify permissions and store review text, and confirm that browser-only users still receive a useful fallback.
  • SEO benefit: keep feature pages, route titles, and structured content indexable on your website while WebViewGold delivers the native app shell for Android users.

Too busy? We set up your app for you.

Our team configures, builds & submits your WebViewGold app — done-for-you, fast turnaround, Made in Germany.

Get your app set up →

Build in your browser

No Mac, no IDE: the WebViewGold Cloud Builder configures, builds & uploads your app online.

Discover Cloud Builder →