Stage 1.Overview
Fixar helps users keep track of their car maintenance. It can be difficult to remember when the last oil change or other important maintenance tasks were completed.
Additionally, it can be challenging to track which parts of the car need to be serviced based on the car's mileage. In this case study, I will showcase the entire process, research, results, and learnings that I gained from creating this application.
Stage 2. Goals
Creating an easy-to-use and intuitive application, considering that the project had a technical theme.
Applying the knowledge gained from the Trazos course and current job experience.
Designing a mobile MVP app with a flexible structure that can scale and grow over time.
Stage 3. Research
I reviewed the general panorama of applications of workshops, vehicle repairs... I chose the 5 most outstanding in terms of quality, popularity and relation to the results expected by the client: CARFix, Mechanical appliance, Viday, Tallergp, Carpower.
This analysis had the following parts:
General: where the app was evaluated globally, visula design, user view, colors, information hierarchy...
Meeting: the dating process with the chosen mechanic. It was checked if the chat was clear, if it had a map to choose the nearest workshop and find by average evaluation...
Payment: the user would have to have a record of the payment made, which would allow the main current means of payment, Paypal, card, payment by company.
Others: at this point, include whether there was gamification, any loyalty system to the application, and in some way some statistics that the user could review about his car.
From this study, I compiled the pros and cons of each one, what I considered the keys to success, the threats and the fields of opportunities, giving the following recommendations for the design of the new app, the business model and the creation of contents:
🌈 Most of the applications had a lack of visual design. There was a lack of color range, pages overloaded with information, lack of information hierarchy, lack of onboarding.
🗺️ Visualization of the map to find the nearest mechanic. This is a critical point because in the case that the car has a critical failure it is important to find the closest one.
💵 Lack of a good payment method in which the bills are collected and also the mechanic could anticipate a budget.
💎 Lack of gamification, most applications needed a loyalty system.
The world of mechanics needs digitization, in workshops it is usually used computers with old operating systems and programs compatible with them.
Stage 4. User persona
After conducting interviews with my friends and family, I realized that I could define two recurring profiles.A disinterested profile in the automotive world and another pro profile that has been self-taught. The two profiles had very different goals and frustrations.
Starting with the previously defined users, their habits and expectations, I began to define characteristics of the application, prioritizing and analyzing them with the client.
After some meetings, we decided to focus on the most important parts that would define the MVP:
Home: the place where you can have a quick overview of the status of our vehicles.New meeting: gathering all the information from the user regarding their vehicle problem.Chat: a space dedicated to conversation between the workshop and the user.
With these characteristics in mind, I started to draw flowchart, low fidelity wireframes (papper and digital) that I would send to the client for their opinion.
