Developers
Build for the screen people look at every day.
The developer kit, the portal and the review process open after Xchange launches. This is what's coming.
Two ways to build
A car app: an Android app for the head unit, installed by Xchange. Or a module: a card inside MyEVionics, built from its own components, no code to ship.
One manifest
xchange.json says what it is, which cars it fits, what it may do while driving, which data it needs and how it's sold.
Reviewed for the road
Every release is checked automatically and reviewed by us: signatures, permissions, data, and how it behaves while the car moves.
Paid through Xchange
One-time, subscription or in-app purchases, paid on the owner's phone. You keep 80%, 85% on your first US$10k a year.
A module's manifest
{
"schema": 1,
"id": "my.example.weather",
"kind": "module",
"name": "Example Weather",
"publisher": "example",
"version": { "code": 1, "name": "1.0.0" },
"compat": { "models": ["byd-sealion-7"], "editions": ["*"] },
"driving": "glance",
"licence": { "model": "one-time", "products": ["example.weather"] },
"data": ["location.coarse"],
"slots": ["home_card", "drive_chip"]
}Draft 1 of the standard. It may still change before the kit opens.