Native feature
A persistent value store and a device UUID, both one URL call away. Pick your builder for session restore, device limits and the privacy answers that match.
From $109 one-time per platform, or let our team do it all from $698.
writevalue:// stores everything after the scheme as one string in the app's private storage; readvalue:// injects it back into the page, as window.storedValues on iOS and window.appSettings on Android. Values survive restarts and cache clears and disappear when the app is uninstalled (on Android also when its app data is wiped).
get-uuid:// sets the JavaScript variable uuid, a non-personal unique device ID. Alternatively append it once to the first request as ?uuid=XYZ (enhanceUrlUUID / UUID_ENHANCE_WEBVIEW_URL) or inject it on every page (autoInjectVariable / AUTO_INJECT_VARIABLES).
Not synced across devices, not a database, not a password vault. Keep values small (settings, flags, a revocable token), keep user data in your backend, and never treat the UUID as proof of identity.
Write a revocable refresh token after login. If the web session is gone after a cache clear, read it back on launch and restore the session silently instead of showing the login screen.
Theme, language, units, "onboarding done", the last opened workspace: read locally on launch, before your backend answers, and even offline.
"Pro works on two devices": register the UUID on activation, count active devices on the server and offer a Manage devices screen to free a slot.
Skip the second factor or the email code on a device the user already confirmed, and show "Signed in on: iPhone, Pixel" with a sign-out per device.
A front-desk iPad or a warehouse scanner phone that should always open the same location or station: store the station ID per device.
Use them first; inside the app they persist the way they do in a browser. The native value store is the backup for what must survive a cache clear, such as a revocable device token, onboarding state or a language choice, and it is available on launch, even offline.
No. It is a non-personal device identifier for your own app logic, not the IDFA or the Android advertising ID, and reading it does not show the App Tracking Transparency prompt. If you used it to track users across other companies' apps or shared it with ad networks, it would become tracking and the ATT rules would apply.
No. Values are per install and per device. Anything that should follow the user (profile, preferences, purchases) belongs in your backend; the device store only speeds up launch and keeps one device signed in.
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.
