Haptic Feedback API
Trigger native haptic feedback (vibrations) from your web app for a truly native app feeling on iOS.
WebViewGold allows for the implementation of native iOS haptic control within your web app. Using our API, you are able to perform the following actions:
We suggest previewing Apple's best practices overview before including these features into your application. An example of how this API can be utilised can be seen below, with an anchor tag and custom javascript function which interact with our haptic API.
<a onclick="lightHaptic('index.html')">Navigation Link with Haptics</a>
<script>
function lightHaptic(url) {
if (isWebViewBrowser) {
window.location.href = url;
loadInnerHref("lighthaptic://");
} else {
window.location.href = url;
}
}
function loadInnerHref(url) {
iFrame = document.createElement("iframe");
iFrame.setAttribute("src", url);
document.body.appendChild(iFrame);
iFrame.parentNode.removeChild(iFrame);
iFrame = null;
}
</script>Click here to view a demonstration web page for this feature. Inspect the page to view the example code.
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.