I worked on the mobile app within the MotionH ecosystem, designed to support two user groups: patients following a physiotherapist’s plan and independent users managing their own training. I joined the project after its core concept and key functional ideas had been established. My work focused on refining the existing wireframes, improving usability and consistency, and expanding the app’s functionality. I contributed to the evolution of an existing product, working across product logic, user experience, interface design and strategy.
This case study showcases selected aspects of my over two-year involvement in MotionH, spanning product design, UX, research, testing, documentation and the broader development of the product.
MotionH is a platform for exercise and rehabilitation, built around collaboration between physiotherapists and the people they guide, while also supporting independent training. Its clinician portal enables physiotherapists to prepare and manage treatment, while the mobile app allows users to follow plans, perform exercises and track their activity, either as part of a treatment programme or on their own.
The product was conceived as a single app rather than separate medical and fitness products. This meant the two paths needed to share a common foundation while accommodating different levels of guidance and control.
The product was conceived as a single app rather than separate medical and fitness products. This meant the two paths needed to share a common foundation while accommodating different levels of guidance and control.
The app had to accommodate two different training contexts without making either feel out of place. This influenced both the visual design and the way users interacted with the product. It needed to feel approachable to independent users while providing a clear and structured experience for patients following a physiotherapist's plan.
The mobile app and clinician software were developed in parallel as parts of the same ecosystem. Research and user insights were shared across both products, and design decisions in one could affect functionality in the other. This meant that UI/UX iterations and usability testing had to run alongside each other, with findings from one product informing decisions in the other.
The process combined usability testing, interviews with physiotherapists and manual testing of functional and technical aspects. Physiotherapist interviews provided insights into everyday clinical practice and helped map user journeys. I conducted four rounds of structured interviews with physiotherapists and three rounds with Wellbeing users, with five to seven participants in each group. The findings informed ongoing improvements to the mobile experience.
The two paths differ in how users plan and manage their training. This distinction shaped the level of autonomy offered by the app and determined which parts of the experience needed to be tailored to each group.
Wellbeing users manage their training independently. They can browse exercises, create their own programs and adjust their routines according to their needs.
Patients follow a plan prepared by their physiotherapist. Their experience is more structured, with scheduled exercises, instructions and progress reporting.
Both paths use the same core components for completing sessions, setting goals and tracking progress, adapted to different levels of user autonomy.
FIn the Patient path, training is structured around a routine defined by the physiotherapist. The app puts the prescribed sessions at the centre of the experience, giving patients a clear starting point and guiding them through each workout with the instructions and tools needed to complete it.
Patients use the plan to track their rehabilitation progress, review completed sessions and see what remains in each phase before continuing with their prescribed exercises.
Patients follow the prescribed exercises, adjust repetitions and weights, and record their effort and pain levels. They then mark each completed set.
Unlike the Wellbeing path, the Patient path does not ask users to choose or assemble a routine. I gave the session prescribed by the physiotherapist priority on entry, so patients can move directly into the task they are expected to complete.
Patients can review their training history, completed sessions and progress charts to understand how their activity develops over time. Additional metrics provide a broader picture of their training, including muscle-load overviews and Companion, which offers a more detailed view of muscle fatigue
The clinician portal brings together data from the patient's rehabilitation activity, giving physiotherapists a broader view of how treatment is progressing between appointments. They can review changes over time, monitor pain levels and assess how consistently the patient follows the prescribed programme. This helps them identify changes in the patient's progress, recognise gaps in exercise participation and use that information when reviewing or adjusting the treatment plan.
Progress: review performance trends and changes over time. Symptoms: monitor reported pain levels. Adherence: track completed sessions, exercise frequency and regularity. Activity overview: review the patient's overall rehabilitation history.
Competitive research informed the decision to extend the HEP model beyond therapist-prescribed rehabilitation. The Wellbeing path allowed users to independently create training programs, set goals and track their activity.
Wellbeing is the self-directed path: users decide what they train and when. Programs are assembled from an exercise library rather than prescribed by the system, leaving users in control of their training routines. One of the product's objectives was to establish a recurring user flow that would support ongoing progress and encourage continued engagement without relying on conventional gamification. To address this, we developed the Goals and Companion systems, providing structure for progression and tools to review training activity.
The experience connects independent training, goal setting and progress tracking in a recurring cycle. Each element plays a different role in organising activity, monitoring progress and informing future training decisions.
Exercise execution: The app supports users throughout their workout, from following a planned sequence of exercises to completing individual sets. It helps them work towards prescribed repetitions and weights, monitor their effort and pain levels, and manage rest between sets. This supports the consistent execution of exercise programmes and provides a record of each training session.
Tracking progress: Progress tracking connects completed sessions with the goals users have set. The interface brings together the history of activity and indicators of consistency, so progress is not reduced to a single performance number. I also introduced streak increments and an exercise-regularity meter. These additions followed a discussion with a physiotherapist during Test 1, who highlighted how gradual musculoskeletal progress can be difficult to notice and how visible markers can help patients stay consistent and engaged.
I added streak increments and an exercise-regularity meter alongside goal progress. The rationale came from a physiotherapist interview during Test 1: musculoskeletal progress can be gradual and difficult to notice, while visible markers of regular activity can help patients stay engaged. This was a research finding from the interview, not a direct usability-test observation of these specific components.
Goals are available to both patients and independent users, but were primarily designed to support progress in self-directed training. They allow users to define training targets, monitor their achievement and connect individual workouts with longer-term objectives.
User testing revealed that the original Goals concept, focused solely on measuring performance progress, was too narrow, particularly for rehabilitation. Achieving a specific performance target is not always the primary objective. Maintaining a regular exercise routine can be just as important.
The original Goals system was too narrowly focused on performance progress, overlooking other important aspects of training, particularly consistency and regularity.
We examined a wider range of training scenarios to understand what users wanted to achieve and how different types of goals should be measured. This highlighted the need for more flexible goal structures and different ways of recognising completion and tracking progress.
This led us to rethink the system and expand it to three goal types: Session, Progressive and General. We also introduced features such as activity streaks and an exercise-regularity meter to make consistency visible alongside performance progress.
The three goal types address different training intentions:
The expanded model was not about adding features for their own sake, but about addressing a broader range of user needs identified through testing and use case analysis.
I developed a new metrics system to provide users with a clearer picture of their training activity and goal achievement. Instead of treating progress as a single outcome, the system tracks several aspects of goal completion: whether a session was completed, whether the goal was achieved, and how many times it was achieved within a single session. This allows users to see not only whether they reached a target, but also how consistently they achieved it across their training activity.
The original goal progression used fixed percentage increments. The next step in the plan was not sufficiently clear to users, because the numbers did not explain how progress was expected to happen. I redesigned the system around explicit targets and intermediate milestones. The changes also covered how users create a goal, review its proposed plan, track actual progress, and pause or resume it.
Progressive goals: the user sets the destination. The previous approach relied on fixed percentage increments, which did not make the next step meaningful or easy to understand. In the redesigned flow, the user sets the long-term target. A starting value is optional: if the user does not know it, the plan can begin after the first workout is logged. The app then generates intermediate milestones between the starting point and the target.
The previous progression relied on fixed percentage increments, which did not explain why the next value had been chosen. I changed the model so users define the end target and the app generates intermediate milestones. The starting value is optional, so not knowing it does not prevent goal creation.
Generated milestones are shown in a bottom sheet rather than taking up space in the form. Users can inspect the proposed steps before saving, while the main creation flow remains uncluttered.
I developed use cases to identify the limitations of the original Goals model and define the requirements for its redesign. I then used them to test and validate whether the proposed goal types and tracking mechanics could accommodate different training scenarios.
The original goal creation flow uses a form where users select a goal type and define its parameters. Depending on the selected type, they can configure different targets, such as workout frequency, session completion or progressive performance milestones. This provides a direct way to create goals for users who are already familiar with the system.
Goal creation takes between two and three steps, depending on the selected goal type. The original form presented all configuration options on a single screen, which proved too demanding for users. We therefore split the process into smaller steps, making goal creation easier to follow and reducing the amount of information users need to process at once.
During usability testing, some users had difficulty understanding the differences between goal types and what each option was designed to achieve. The form-based approach assumed a level of familiarity with the Goals system that new users did not always have.
To reduce the initial learning effort, we introduced Guided Add as an alternative way to create goals. Instead of presenting all parameters in a single form, the process breaks goal creation into smaller steps, with each screen explaining the choice the user needs to make. The flow adapts to the selected goal type and its parameters, so users only see the steps relevant to their chosen goal.
Goals and progress tracking form a central part of the independent training experience. We wanted to minimise friction at the point where users first engage with these features, rather than risk discouraging them with complex forms before they could experience their value.
MotionH can accommodate different approaches to exercise, but its core value lies in supporting overall and balanced physical development. This principle goes beyond individual workouts and training goals, taking into account how different muscle groups are engaged throughout a training routine. Our task was to translate this approach into the app by identifying and designing features that would help users maintain a more balanced training routine.
Research highlights the relationship between opposing muscle groups as an important aspect of muscular function. Studies examining agonist-antagonist strength ratios show their relevance in assessing muscle balance, physical performance and rehabilitation. This supported the rationale for including opposing muscle groups in MotionH's approach to balanced training.
Source: American College of Sports Medicine (2026). Resistance Training Prescription for Muscle Function, Hypertrophy, and Physical Performance in Healthy Adults
Source: Cozette et al. (2019). Isokinetic Strength Ratios: Conventional Methods, Current Limits and Perspectives
To support balanced physical development in practice, we needed a way to help users understand how their training engages different muscle groups and identify areas receiving less attention. Tracking completed workouts and progress towards individual goals alone did not provide this broader perspective.
I designed Companion feature to visualise training distribution across muscle groups, identify neglected areas and suggest complementary exercises based on workout history.
The feature analyses which muscle groups have been engaged in recent workouts and which have received less attention. Based on this information and the relationship between opposing muscle groups, it generates a complementary exercise programme. Users can incorporate these suggestions into their training without replacing their existing plans. Users can refine the recommendations by selecting a body-part focus, exercise type and training history period
Companion complements Goals by adding a broader perspective on training: while Goals focus on individual targets, Companion helps users maintain balance across muscle groups. It supports both independent training and physiotherapist-guided programmes, without replacing the prescribed plan. Its role as a core feature was also reflected in its prominent placement in the main bottom navigation.
The mobile app reached MVP with two coherent paths on shared mechanics: Patient (prescribed plans synced with the clinician portal) and Wellbeing (self-directed programs, Goals, and Companion). Core systems I designed — goal creation and progression, session flow, progress tracking, and muscle-load insights — now form the product’s foundation.
A shared visual system does not mean identical interaction models. Patients need a clear path through a prescribed plan. Wellbeing users need control over their routine. Hierarchy and context matter more than pure consistency.Maintaining a design decision log proved essential for preserving reasoning, improving handoff, and turning research into traceable decisions. Testing the built app also revealed edge cases (timers, recalibration, state changes) that static designs could not fully surface.
What's next: The next phase focuses on extending the Wellbeing experience and supporting users over a longer period. Areas for further exploration include social features, such as sharing progress or training with friends, and more automated, AI-assisted program generation to make it easier to get started. On the clinician software side, a future area of work is deeper analytics for clinics.