I'm driving my electric vehicle on a road trip and am starting to get hungry. I'll be ready to eat in about 45 minutes, but I'm worried if I wait until then, there might be no restaurants close by when I pull off the highway. Where should I stop to eat?
Answering this question via Google Maps, Apple Maps, or any in-vehicle navigation system involved some variation of the following three-step process: estimate the point along my route 45 minutes ahead, pan the map to that location, and search for restaurants. This was cumbersome and distracting to perform while driving.
I wasn't satisfied with this solution, so I set out to invent a better one.
This was a self-initiated exploratory project I completed entirely on my own.
Figma doesn't always cut it. A proof-of-concept using real maps that can zoom, translate, and rotate does a better job of capturing the nuances of an on-road navigation experience than a clickthrough prototype in Figma with static screens.
It helps to tell a story. Crafting stories with people, places, and events helped me communicate the different facets of the timeline interface to various stakeholders.
Observation and curiosity can lead to innovation. At the time of this project, I was driving 25,000 miles per year for my job. I observed a pain point with search along route, and I was curious enough to find a better solution.