UX Case Study on Electronic Vehicle OS (Android Automotive OS) and Call rejection feature
Introduction to the project
Electric Vehicles
Electric Vehicles (EVs) are gaining traction in India as a cleaner and more sustainable option for transportation. With concerns over air pollution and environmental degradation, the Indian government has introduced incentives and policies like the FAME scheme to promote EV adoption. Electric two-wheelers (e-2-wheelers) have lower operating costs, thanks to cheaper electricity and reduced maintenance. Improved charging infrastructure is making e-2-wheelers more convenient, while technological advancements provide competitive range and performance. These factors, along with the suitability of e-2-wheelers for navigating congested urban traffic, make them a popular choice in India, helping reduce pollution and greenhouse gas emissions.
Software used by Electronic Vehicles
Android Automotive OS (AAOS) is an infotainment system built into vehicles by car makers. Android apps that support AAOS requirements can be downloaded from the Google Play Store to any car manufactured by a Google Automotive Services (GAS) partner. Instead of using a particular phone app, users install a version of the app that is designed for cars directly onto the head unit.
More on this here, on the Android Open Source Project's documentation
Please note, this is the most popular OS but the case study can also apply on non Android OS used by the vehicle firms (if any).
About my role
My role is to conduct research with user interviews, finding problems, come up with a solution, paper design/wireframe (LoFi) and a high fidelity (HiFi) design.
Research
I conducted a survey to people who actually own the EV on the internet platforms like (reddit) and few real life interactions, questions I asked are listed below. I used the "direct question" method as I only had limited time with people I interviewed:
I will take an example of two people Mohan and Amit ( real life interactions ):
Question 0. Demographics (Name, Age, Technology knowledge)
User #1: Mohan, 26, Yes, almost.
User #2: Amit, 38, Limited knowledge of technology
Question 1. Since how long are you using this particular EV and for what do you use it for regulary?
Mohan: 2 years now, initially bought when I completed bachelors now I use it to go to office everyday and to friends house, clubs etc on the weekends.
Amit: I use it for everyday tasks like going to metro as my office is far, groceries, nearby trips, gym, parks etc
2. What are the biggest problems that you faced in this EV's operating system?
Mohan: Lack of proper information related to rides, battery range, messages management and call handling, Also, updating this takes hours and often slows down the whole software.
Amit: Calling related features, it only has pick up and decline feature.
Problem Statement
Based on the research conducted, these are the problem statement that come out are listed below:
- Call decline and automated response via messages
- Energy Efficiency Visualisation
Goals
- Find a solution for the calling dialogue to be more UX friendly and allow quick decline with pre saved message sending feature.
Target Audience
Since the legal age to drive a vehicle is 18, its the minimum age and as per many articles, research papers published online, it is said that one can ride a bike perfectly in their 80s as well.
Hence, Ages 18-80.
Pain Points
1. Time:
Driving the vehicle is the main priority as it requires all the attention, hence the user has very less time to make decisions.
2. Accessibility:
EV should allow the user to send a pre-saved message like "Hey, I am driving as of now, can't pickup. Will callback in a while". This is also useful when the person is at traffic light or does not have bluetooth earbuds and wants to avoid talking in public spaces.
3. Interface
The Interface of such a feature should be very easy, minimal and quick to action.
Possible Solutions
1. A separate button to decline a call with pre-saved message response
2. Swipe to decline and send a pre-saved message response
Wireframes (LoFi) and User testing
I came up with the above two wireframes for the two solutions and As per the user testing, I asked 6 users on which feature actually makes sense according to the problem statement, and surprisingly all 6 of them voted that B is the much better option.
Final Design -- High Fidelity
Prototype and Video Demo
Thank you, if you like this project or have feedbacks, Kindly share to:
kubersh20@outlook.com
kubersh20@outlook.com
