I reimagined how apps and activities on personal devices can seamlessly transition into the vehicle environment. By removing the need for manual prompts and creating a singular, unified visual language, the design delivers a frictionless handoff that feels both natural and effortless.
This project is a conceptual design exercise and is not officially affiliated with or endorsed by Apple Inc. Any images used are displayed for illustrative and/or research purposes.
We analyzed, in-depth, 12 vehicles (plus 1 more deeper analysis) to get a sense for the ways car manufacturers are solving problems and crafting experiences.
Trendy features can be integrated in a way that impacts safety and the driving experience. For instance, drivers have been growing frustrated by the prevalence of touch screens but Tesla have condensed almost every single aspect of the dashboard into a single touch screen.
None of the vehicles we reviewed had complete ownership over their digital UX, instead contracting services like CarPlay and Android Auto. Since each service has their own guidelines and requirements, the result is a clash of multiple visual design languages.
Manufacturers exploring new technologies will rush to bring them to market without working to incorporate them into the driving experience. For instance, this interior strip of lights is supposed to provide feedback but is too limited for any meaningful assistance.
We looked at how Apple handles transitioning between devices with a series of features under the umbrella of Continuity. One feature, called Handoff, allows eligible apps to be moved, mid-process, to another Apple device. If you're using Safari on your iPhone and open up your MacBook, an icon will appear on your desktop asking if you want to open up a browser to continue reading that website.
Personal devices are fully capable of being interconnected to create a continuous, personal experience. Is your car not a personal device?
From the initial vehicle analysis and noticing the broken mental model and disconnect between devices, I wanted to prioritize that feeling of using tech in a way that "just works".
My team and I took our user journey map through a series of brainstorming exercises and ended up writing out a variety of text-based concept flows. After several discussions, and refining some of these scenarios, this is where my concept proposal started to take shape.
One of the major things that people are averse to is seeing “Settings” pages when talking about a new feature or concept. With that in mind, I made a quick proof of concept just to show what a user might actually encounter during the actual event.
Talking with my team, I realized we would need a “home” for our concepts to work from, and we agreed on an iPad-sized screen for the center console, potentially utilizing MagSafe connections to use whatever sized screens the owner would prefer.
This new “prototype” shows a seamless interaction where the user doesn’t actually have to do anything. The devices realize they’re nearing each other and, at an optimal time, the active process (in this case, a FaceTime call) is automatically transferred over without the user needing to manually do anything.
With a revised concept of how the transition should actually occur, it quickly became apparent that the active process should take precedence over other tasks, i.e. a FaceTime call should become, hierarchically, the most important active app on the screen.
Since the phone can be placed on the MagSafe dock and used as an additional screen, we can move the clock off of the main screen’s Tab Bar. This gives us space to use the Tab Bar to form the equivalent of the Dock, which is in familiar use on many other Apple devices. This change means that the active process can now utilize the entirety of the screen.
With the clock moved to the phone, we have space to move and rearrange app icons and shortcuts into the equivalent of a Dock within the existing Tab Bar.
Like many of Apple’s features (such as Apple ID and Continuity) the magic is happening behind the scenes, and adjustments have to be made in Settings and Profiles. Showing a Settings page is a boring way to promote a new concept, especially because it’s not the part that will be most interacted with. This prototype shows how the actual user experience will play out.
We actually worked as a team to conceptualize several connected driver experiences under the umbrella of an Apple-branded vehicle. We spent quite a bit of time researching the brand and coming up with a consistent design system, including shape language and colors.
This video highlights all of these features in the appropriate context of a driver's day.