This project is about how to design a native app into a specific platform such as iOS and Android. It is therefore able to take advantage of all of that platform’s features through its native operating system, generally providing a better experience. The theme is meditation, which helps users to learn how to meditate, relieve anxiety, and stress.
This project is about how to design a native app into a specific platform such as iOS and Android. It is therefore able to take advantage of all of that platform’s features through its native operating system, generally providing a better experience. The theme is meditation, which helps users to learn how to meditate, relieve anxiety, and stress.
This project is about how to design a native app into a specific platform such as iOS and Android. It is therefore able to take advantage of all of that platform’s features through its native operating system, generally providing a better experience. The theme is meditation, which helps users to learn how to meditate, relieve anxiety, and stress.
Company
365scores
Project Name
Native App
Dashboard
Platform
ANDROID & IOS
Project Overview
Redesign and rebuild of existing Native application
To experience the full product
Android
IOS
Company Overview
365Scores is a sport application that presents live scores and various content for millions of users around the world, and one of the 5 most popular sport application worldwide.
Project Overview
The project was to redesign and rebuild the existing Native application, driven by both the need for its growth and the shifts in the regulatory market that opened doors to adding the gambling-related content. These opportunities created new business goals and therefore new requirements for the application.
I started from the dashboard area - an essential focal point for user navigation. It was the first big milestone in transforming the product visually and targeting a new audience.
Challenge
To deal with the challenges in this project I had to study the world of live sports results at every level. That meant getting to know our competitors, understanding the global market, and figuring out where it's all headed.
I needed to learn the diverse range of users across different countries and continents.
Every decision I made here was a big deal because it could impact our current users and shape the future of our products. From the content we offer to how it looks and works, it all matters.
Goals
These are the main goals that were defined for the project:
Define UX Strategy
Product & Brand Style Guide
Design System
Define workflows with other teams in the company
Design Process Overview
2
3
4
5
6
Project Kickoff

