Scaling mobile products

Users can see changes in follower count, daily and weekly trends, and key account metrics, add a widget to the Home Screen, and receive recommendations from an AI assistant.

The challenge was to organize a large volume of constantly changing data without turning the home screen into an analytics dashboard. The key metrics had to be readable within seconds and work not only inside the app, but also in compact widgets.

Users set a target amount and deadline and calculate a recurring contribution, log deposits and withdrawals, join savings challenges, and explore personal finance content.

The main design question was how to make the calculations clear to someone without a financial background. Most flows were therefore built around a specific goal and progress toward it, with simple charts and clear actions replacing complex financial terminology.

In the app users can browse upcoming matches, select an event and book a table or VIP room, and later manage the reservation from their account.

The core journey was built around the match. Users first choose the event they want to watch, then select a place and make a reservation. This makes the schedule and booking feel like one continuous journey rather than two separate sections of the app.

The app collects weather, wind, pressure, and other conditions for a selected location, then uses AI to forecast fish activity. Users can also save locations, keep a catch history, and track the condition of their gear.

I did not want the home screen to present a set of weather readings without context. Instead, the data primarily answers a simpler question: how suitable are the current conditions for fishing at the selected location? Detailed readings remain available to users who need them.

Users enter the team’s starting parameters and receive options for the name, chant, color palette, and logo. The results can be compared and put to a vote among friends or supporters.

AI was meant to help users get started without taking the final choice away from them. The journey therefore does not end with one generated result: users receive several directions, compare them, and choose the final identity together.

Users choose a sport, find a venue, add players, and split them into teams, and check the weather or equipment list when needed. During the game, a timer and score counter are available; afterward, users can review their match history.

A potentially short journey could easily have turned into a long onboarding flow with too many settings. I kept optional parameters out of the main path: only basic information is required to start a match, while the venue, equipment, and additional settings can be added later.

Users choose a sport, level, and goal, then receive suitable exercises and ready-made training programs. Interval sessions include a built-in timer, while a separate section covers focus, motivation, and stress management.

The training itself remained the primary journey: choose a program, start a session, and move through the exercises in sequence. I kept supporting content outside this flow and placed it on a separate navigation level so it could expand the product without complicating the core experience.

Working in short cycles taught me to identify quickly which problems could be solved with established patterns and which required dedicated exploration. I invested more time in the product’s core mechanics, structure, and non-standard scenarios.

Over two years, I progressed from working within established rules to independently running several products in parallel, reviewing other designers’ work, and supporting each product from brief to development handoff.