My Role
Designed the Android Auto app interface
Led the beta testing process
Refined the design through feedback driven iterations
timeline
Spring and Summer 2024
impact
Increased Android user engagement by 42% and retention by addressing a key customer demand
Enhanced user satisfaction by delivering a highly requested Android Auto feature
DEfine
unhappy campers
We had been underserving our Android users by not offering Android Auto. While most of our users have iPhones - Android users make 30% of our users - there definitely was a need for this feature. We often heard things like:
There is no Android Auto app which is a deal breaker... I heard others at the campground say they felt the same way. - Tom
Make Android app support Android Auto. This is a HUGE Frustration! - Aaron
If it worked with Android Auto I would have been happy to continue. - Julie
Design
Creating the App
Our CarPlay app served as our starting point, but Android Auto specific limitations often only became clear during development. I collaborated closely with a developer to design the app, enabling a short feedback loop and rapid iteration.
Goals
Our goals were to make Android Auto:
Safe and simple to use while navigating
Aligned with our mobile and CarPlay application, which was part of a broader goal of enhancing consistency across our tools
Compliant with Google’s many limitations
Research
User Outreach
We had a list of 55 users who expressed interest in this feature either to our Product Owner at trade shows, or to our Support team. I sent out an initial feeler email to our list and within 20 minutes we had over 15 responses. One user even posted about this in a forum so we actually had users reaching out to us to participate!
Beta Test
We opted for a closed beta test. I didn’t want to open the beta test wide due to safety concerns of users unknowingly using the feature while it was still in beta.
Once we had a list of confirmed participants, I emailed them step-by-step instructions on how to set up the beta test and share feedback. To keep the feedback focused, I asked users to keep these questions in mind:
Have their been any instances of app crashes?
Have you encountered any bugs?
How is your experience with the app, overall?
Analysis
Beta Test Results
Most of the feedback was related to bugs and crashes which our developers resolved quickly.
We did receive feedback about some other known issues - like low voice volume control and inconsistent shield icons - which we have since been working on improving.
Overall, users are very happy with how the feature was working:
We have LOVED having RV LIFE working via Android Auto as that really helps!!!! Thank you for doing that. - Erin
We liked the interface, the layout is great and not messy - TJ
Upcoming features
During the beta testing we inadvertently gained additional insights into our users needs and pain points. One key point was that users dislike having to pull over to change their route and usually they have a co-pilot who can make these types of adjustments. We now are working on these new features which users can use while navigating:
Remove Stop
Allowing users to skip their next stop while multi-stop navigating
Search Along Routes
Allowing users to search for POI’s, like fuel stations, while navigating
Wrap Up
Learnings
Beta Testing Best Practices
This was our first time conducting a beta test and it was a good learning experience to develop best practices. For one, we set up an inbox just for feedback which helped us stay organized.
Importance of Short Feedback Loop
A part of the success of this project was the collaboration between me, our developer, and the Product Owner. The goals were clear and the roles were defined so we were able to iterate quickly based on our user’s feedback.
One last thing
RIP
These are some of my favorite outtakes of early iterations - look at the Speed Limit sign! (Don’t worry, these never went live.)
