Release model
Going live is a deliberate, controlled step. The store team releases each app version to the markets and vehicle contexts it should reach — this is sometimes called “freischalten” (releasing / making a version live).
How release works (high level)
- Release decisions are made per app version. Different versions of the same app can be live in different places at the same time.
- A version is made live for a specific set of markets (countries) and vehicle contexts (the vehicle and configuration combinations the platform targets). Only versions that are live and match a vehicle’s context are offered to that vehicle.
- You do not perform the release yourself; you prepare a release-ready version
(clean build, complete
en_USlisting, findings addressed) and the store team makes it live for the agreed targets.
Where you see your live status
In the portal, each app version shows where it is live — for which markets and vehicle contexts — so you always know the current reach of every version.
”Live with open issues”
A version can be made live even if it still has open tickets. When that happens, the portal shows the version as “live with N open issues” so both you and the store team can see, at a glance, that a released version still has findings to address. Resolve them in a follow-up version.
Lifecycle at a glance
draft → in_review → approved → live ↘ rejectedSubmit a version for review when it is ready; after approval the store team can make it live for its targets. See the feedback loop for how findings and review notifications reach you.