How to check whether a car’s Google apps will work in the UK
A practical UK buyer checklist for separating Android Auto, built-in Android Automotive OS, in-car Google Play, supported apps and future software plans.
Start with the exact car, not the label
A phrase such as “Google built-in” sounds like a complete answer. For a buyer, the useful answer is narrower: does this exact UK-specification car run the platform you mean, can it use the app you need, and is that true now or only planned? Check those points separately before treating a brochure line as a feature you can rely on.
Write down the make, model, trim, model year and UK specification of the car you are considering. If it is a particular demonstrator or stock car, add its infotainment software version if the retailer can show it. If you are ordering a car that has not been built, say so. A general model-family answer may not settle a question about one trim, year or market version.
Separate Android Auto, Android Automotive OS and Google Play
These names describe different things. Google’s Android for Cars documentation says Android Auto uses a phone connected to a compatible car display. Android Automotive OS is built into the vehicle, where apps can be installed on the car itself. Google Play is the app distribution service in the XPENG announcement; ask the seller to name the actual in-car system and what it does on the vehicle you are buying.
A car that offers Android Auto does not, on that fact alone, have Google Play installed in the car. Nor does an advert using “Google” tell you whether it means phone projection, a built-in operating system, a particular Google service or a future software plan. Ask for the exact feature rather than accepting the label.
Check the app you need
Name the app you would actually use. Ask whether that named app is available from the in-car store on this vehicle, in the UK, for the software version shown. If possible, ask the retailer to demonstrate it in the car while parked: open the vehicle’s own app store, find the app and show that it launches on the dashboard. A phone app, a screenshot or a broad list of supported app categories is not the same demonstration.
Google’s developer documentation says car platforms support only certain app types because cars have requirements of their own. That is a reason to check one app at a time. Do not assume that an app available on a phone, or an app category mentioned in a general platform guide, will be offered in every car or market.
Separate a live feature from an announcement
Record the answer as one of three things: demonstrated on the exact car; confirmed in writing for that exact model, version and market; or announced/planned with details still to come. If the seller cannot confirm one of those, write “not confirmed” rather than filling in the gap from another country’s advert or a future product announcement.
For a planned feature, ask which model years and UK versions are eligible, which software version it requires, when it is expected, and how it would reach the car. If the update route or timing has not been published, ask the seller to say so. Do not convert a general promise of ongoing app updates into a promise that your current car can be upgraded.
Keep a short record you can compare with the order
Ask the retailer to answer this in writing: “For the [model, trim, model year and UK specification] I am considering, can you confirm whether [app name] is available directly in the car through [named platform] on the software version shown? Has it been demonstrated on this exact vehicle? If it is planned rather than available, what eligibility, expected timing and update route have the manufacturer confirmed? Please mark any detail that is not yet confirmed.”
Keep the reply with the vehicle specification and date it was checked. If an answer changes between an advert, a demonstration and the order paperwork, go back to the manufacturer or retailer for the specific point that changed. This is a practical buyer’s record, not a technical certification or a guarantee that an app will remain available.
A dated example: XPENG’s Google Play announcement
XPENG’s pressroom announcement carries a 16 October 2026 heading and a 15 October Paris dateline. The company said it planned to bring Google Play directly into its cars in early 2027 and described the integration as based on Android Automotive OS. It said participating models, markets and app availability would be announced later. The release’s “100+ countries and regions” wording describes the broader app ecosystem, not a list of XPENG markets.
That announcement is a useful prompt for the questions above, not evidence that a particular XPENG model sold in the UK will receive the feature. The release did not name eligible UK models, apps or an upgrade path for existing cars. Confirm those details against the exact vehicle when the manufacturer publishes them.
Frequently asked questions
- Does Android Auto mean Google Play is installed in the car?
- No. Android Auto connects a phone to a compatible car display. Android Automotive OS is built into the vehicle and allows apps to be installed on the car.
- Does XPENG’s announcement confirm Google Play for a UK model?
- No. XPENG said the integration was planned for early 2027, with participating models, markets and app availability to be announced later.
- Does an app being available on my phone mean it will run in the car?
- No. Check the named app in the vehicle’s own store and, where possible, ask for a demonstration on the exact car.
- What if the retailer cannot confirm the software version or update route?
- Record that detail as not confirmed. Do not treat a planned feature or a general model-family answer as confirmation for the specific car.
Keep reading
Put the numbers to work
Turn a WLTP figure into a realistic UK winter range, or see what salary sacrifice saves on your tax band.