Clipboard API
Copy text to the Android clipboard and read clipboard content from your web app via JavaScript.
The WebViewGold Clipboard API provides a simple and secure way to access the device clipboard contents from within your WebView-based app. This serves as an alternative to relying on native WebView clipboard access, offering more reliability across platforms and updates.
Use Cases:
- Pre-filling form fields with copied data
- Enhancing user flows in authentication, note-taking, or sharing apps
- Creating quick paste features or clipboard history tools
How to Retrieve Clipboard Content:
To access the clipboard data, use the following call:
<a href="getclipboard://">Get Clipboard Data</a> <a href="#" onClick="alert(clipboarddata);">Show Clipboard Data</a>
- Get Clipboard Data: Triggers the native clipboard read functionality.
- Show Clipboard Data: Displays the result stored in the
clipboarddataJavaScript variable.
Technical Note: Once getclipboard:// is triggered, WebViewGold automatically injects the clipboard content into the clipboarddata JavaScript variable on the page, making it accessible for any further actions.
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.