Propheski

Propheski

Propheski is a fantasy skiing app built around Olympic and World cup alpine ski races. Performance is tied directly to race outcomes, predictions, and league standings over the season.


The goal is to make following competitive skiing more engaging, and social.

Fantasy skiing felt confusing and inaccessible

Fantasy skiing felt confusing and inaccessible

Fantasy skiing felt confusing and inaccessible

Product design, 2025

Skiing is niche and unfamiliar to most people, including me. The existing app felt outdated, and key flows like team setup, predictions, and leagues were hard to follow. That friction narrowed who could realistically use the product, which in turn limited growth and revenue potential for the company.

Learn the game, then simplify it for everyone

Learn the game, then simplify it for everyone

Learn the game, then simplify it for everyone

Product design, 2025

Designing propheski started from a place of unfamiliarity. Skiing and fantasy sports were far from my everyday reality, so understanding the product meant first understanding the behaviour behind fantasy games from a player’s point of view. Using different sports app and participating in FPL helped.

I was able to focus on reducing cognitive load by breaking each action into clear, repeatable steps, especially for people who may not follow skiing closely. The aim was to make decisions feel guided rather than overwhelming.

Visually, I kept dark mode to stay familiar to existing players while introducing icy blue accents to reflect the cold, alpine nature of the sport. Card-based layouts, subtle blurs, and controlled gradients were used to create a modern, elevated interface that remains compact and easy to scan during live moments.

What I learned designing Deal Page

Easy is relative: When we tested letting users type directly into the builder, we assumed it would feel fast and intuitive. In reality, internal developers got confused and skipped sections, which created errors. Introducing a side panel for each section helped guide users step by step and made the process truly easier.


Structure reduces mistakes: Allowing free placement of elements on the page led to inconsistencies and missing information. Enforcing a clear order with fixed sections reduced errors and made the builder more predictable while still letting users complete their tasks

How I took the old design from 0 to 100.

How I took the old design from 0 to 100.

The home page

Product design, 2025

Before: The homepage was dominated by multiple leaderboards competing for attention. You landed there and immediately had to figure out what mattered and what you were supposed to do next.


Now: I treated the homepage like a quick check-in, not a stats page. Now the first things you see are your teams, your budget, and your most recent predictions. You can immediately tell what’s active, what’s coming up, and where you stand in your leagues, without digging through rankings.

Creating a Team

Product design, 2025

Before: Creating a team happened on one crowded screen. Athletes were picked from dropdowns that showed only names and prices, so you were basically guessing.

Now: I slowed this part down and gave each choice more context. Team creation is split by discipline, with a clear budget tracker and visible slots for each athlete. When you tap a player, you can actually see who they are, how they’ve been performing, and how their price has changed before committing.

League details

Product design, 2025

Before: The league screen tried to show too much at once. Standings, races, and matchups all lived on the same screen, which made it hard to understand what you were looking at or where to go next.


Now: I reorganized the league experience around how people actually think about leagues. You start with a simple list of all your leagues. Inside a league, information is grouped into clear sections: standings, races, and knockouts. Each section answers one question at a time, so it’s easier to follow progress and understand your position without feeling overwhelmed.

Making predictions

Product design, 2025

Before: Making predictions and reviewing old ones happened on the same long screen. Rules were easy to miss, and past predictions were buried below the form.


Now: I separated creating a prediction from reviewing results. Predictions are created in a focused flow, with rules easy to access if you need them. Once submitted, predictions become clear cards with a status like open, live, or finished. When a race is over, you can easily compare what you predicted with what actually happened.

Leaderboard

Product design, 2025

Before: Leaderboards mainly showed up on the homepage, which made the app feel noisy and distracting.


Now: I gave leaderboards a clear home, without removing them from the league experience. Leaderboards now have a main place where you can easily check your ranking, but they’re still accessible inside each league. This way, standings are always visible when you need them, without overwhelming the rest of the experience.

Lessons learned...

Lessons learned...

Lessons learned...

Product design, 2025

You can’t design what you don’t understand. Using the Fantasy Premier League and actually playing the game helped me to learn how everything works. I joined leagues, built teams, made predictions, and over time the logic clicked.

It even became fun. I created a team without players from my favourite club because they are “not on form” this season (we've had 3 off seasons btw).

That hands-on experience shaped my decisions on team creation, predictions, and league views, grounding the design in how it truly feels to play and compete rather than in assumptions.