When INRIX acquired OpenCar, they wanted to reflect the INRIX brand and also integrate our traffic analytics, navigation, and Autotelligent data into a new OS and a suite of apps. This platform would provide a car platform for automakers and developers.
OpenCar has an open framework and environment that can be built once and used for any number of OEMs. The OEM has complete control of the platform, including how data comes from the car and how users interact with it.
The connected car platform itself is for drivers, but the individual apps we designed for are B2B.
We went with a customer-first approach, where we optimized the experience for drivers and created guidelines for B2B to follow when integrating the OpenCar platform.
Users interacting with their cars is in flux right now; with the high use of touchscreen devices, more cars are integrating touch screen interfaces but at the risk of safety.
My biggest challenge was determing what user’s really want to do when they’re driving, and acommodating for ambiguous interaction elements with car hardware.
I worked on creating flows and layouts for different app types, such as music and content apps, including TripAdvisor and iHeart Radio.
I had influence on interaction models and design patterns by thinking through different use cases. I worked alongside other designers that focused on establishing the design language and prioritizing the work at hand.
The new profile alongside the apps were first presented at the 2016 Denver Auto Show and received positive feedback on profile and app integration.
This was our baseline of what the OpenCar OS experience and interface was like. From the perspective as a user experience designer, I evaluated and noted particular elements that worked and could be improved upon.
The team decided to focus on the busy commuter persona since they make up the majority of our users.
Before working on wireframes, I analyzed TripAdvisor and similar apps to distinguish which elemenets set them apart from others. With that information, I then put together an information architecture diagram based off primary use cases.
Besides TripAdvisor, I worked on other apps such as iHeart Radio. I created loose sketches, which were enough to get my concepts across to the team and determine what's feasible given the needs and constraints.
Through design critiques, the design team helped me improve the user experience by asking clarifying questions and realize elements I haven't considered previously.
Once the the other designers had finished wireframes and solidfying the flows for a number of key apps, I identified unique screens and worked with the visual designer to get a visual style guide.
After going through a few iterations of wireframes while receiving feedback from the team and discussing interactions of the apps, I applied visuals to the wireframes.
Here's a quick demo of interactions along with animations to get into an app.