context
For years, our users have requested Android Auto integration. Many have cited this as a key reason for not renewing their subscriptions in our Exit Survey. Acknowledging this clear demand, I collaborated closely with a developer and the Product Owner to bring this feature to life. To ensure a seamless launch, we conducted a Beta test to identify any potential bugs and confirm the feature’s reliability before rolling it out wide.
Timeline
Spring and Summer 2024
MY ROLE
Designed the Android Auto app
Facilitated beta testing
Iterated upon the design based on feedback
OUTCOME
Made users feel heard by providing them with a feature they had been requesting
Attracted and retained Android users
Define
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.
If it worked with Android Auto I would have been happy to continue.
Design
We had an existing CarPlay app which served as our starting point, but there were many details to sort out which were Android Auto specific. I collaborated closely with a developer on designing the app. 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!
Research
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 how to 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?
I also told users that for now we're not seeking feedback on routing or other features.
Analysis
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.
We liked the interface, the layout is great and not messy
ANALYSIS
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
“I want to be able to remove an upcoming stop and navigate directly to the next stop.” Ed
Search Along Routes
Allowing users to search for POI’s, like fuel stations, while navigating
“Selecting POI’s along my route would be great” Laura
Wrap Up
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.
The Value of User Engagement
It was rewarding to offer users a long-desired feature and to connect with them through emails and forums. It’s very fulfilling to have direct communication with users.
Collaborating with Developers
I worked alongside a developer to design the app so that it met the guidelines set by Google. We both learned to understand each others perspectives and anticipate questions.
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
These are some of my favorite outtakes of early iterations - just look at the Speed Limit sign! (Don’t worry, these never went live.)
