Designing the journey, not the map.
A co-pilot tool wins by being glanceable, not by doing everything. One app that reads context on two axes: your posture (moving or stopped) and your phase (start, middle, arrival).
Road trips are fun, but the person in the front seat is juggling too much with no real tool to help.
At 100 km/h you need a 2-second glance. At a chai stop the whole group gathers round one phone. One density doesn't fit both.
Detours, delays, spontaneous stops, a trip is a living plan. But nothing helps you adapt on the fly without re-routing from scratch.
Long highways, late-night stretches, fatigue creeps in. There's no system to flag lethargy, swap drivers, or even track who's been behind the wheel too long.
How far can we go? Should we stop now or push to the next town? Without vehicle-aware data, every fuel decision is a guess.
Texts, calls, Maps, notes, the co-pilot bounces between five apps to keep everyone aligned on route, stops, and timing.
The first 30 minutes of a trip feel different from hour 4. Arrival is its own moment. Yet every app treats the entire journey as one flat state.
The driver already has Google Maps. The back seat is along for the ride. The front-seat passenger is the underserved user.
Eyes on the road. Already has Maps for navigation. Not our user, they need less, not more.
Juggles route, stops, fuel, food, group comms, the person who makes the trip actually work. Our user.
A co-pilot tool wins by being glanceable, not by doing everything. The app needs to read two types of context:
Juggles everything that isn't driving, route, stops, fuel, food, keeping the group informed.
Acts on behalf of the whole car. Their wins are the group's wins.
The Back Seat is Informed, occasionally consulted, Driver is not our user and needs no attention
One app that reads context on two axes
Changes minute to minute. Controls information density and interaction cost, a 2-second glance vs. the group gathered round.
Changes across the whole trip. Controls which contextual card surfaces, and retires it once the moment passes.
The system shifts to provide contextual data
Progress, time to next stop & to destination. The orient-me job.
Peek in motion; full detail, facilities, vibe, at a stop.
Vehicle data input to provide suggestions on refuelling, range etc.
Running late → skip, trim, or add on the fly. A trip is a living plan. Adapt to spontaneous changes of plan because of external factors.
Balance + toll forecast. Immersive view of route for zero confusion.
Group enjoys music, chatting and everything. Similarly, talk to AI rather than typing, brings better & easy conscious to the co-pilot app. Making sure app understands the needs basis duration into the trip.
Manage who's driving, swap roles at stops, and monitor driver fatigue with timely alerts.
The brief scopes to one car. Convoy is a bigger, different problem, cross-vehicle coordination, not co-piloting.
The driver already has Maps. We win by being glanceable, not by becoming competitors to Google.
The brief says design during the trip. Arrival nudges stay as a deliberate edge, not a marketplace.
Glanceability
Richness of content
Map for Reference
Map as a navigation
Phases of the Road Trip
(Start, Middle, Arrive)
Treating the whole at single level
The co-pilot's job is to make the journey smoother, quietly.
Glanceable in motion. Open at a stop. One product, two scales of context.
, Dhruv Prasad