Carspecs APP

The use of Carspecs 5 (web tool) started to increse on mobile devices in 2019, around 15% more than 2018, so we predict that for 2021, it will be around 45% users using our tool on mobile devices.

That's the reason why we started to think about how to improve UX for mobile devices. First we just wanted to improve Carspecs 5 (web tool), but we discoverd it wasn't enough, the response time of the UI with the API services, one of the user pain point that we found, wasn't able to improve because of the technlogy that we were using. Also we compared how much effort will take to improve/migrate what we already and the result was similar to build a new product, so, our team proposed to create a native App.

We decided to use Design Thinking methodology to get a better solution, to discover real user problems and solve all their needs.

The best part is that we didn't have to start from 0, we had a lot of information about how users have been using Carspecs 5 on mobile devices, so we starting to analize all those insights, the behaivor of the users, we started to detect some user pain points. But we realized it wasn't enough, so we started to do more research about it.

We started with stakeholders and end users interviews, to know how they were seeing Carspecs 5, and how do they imagine a Carspecs App, we had sessions, with end users, asked them to make specific tasks on Carspecs 5 (on mobile devices), to observe how they were interacting with the web App and detect and get all the information to create personas profiles and be able to create a functional and affortable solution.

With all the insights and data analized we started the ideation process. We had brainstorm sessions to find possible solutions, what should and what shouldn't have the App we were building. Which were the best technologies to do it, if those technologies were compatible with our ideas. We compared similar ideas to see if we will be able to adapt or to implement same solutions, or to combine different solutions to solve our problems.

We identified that users were using the saved selections button, more than we thought, that's why we decide to run a test with saved selection button at the beggining of the user flow (ones is logged) or at the beggining of the selection process (just as we had on Carspecs 5).

Result: Most of the users, didn't see the saved selection from the second prototype, they continued the selecting vehicle process, and then, when they realized they forgot to open saved selections, they returned to the beggining of the process and then they saw the saved selection button. So, as a conlcusion, we decided to go with the first prototype, because we were saving users time, and we were doing it more evident to start a process with the regular selection process or with the saved selection process.

We identified another problem, the user lost the vehicle information, so we did another test, now, with fixed columns on the vehicle comparison report.

Result: The user was able to see which specific data was watching and for which vehicle belongs.