Android SDK

This SDK is not yet available. There is no Maven artifact to depend on and no Gradle coordinate to add. We are saying so plainly rather than leaving the page blank, so you can plan around it.

What it will offer

A native Android library covering the same ground as the web SDK: search, cart, checkout and payment as composable UI, a session held and refreshed against your own backend, and the same event vocabulary surfaced as Kotlin types instead of DOM events.

The design constraints will not change with the platform. Your app will still never hold a DriveCars client secret — your backend will mint the session, as it does today — and what renders will still be a function of the products your account is enabled for.

If you need it now

Two options, neither of them a native SDK:

Server-to-server. Build your own UI and call the /v1 API from your backend. This is fully supported, gives you complete control of the interface, and is the right answer if you have design opinions about how rental search should look in your app.

A WebView. Host the web SDK in an Android WebView. It works, but the bridge that would make it comfortable does not exist yet — see WebView embedding.

Tell us either way. Native demand is what moves this up the list, and we would rather build against a real integration than a guess. Your DriveCars contact can put you in touch with the team.