Android Auto
A phone companion for compatible car displays. Find parking and prepare your stay from the vehicle interface.
In-car · Coming soon
From the dashboard
to the kerb.
Parking where the driver already is: on the car’s own display. The same zones, prices and session as the IPark app, with the phone taking over when you leave the car.
Coming soon · IPark in your car
Park the car.
Keep the connection.
In-car parking · Coming soon
Bring parking to the vehicle display with planned Android Auto support and dedicated Android Automotive OS apps. One session follows you from the car to your phone.
- Android Auto · planned
- Android Automotive OS · dedicated app planned
Planned for compatible vehicles. Supported platforms, vehicle models and launch timing will be announced before release.
Ask about in-car availability
Android Automotive OS
A dedicated app installed in supported vehicles, connected to the same IPark services.
One shared session
Continue on your phone after leaving the car, with the confirmed session available to inspectors.
The driver experience
One parking session.
Two screens in sync.
While parked, review the vehicle, location, duration and price. The confirmed session follows you to your phone.
How it would work Car display
Portland Crescent · Manchester
- Vehicle
- MA21 PRK
- Duration
- 1 hour
- Total
- GBP 2.00
IPark · Your phoneReady when you are— — : — —Confirm on the car display
Local simulation · no payment · no vehicle connection
From concept to integration
The business flow.
The engineering behind it.
The car becomes one more IPark client. Parking rules and payment decisions stay in the platform, where they already live.
The same rules, wherever you start.
The same zone, tariff and maximum stay apply on every screen. A session starts only after payment is confirmed.
Native car surfaces. Shared IPark services.
Android Auto uses a companion on the phone. A dedicated Android Automotive OS app runs in supported vehicles. Both would use platform-approved interfaces and IPark services.
Confirm once. See it everywhere.
Vehicle and phone read the confirmed session from IPark. Expiry reminders continue on the phone.
Car companion + phone appIPark API · rules and paymentsShared session · console and inspectors
Integration notes
What exists today: zone lookup, payment intents with server-side verification, and active-session reads — all behind the same driver authentication and vehicle-ownership checks the mobile app already uses.
What is new: native car companions, hand-off between car and phone, platform-compliant payment authorisation, retry-safe session start and recovery after a lost connection. A session is never shown as started until the platform confirms it.
Release depends on platform entitlements, approved templates, driver-distraction guidelines, simulator and in-vehicle testing, and store review. This scene is a product concept: IPark does not currently ship a CarPlay, Android Auto or manufacturer integration.
Questions & answers
Common questions
about this part of IPark.
Getting to know IPark? Start here.
All questionsWill IPark be available in cars?
Android Auto and a dedicated Android Automotive OS app are on the roadmap. Supported vehicles and launch timing are not yet announced. The preview is a local simulation.
How does a driver pay for parking?
The driver picks a saved vehicle, confirms the zone — detected by GPS or found by address — chooses a duration and sees the price before paying. The session starts once payment is confirmed, and the app sends a reminder before it expires.
Make your parking network work together.
See the platform with your zones, teams and operating requirements in mind.