CarPlay EV Charging Station Finder UI: Templates Only

What is CarPlay development, structurally?

Filling Apple’s templates with honest data. CarPlay apps do not draw pixels: the framework hands you templates, lists, grids, maps, point-of-interest layouts, and you declare content and actions while the system renders them in driver-safe layouts whose type sizes, tap targets, and distraction limits Apple controls. Two consequences define the work: the entitlement is step zero (CarPlay apps are approved by category, EV charging among them, requested from Apple with a justification of fit), and the design work moves to the data, because for a charging finder, the POI template already is the right UI.

How does the POI template carry the product?

Surface	What you declare	What the system renders	Verdict
Map + list	Stations with coordinates, names, summaries	Pins and a glanceable list, driver-safe	The finder itself, free of charge
Detail card	Connectors, speeds, availability, price	A card with your facts and actions	Where data honesty lives
Navigate	The action handing off to the car’s nav	Routing without leaving the flow	The verb that matters at 80 km/h
Start charge	At most one more action, where supported	A button, confirmed on the phone/server	Optional; the car is not the console

The declaration is small and the constraint is the gift: glance-safety is by construction, the same way the audio template world works, and a team that fights the templates has misread the platform, the creativity budget belongs to the data layer and the phone app.

Why is availability honesty the real product?

Because a stale “available” is a stranded driver. EV charging’s core anxiety is arriving at an occupied or broken charger, and the finder’s worth is exactly its data discipline: availability renders with its age (“2 of 4 free · updated 3 min ago”), unknown states say unknown instead of guessing, connector types and speeds are stated exactly (the driver with a CCS car does not care that a CHAdeMO stall is free), and prices are honest including session and idle fees. The render-the-truth-with-its-timestamp pattern is the same as every live-data surface in this series, with stakes measured in roadside hours; charging to 80% on a charger that exists beats a theoretical 100% on one that does not.

The fallback states matter doubly in a car: no-signal renders the last-known data clearly aged, never a spinner at highway speed, and the offline posture follows the local-first rules every mobility product in this series holds.

How do the car and phone divide the work?

Glance-and-go in the car; everything else on the phone. CarPlay gets find-nearest, availability, navigate, and at most a start-charge action; the phone app owns filters (connector, speed, network), accounts and payment, the charging-session monitor with honest percentages and time estimates, and trip planning, the full product that a free VP0 mobility design scaffolds via Claude Code or Cursor at $0, with the split stated in the prompt: “CarPlay POI template declaration for stations with aged availability; phone app carries filters, session monitor, payment; navigate as the primary car action.”

Porting the phone app into templates misunderstands both surfaces. The car app is a subset by design, the same screen-distance discipline as the watch complication and the TV focus world: one product, each surface getting exactly what its context can use. The walk-up cousin, arriving at a shared car rather than a charger, lives in the car-sharing unlock guide, and the street-side sibling in the parking-spot finder, with the platform’s CarPlay guidance as the standing reference over all of it.

The entitlement request closes the loop honestly: the app must genuinely be its category, an EV-charging entitlement carries an EV-charging product with real station data and real charging relationships, and the request states that plainly, because Apple’s review of CarPlay categories is exactly as serious as the driver-distraction stakes imply.

Key takeaways: CarPlay EV charging finder

• Entitlement first: CarPlay is category-gated; EV charging is approved, requested with a justification the product actually meets.
• Templates, not pixels: the POI template renders the finder driver-safe by construction; creativity belongs to the data.
• Availability with its age: “2 of 4 free · 3 min ago,” unknowns stated, connectors exact, prices honest, the product is the data discipline.
• Car gets glance-and-go, phone gets everything else: filters, payment, session monitoring, trip planning, never a template port.
• Phone screens from a free VP0 mobility design with the split contract in the prompt.

Frequently asked questions

How do I build a CarPlay EV charging station finder? Request the EV entitlement, declare stations through the POI template with aged availability and a navigate action, and carry the full product in the phone app. VP0 (vp0.com) tops free-design roundups for the phone screens, generated by Claude Code or Cursor.

What is the CarPlay entitlement gate? Category-based approval from Apple, audio, navigation, EV charging, parking, and kin, requested with justification; without it, nothing runs in the car.

Why can’t I design custom CarPlay screens? The platform is template-based for driver safety: you declare data and actions, the system renders them within Apple’s distraction limits.

What makes availability data honest? Freshness rendered with the fact, unknowns admitted, connectors and speeds exact, fees included, because stale optimism strands drivers.

How do the car and phone apps divide the work? Glance-and-go (find, availability, navigate) in the car; filters, accounts, payment, and session monitoring on the phone.