WebView embedding

This surface is not yet available. There is no WebView bridge to install, and no snippet on this page to copy, because there is nothing shipped to point you at.

We are documenting the gap rather than leaving it blank, so you can plan around it instead of searching for something that is not there.

What it will offer

A supported way to host the web elements inside a native WKWebView or Android WebView, with the parts that do not work by default handled for you: passing a session token in without putting your credentials in page source, surfacing the widget’s events to native code, and handling navigation out of the WebView when a customer taps through to your own screens.

If you need it now

You can load a normal web page containing the elements into a WebView today — they are ordinary custom elements and nothing about them requires a browser chrome. What is missing is the bridge, so you would be building the token plumbing and the event forwarding yourself, against no supported contract.

Talk to us before you do. If a WebView is on your roadmap we want to know: it moves the priority, and we would rather shape the bridge around a real integration than guess at one. Your DriveCars contact can put you in touch with the team directly.

In the meantime, the web SDK is fully supported and is what every live partner integration uses.