A short motion demo
Micro-interactions and transitions in context
It's an older case study, kept here for anyone curious.
No password? Ask me for access, or go back to the homepage.
Mobile appiOS and Android2019 to 2021
A mobile app for training at home, built to get people in the Gulf (GCC) countries who never go to a gym training regularly.
App Store and Google Play links are available on request.

The first release focused on live classes, programs and workout sessions. It launched in the Gulf, starting with Kuwait, as a subscription measured on engagement and retention.
Hot is a Kuwaiti company started by a tech company with a background in gyms and fitness training. In 2019 I started on the app as the only designer, with one backend developer, two Android and two iOS developers, and the CEO.
We ran design sprints against fixed deadlines, shipped features and improved them live, and designed around technical limits as they came up.
Top 1 to 3 grossing in Kuwait on the App Store and Google Play, and Featured App of the Day on iOS, with one designer, five developers and the CEO.
Research, personas and the customer journey.

I was lucky to have a gym owner who could help me identify the target audience. From their data, benchmarks and the rival businesses I studied, I wrote fictional personas based on Engaging Personas and Narrative Scenarios by Lene Nielsen.
The persona cards turned my thoughts into one scenario while we wrote user stories and ran customer journey sessions with the team.
I used three personas, from a housewife to a fitness enthusiast, and shaped the flow by cross-referencing their needs and emotions in an affinity map.


We needed a clear picture of how customers would find us and use the product, for the launch and for scaling later. I made a simple 5×5 table, explained it to the head of each department, and they filled it in from their own knowledge of the business.
I gathered their input, compared what each of them pictured, and merged it into one customer journey table: a shared vision for the roadmap.
We agreed to start with live classes, programs and workout sessions, and to leave leaderboards and achievements for the next major release.
I ran test sessions in Iran and remotely in Kuwait. Our focus groups used their own fitness app, mostly Peloton, and told me what they loved, what they hated and what they wished it had.
I used the human-centered observation method from Don Norman's The Design of Everyday Things, noting their visceral, behavioral and reflective reactions.
With that, we knew how we wanted to run the business, and it was time to start design thinking and ideate against our feature and vision lists.

Low-fi to mid-fi, tested at every step.

After rounds of brainstorming, storyboards and sketches in notebooks, I wireframed the flows. A very low-fidelity wireframe in Adobe XD went to Kuwait first, then a mid-fidelity Balsamiq mockup once we agreed on the pages.
Testing those wireframes with fitness groups and our personas changed the flow a lot. At first I put the activities (Live, Programs, Workouts) in a bottom nav bar, but a tab bar stacked on a nav bar never felt right. Moving them to the top of the page made switching between activities feel natural to the test group.
Small things, like how content scrolls, can seem unimportant at first. A/B testing early mid-fi prototypes with horizontal and vertical scrolling, and different content and button placements, showed me where people actually touch the app while they work out. Class types and categories needed tree testing and card sorting to reach categories most people agreed on.
Master components, remote theming and hi-fi screens.

One thing that helped a lot was keeping a design system artboard with every asset as a master component. It made revisions and experiments far easier. Component states and responsive resize in Adobe XD were enough to make me switch from InVision Studio right away.
As a team we came up with NCS, a cloud system that held the color palette, videos, images, icons, fonts and sizes. You could change any of them from a dashboard and every installed app picked it up without an update, so a badly performing icon or image could be swapped at once. Credit to Payam Chamani and Hamidreza Vakilian for building it.

The most important feature was probably the video player. Most content ended in videos played in rotation, so it had to let people skip a session, show what was going on, and never pull attention from the workout. I built one variation on top of another until I reached one I really liked.
Then technical implementation caught up with us. A feature called Achievements tracked what you did in the app and gave digital or physical rewards at milestones: videos watched, distance, fat burned and more. It needed a check so nobody could start a workout, leave the phone running for 24 hours and cash in prizes. We found a solution fairly quickly.
Last, I finished the micro-interactions to give the app a lively, playful feel. A couple of months after launch, Apple featured it as App of the Day.
Micro-interactions and transitions in context
What happened after we shipped.

We started with very little information, then ran many workshops, user tests and a good amount of analytical guesswork. When we released the app, the response overwhelmed us. Within a couple of weeks it reached the top of the charts and stayed at #1 or #2 top grossing on iOS and Android.
Until my last days with the team we kept analyzing heatmaps, analytics and NPS scores to fine-tune the app.
I'm glad I got to work with this team.
Hiring a design leader? Let's talk.