What's the difference between Android Automotive and Google Built-In?

The investable question is not whether Gemini improves the cabin experience, but who owns the customer interface, usage data and monetization rights. Google can strengthen its distribution position and keep drivers inside its services, yet automakers retain leverage if they can substitute their own assistants or limit data access. GM’s dual-track strategy is therefore both a hedge against dependence on Alphabet and a potential cost/UX burden; it is not evidence that either system will generate attractive revenue. Rivian’s unbranded use of Android architecture similarly shows that Google can gain technical reach without owning the vehicle relationship.

Near term, this is unlikely to justify a material Alphabet earnings revision absent disclosed licensing economics, paid-service conversion or advertising/data monetization. For Apple, native systems create a distribution risk to CarPlay, but consumer resistance and the continued value of phone continuity make an abrupt displacement thesis premature. Over 6–18 months, automakers that control the assistant and vehicle data could capture recurring software value; the counter-risk is safety, privacy or reliability failures that make drivers reject voice AI and regulators constrain its use.

Contrarian read: feature launches may overstate commercial progress. The key missing evidence is adoption and retention, willingness to pay, automaker rev-share, data rights, and whether AI reduces support/friction costs. Treat this as a strategic positioning watch, not a near-term earnings trade.