Open App Settings API
Send users straight to your app's page in the iOS Settings app to manage permissions and notifications.
The Open App Settings API of WebViewGold sends the user straight to your app's page in the native iOS Settings app. From there they can manage permissions (camera, location, notifications…), language, and other app settings — without leaving your web app to hunt through iOS Settings.
How to Use:
Trigger the screen from an HTML link or from JavaScript:
<a href="settingsapp://">Open app settings</a>
window.location.href = "settingsapp://";
Typical Use Cases:
- The user denied a permission (camera, microphone, location, notifications) — send them straight to the system screen to re-enable it.
- Guide the user to the notification settings of your app, e.g. in combination with the
checkNativePushPermissions://call of the Push Notifications API.
Notes: No parameters. Any URL that starts with settingsapp:// opens the same screen.
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 iOS behavior only where it adds value. This approach keeps your codebase maintainable because the same web application can serve browsers, WebViewGold for iOS, 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 iOS users.