Same JavaScript, native permission
WebViewGold bridges the HTML5 Geolocation API to Core Location and the Android location services. The first call shows the system dialog with your purpose string; later calls return positions directly.
How it works in the app
HTTPS is mandatory
Geolocation only works on https:// pages. Your published Lovable URL already is; make sure every embedded map or API call is HTTPS as well.
Store paperwork
Apple asks what you do with location data (App Privacy), Google asks in the Data safety form and wants a reason for the permission. "Show nearby offers" is enough if that is what you do.
Prompt for Lovable
Paste this into Lovable to implement the web-app side. Review the result, publish, then test inside the WebViewGold app.
Prompt to paste into Lovable
Add location features for the WebViewGold app wrapper. Create a Nearby page that first shows a short explanation and a Use my location button; only after the tap call navigator.geolocation.getCurrentPosition with enableHighAccuracy false and a 10 second timeout. Handle PERMISSION_DENIED with a message explaining how to re-enable location in the phone settings, and TIMEOUT with a retry. Save latitude and longitude into profiles.last_location (PostGIS geography) through a Supabase RPC update_location, and add an RPC nearby_places(lat, lng, radius_m) that returns places ordered by distance. Never request location on page load and never use watchPosition in the background.
Great way of converting your web app to a native app! Fast turn-around, and a great way to get your apps into the app stores without the need to develop a full native app!
Set it up for a Lovable app
About 10 minutes.
Write the purpose string
In the WebViewGold Xcode project edit the location usage description in Info.plist ("We use your location to show gyms near you"). Android: the permission is declared in AndroidManifest.xml and the system explains it. The Cloud Builder exposes the text as a field.
Ask at the right moment
Call
navigator.geolocation.getCurrentPosition()when the user taps "Near me", not on page load. Apple rejects apps that request permissions without context (Guideline 5.1.1).Handle denial gracefully
If the user declines, show a manual input (city or ZIP) and a hint;
settingsapp://opens the app settings where the user can change the decision.Store only what you need
Send coordinates to Supabase or Lovable Cloud (Postgres, storage, edge functions) only for the feature that needs them and say so in the privacy policy; precise location is a sensitive data type in both questionnaires.
Limits to know
- Background location is an opt-in native option (
backgroundlocationin Config.swift,requireBackgroundLocationin Config.java) that both stores scrutinize; leave it off unless your product genuinely needs it and explain it in the review notes. - Watch positions (
watchPosition) work while the app is in the foreground; stop them when the user leaves the screen to save battery. - Reviewers test on devices with location services off: make sure the app still works without a position.
Frequently asked questions
Do I need native code for GPS?
No. The standard HTML5 Geolocation API in your Lovable app is bridged to the native location services by WebViewGold; you configure the permission text.
Why does Apple reject location requests on launch?
Guideline 5.1.1 asks that permission requests make sense in context. Request the position when the user triggers a location feature and explain why in the purpose string.
Can I use Google Maps or Mapbox in the app?
Yes. Map embeds and SDK JavaScript libraries work in the WebView like in the browser, as long as everything loads over HTTPS.
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 pageCloud 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 demoFull 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
Winter Sale prices valid until December 31, 2026.