"Coming together is a beginning, staying together is
progress, and working together is success."
- Henry Ford -
To kickstart a project, it's crucial to gather key players from various teams such as development, product, and marketing. To make sure we had a smooth start, I organized a kick-off meeting well in advance, giving everyone time to prepare. They were encouraged to come ready to share their insights and discoveries in line with the project's objectives. During our discussion, we addressed challenges and defined the project roadmap, consciously avoiding diving into design details at this early stage.
Research
I had to dive deep into market research, usability testing, and user feedback. For that, I used a variety of research methods, like interviewing users and stakeholders, brainstorming sessions, and running surveys tailored to different groups. Furthermore, I had to scope out the competition and take a global view, examining what's happening across various regions and continents.
Market research
Research methods
Focus groups
I set up meetings with application users involved in the process, splitting them into groups based on topics, like different sports, users interested in gambling, and people from various countries, cultures, and languages. These sessions usually happened more than once to explore more information and foster collaboration.
Stakeholder interviews & in depth interviews
I had individual interviews with key stakeholders whose insights and perspectives helped me to gather a better understanding of the field and were crucial for the decision-making process.
One of the most sensitive issues was integrating gambling content into the application without overtly branding ourselves as a gambling company
Competitors Analysis
To analyze our competitors we selected specific comparison points where we knew we could gather data using various tools available on the market. These points included:
Revenue analysis
Identifying advantages and disadvantages
Assessing strengths and weaknesses
Competitors market size and audience
UX research
My goal in UX research in this project was to find how to make the product more appealing and desirable to users. To do that, I needed to explore several key areas:
Understanding the current product landscape, including our product and competitors, and how users interact with them.
Identify user needs, requirements, expectations, and their overall sentiment towards our product and competitors' products.
Identify existing user behavior patterns and trends.
Explore opportunities for new features.
Assess the optimal information architecture and implementation strategies.
Pinpoint areas for enhancing user experience.
Research methods
User interviews
The majority of 365Scores employees were active users of the application, and some of them also used similar applications within the same domain. As such, their insights were super helpful not only in the initial stages but also in guiding usability testing during the later stages of the project's development.
Surveys
We formed focus groups consisting of individuals with shared interests.
The goal was to test how potential users reacted to the new navigation and content architecture.
Product analytics
Since the company already had a BI team, we tapped into their data, and I also explored other tools available.
We examined various metrics to gauge how we could improve user experience.
DEMOGRAPHICS
SPORT FANS
100%
Sport fans
85%
18-34 years’ old males
68%
Online shoppers
72%
Technology enthusiasts
72%
Users have a university degree
40%
Users Select more than 1 sport type
24%
Leagues selected on average
1000
Notifications / month
16%
Teams selected on average
Ideation
After thorough research, I and other stakeholders were ready to discuss new ideas for the product. To do that we used several methods to bring up and present these ideas and ensure they were in the right direction.
User Stories
User stories gave us a practical view of our users' needs. By stepping into their shoes, I got a picture of how the product fits into their daily lives - how often and when they use the application, how long they stay, and what info they are looking for. For instance, it surprised me that many users check the application even during a live game at the stadium.
This user-centric approach brought up some fresh ideas and creative solutions we wouldn’t come up with otherwise.
User Flows
When defining User Flows it was important to distinguish between users interested in gambling content, like betting statistics, odds, and expert opinions, and those looking for info about their favorite teams or players. I discovered that both types of users had more similarities than I initially realized. The main differences were basically how often they entered the application and how long they stayed in the session.
Wireframes
I used wireframe screens and basic prototypes to map out the flows.
It helped me visualize how the new components could present all the data, the information flow, where buttons should go, what microcopy to include, the size of cards, and what navigation options to use (text, icons, or both).
The most challenging was dealing with dynamic data in multiple languages, and multiple regulations (results presentation is not the same in different countries and different sports), and on all sorts of devices, even older ones with low resolution.
Define
The next step was to create requirements definitions for the development of our Native application for both IOS and Andriod.
Mockups & Prototype
I started to work on comprehensive mock-ups, covering all the UX components - screens, buttons, cards, microcopies, etc; added animation to them, experimented with different styles, and played with colors combinations, fonts, and icons. It was crucial to ensure that everything functioned seamlessly across various languages and could handle different content volumes. I continuously gathered feedback from active users within the company to ensure that the content was easily understood on visually appealing screens. I paid close attention to details like text size, contrast between content layers, and whether the design sparked curiosity for further exploration. Ultimately, I evaluated whether the user journey flowed smoothly and whether I successfully guided users to the areas I wanted them to explore.
Another objective at this stage of the project was to determine which components to use as native and which ones to customize. Since the product is available on both Android and iPhone platforms, I collaborate with two separate development teams, each with its own set of requirements. Decisions needed to be made on how to align the two platforms, aiming to establish a unified design system for the product that would enable scalability and maintenance in the long run.
Design
Style Guide
Creating the design language for the product involved lots of experimenting, testing and brainstorming with the relevant people. We ended up giving the product two user-selectable skins - dark and light. To streamline things, I decided to create one main style that could be split into these two skins with specific components. This made it easier to manage and maintain it and also to expand or transfer it to other products smoothly. Additionally, it worked well with Android and iOS development teams.
For instance, I decided to keep the application header consistently in the dark skin, while allowing the other tabs and sections below to adapt to the user's selected skin. This approach helped build the structure of our components, ensuring clarity for everyone involved in the process.
Design system
The design system for our product was divided between Android and iOS, each with dark and light themes. At this point, I'd already sorted out which components would be native and which would be custom-made. We've also nailed down the design style for the product's icons style.
Since this design system would also serve as the foundation for future products, it was crucial to ensure that the system I developed could handle a variety of components and adapt smoothly as the product expands.
Some examples from the system
High Fidelity Screens
Creating final screens for both platforms - Android and iOS
Delivery
I facilitated the "design handoff" to both development teams, Android and iOS, where we went through the screens, native and custom components, key highlights, and other important details together. These meetings were also super important because of the complication and amount of different components we had. It needed good coordination and communication between the development and product teams and myself to make sure everything was aligned and accurate.
QA & Analytics
Two critical factors for the project's success were our approval processes and continuous design monitoring throughout development. Every component needed to pass design approval with each version release, ensuring nothing went live without proper vetting.
Additionally, we kept observing components and user behavior to ensure alignment with our KPIs. We utilized BI tools to gain comprehensive insights into user interactions and overall performance.