Diego
33, a sports journalist in the newsroom of a popular Argentine outlet.
Research and an improvement proposal for the mobile version of Promiedos, the football results web app. A self-initiated project, done as a user of the app.
Pick a day and star a match: it moves up to Mis favoritos. It’s a replica with sample data.
Promiedos is a web app people use, above all, to keep up with football matches.
As a user of the app and of the category, I thought it would be interesting to do some research and propose improvements based on the insights I found.
I analyzed the competitors to understand what they are doing and why. Key to staying competitive in a saturated market.
Benchmark matrix: five results apps compared on downloads, content hierarchy, friendly interface, weight given to Argentina, community, calendar filter and favorites. Almost all of them have a calendar filter and favorites.
I compared content hierarchy, friendly interface, weight given to Argentina, community, calendar filter and favorites. Almost all of them solve the calendar and favorites, exactly the two things Promiedos didn’t have.
I ran a Google Forms survey with users of the product to understand their needs, gather qualitative data and spot opportunities for improvement.
47 squares, one for each person who answered the survey.
47participants, one square for each
26years old, the average age
I went through the app’s reviews on the Android store.
“It was a 5-star app (just like its website, which I’ve used since 2015). Looks were never its strong suit, but the historical and statistical information…”
“They removed the profiles where I had my favorite teams; they’ve been going downhill for a while.”
“It’s very complete and the results update fast. It has lots of data and you can follow several competitions.”
From the qualitative data I defined two personas to focus the proposal.
33, a sports journalist in the newsroom of a popular Argentine outlet.
22, a psychology student who works in an admin job.
With the “how might we” method I worked through the most important problems from the research.
The interface feels confusing and dated.
How might we improve the interface without breaking the simplicity and structure users already know?
Important matches and tournaments can’t be found quickly or in a personalized way.
How might we put each user’s interests first?
There’s no way to move between different days of the month.
How might we improve navigation to past or upcoming days?
I mapped out in detail how the app’s current flows worked to define the best way to implement the solutions.
Screenshots of the app in June 2023. Drag the carousel or tap a screen to bring it to the front.
The home had three buttons to move between yesterday, today and tomorrow. The calendar sat inside the menu, two steps away.
I prioritized what to redesign by the impact it would have and the development effort.
Impact and effort matrix. In, by priority: identity refresh, marking matches as favorites, calendar navigation, and icon and button changes. Left out: Prode, Gambling and Your profile.
Prode, Gambling and Your profile.
With those decisions made, I designed the prioritized flows in low fidelity and then took them to high.
The five screens of the flow at 375 px: the wireframe on top, what it became below. Hover one to see its pair.
To close the process, I designed every screen in high fidelity. This is the proposal on the phone: each priority marks its part.
Three problems, three answers. A new identity on the same old structure, favorites at the very top and a calendar to move between days.
The UI kit components every screen is built from.
Three variants depending on the chosen day. The active day goes in violet and carries the way into the calendar. Tap a day: the component switches variant.
One row per match: status, teams, score and favorite. The status sets the color of the first cell. Change the status and tap the star.
The top buttons say what they do and what state they are in. Each competition opens with its title and closes with a menu: the way into the tournament, the goal alert and which matches to show.
Components rebuilt from the design file, with sample data.