Role
Product Designer
Scope
UI & Features
Team
Design, Devs, PM, QC
Year
2024 - 2025
UniScore is a platform that provides users with live score tracking across various sports including football, basketball, and tennis. The product is designed for everyday sports followers who want a quick and simple way to stay updated with real-time match results, rankings, and fixtures.
Understanding the Challenge
In Europe and the Americas, football fans crave more than scores — they want clear, reliable data and engaging experiences. Yet Uniscore’s outdated UI and limited features fell short of these expectations. To better serve passionate fans and data-driven users, the product needed a refreshed interface and improved data presentation that meets modern usability standards.
What needs to change for users?
Joining the project at a later stage, I noticed that many design decisions were made reactively rather than strategically. This led to scattered user experiences, unclear feature priorities, and challenges in creating a cohesive visual identity.
Inconsistent UI Patterns
Many screens lacked a shared design language. Components varied in size, spacing, and behavior, making the app feel fragmented.
Unclear Feature Strategy
Many features were added reactively without a clear prioritization or user-centered rationale. As a result, some key functionalities were missing or incomplete.
From brainstorming to solutions
This FigJam board captured our collaborative ideation session with stakeholders and developers, where we evaluated feature feasibility and business impact. The outcome helped define which ideas could realistically move forward into design and development.
Feature breakdown — Planning sheet
A snapshot of the early-stage feature tracking in Airtable. I used this board to understand scope, align with dev timelines, and keep track of feature delivery based on timeline and content type.
From feature planning to functional UI
Once the features were prioritized, I designed high-fidelity screens and gathered internal feedback within the design team. After finalizing, I delivered the designs to developers, walked them through the feature flows, and collaborated on possible adjustments. Once aligned, the features were implemented and uploaded to Firebase for internal testing across teams.
Making search more flexible
Provide users with a fast, clear, and intuitive way to search for teams, players, matches, or countries.
Instead of displaying all results in one mixed list, I designed separate tabs (Teams, Players, Matches, Country) to categorize results clearly. This made it easier for users to focus and reduced cognitive load.
Letting users personalize their experience
I restructured the Favourites section with tabbed navigation for better content separation. I also added the ability to edit and bulk-remove items using a "Select All" option, addressing a common UX pain point.
Let users choose what they want to hear
Previously, users could only receive notifications when a match was in progress. However, that limited experience didn’t support different user needs — such as staying updated on key events like goals or lineups.
To improve this, I designed a customizable notification system where users can activate alerts per match and choose specific event types to be notified about (e.g., Goals, Cards, Corner kicks, Lineup, etc.).
Scaling the experience from mobile to web
Since Uniscore is not only used on mobile but also extended to the website, I ensured a consistent design language across platforms.
Unified UI system: typography, colors, and components are standardized across mobile and web.
Responsive adaptation: layouts adapt fluidly to different screen sizes.
Seamless experience: users can switch between app and web without confusion.
Learnings & reflection
This project challenged me with its fast-paced delivery—there was no BA, and I had to prioritize features without much experience. It was overwhelming at first.
I learned to be more proactive in communicating with the dev team and leads. Their feedback helped me design with better technical awareness, and I actually enjoyed those discussions a lot.
I also realized I needed to let go of perfectionism. "Done is better than perfect" became a mindset I’m learning to adopt. Product thinking is something I’m starting to care about more—not just UI, but the why behind features.
If I could do it again, I’d double down on improving core features first, and push for more strategic ideation with the team. I’d also dig deeper into competitor reasoning, not just copy their approach.