Prototype SDK support matrix¶
SDK availability depends on the system image, installed providers and account state. Package or framework presence is a prerequisite, not working SDK behavior, and nothing here guarantees prototype runtime support. No cross-platform implementation is inferred from an SDK name.
Support matrix¶
Columns: AOSP default (API 30 only; API 36 AOSP not checked), google_apis (the AutoMobile
default image, API 36). The remaining columns are google_apis with GMS disabled, google_apis_playstore (API 36),
physical Android, iOS Simulator (iOS 26.5/27.0 framework presence only) and physical iPhone.
No SDK has been run in a host app, so no cell is verified. Every physical-device cell is
“unverified, needs account/hardware”.
| Feature | Status |
|---|---|
| MapLibre, MapKit, Android System WebView / WKWebView, ML Kit bundled models, Apple Vision, Glance / Quick Settings tiles / WidgetKit | unverified everywhere |
| Google Maps SDK | impossible on AOSP default (no GMS on API 30); unverified elsewhere |
| Credential Manager | impossible on AOSP default (API 30 predates the provider API); unverified elsewhere |
| Custom Tabs / ASWebAuthenticationSession | impossible on AOSP default (no Custom Tabs service); unverified elsewhere |
| Play Billing, Google Pay TEST environment, StoreKit Testing, Sign in with Apple, ML Kit unbundled models | unverified, needs account/hardware, on every runtime |
| Apple Pay sheet | unverified on the Android columns; unverified, needs account/hardware, on iOS |
Account, purchase, model-download and physical-device checks have not been run; the account/hardware label does not imply compatibility on every platform. The image contents behind these cells are recorded in SDK prerequisite captures.
Image facts that affect setup:
- AOSP
defaultAPI 30 has no GMS, Play Store, Chrome or Google WebView; its WebView provider is the non-updatablecom.android.webview. - Both API 36 Google images ship GMS and Maps packages, the updatable
com.google.android.webviewprovider, and Chrome as the Custom Tabs service. Onlygoogle_apis_playstoreservesInAppBillingService.BIND. Neither has a signed-in account, a Wallet package or NFC/HCE. google_apisis a userdebug build that allowsadb root; the Play Store image is a user build.
Provisioning¶
ANDROID_TAG_PREFERENCE in src/devices/deviceProvisioning.ts ranks
google_apis > default > google_apis_playstore when comparing images of equal
API level and ABI. The default preference therefore supplies GMS but does not
supply a working Play Billing service on the API 36 google_apis image. See
device resources for googlePlayServices disabling.
A request that sets requires.playStore: true asks for Play-dependent features. It
matches only an emulator built from a Play Store system image (a *playstore* tag, or
Google TV), and a new emulator is created from google_apis_playstore (or the Play car
image for automotive). With no such image installed the request is refused with the
sdkmanager package to install. A device whose image is unknown, such as a physical
device, does not match. Without the requirement the preference above is unchanged.
Play Store images are user builds that refuse adb root, so root-dependent features on
them refuse with a message that they need a non-Play image. Play Billing there still
needs a signed-in Google account, which no captured image has.
Backend advertisement (#14302, contract only)¶
A spec picks an SDK backend only through its module’s own backend field, such as
the map node’s backend (#14308) or the commerce catalog’s backend (#14314). It
never names an SDK or a URL. Runtimes advertise backends as capability strings, and
the report carries no separate backend field:
- The module’s default backend (
autofor maps,fakefor commerce) needs only the module capabilityprototype_platform_<module>_v1. A module without abackendfield, such as fake sign-in (auth, #14303), has only its default. - Each other backend is one capability string,
prototype_platform_<module>_<backend>_v1, for exampleprototype_platform_map_google_v1orprototype_platform_commerce_storeKitTest_v1. The backend name is spelled as in the spec’sbackendvalue. - A runtime advertises a backend capability only while that backend can work on
this device. Google Maps needs a host-configured key and GMS; Play Billing needs
an image that serves
InAppBillingService.BIND. A backend that becomes usable later appears in the next capability report. The spec does not change. - The
platformModulestable inschemas/prototype-spec-contract.jsonlists each module’s non-default backends and their capabilities next to its calls. The generated platform gates then refuseshow,patchandreplaceNodefor abackendvalue whose capability is absent, with the field path, as they do for per-call capabilities. ProtoViewerbundle.jsonrequireslists the same strings.
The map module lists google and maplibre (#14309). The TypeScript gates are
generated from the table; the Kotlin and Swift strict scanners read the same table
for the node that carries backend.