Healthcare XR

Building a VR Rehabilitation App: Inside Reahap

Illustration of a VR exercise session with a therapist and a progress display

A VR rehabilitation app needs two connected experiences: the exercise a person sees in the headset and the tools a clinician uses to configure and review it. A compelling game mechanic only addresses part of that brief.

Virtual Verse Studio built Reahap, a Meta Quest application that turns physiotherapy movements into game interactions. The platform combines personalized difficulty, visual and audio feedback, progression systems, and a clinician dashboard. This article explains those software design decisions. It does not report a clinical trial or establish that Reahap improves recovery, adherence or pain outcomes.

The Reahap brief

The project aimed to make prescribed exercises easier to follow and session progress easier to review. The patient-facing experience needed to present a clear task, respond to movement and show progress. Clinicians needed visibility into sessions and a way to adjust programs.

The delivered platform uses Unity, C# and the Meta Quest SDK. Its core features are:

  • Gamified exercises mapped to physiotherapy movements.
  • Difficulty and range-of-motion targets that can adapt within clinician-defined parameters.
  • Immediate visual and audio feedback during an exercise.
  • Progression and rewards within the experience.
  • A clinician dashboard for reviewing session data and adjusting programs remotely.

These are descriptions of the product. Whether they produce a particular clinical benefit requires a separate evaluation of the intended program and patient population.

Start with the movement, then design the interaction

For this kind of application, the starting point is the intended movement and the constraints supplied by the clinical team. The development task is to represent that movement as an understandable interaction in a virtual scene.

In Reahap, reaching, stretching and rotating become parts of in-game actions. That gives the player a visible task and gives the software something concrete to respond to. It also creates a design constraint: a reward should correspond to the action the program intends to capture, rather than simply to the highest score or fastest completion.

For a new build, we would document the relationship between each exercise, its interaction and the data recorded. That specification helps the development and clinical teams review the same behavior. It also makes a change to a game rule easier to trace back to the exercise it represents.

Feedback needs to explain the software's response

Reahap uses visual and audio feedback during movement. The engineering question is whether a user can understand what the application detected and what happened next.

A target changing state, an audible response and a progress indicator can make an interaction legible. Their timing needs to match the detected action; otherwise, a player can be unsure which movement produced the response. The display also needs to distinguish an incomplete task from lost tracking or an interrupted session.

Those are interaction-design requirements. Feedback in an app should not be described as a validated assessment of movement quality without evidence for that specific measurement. A controller position, a game score and a clinician's assessment are different kinds of information.

Adaptive difficulty needs explicit boundaries

Reahap supports personalized difficulty scaling based on progress and clinician-defined parameters. The aim is to make the exercise experience configurable for the person using it.

For the implementation, “adaptive” needs a precise definition. Which inputs can change the difficulty? Which settings remain under clinician control? What happens after a tracking interruption or an incomplete session? These questions belong in the specification and acceptance criteria before the team promises an adaptive system.

The public project description does not establish a reinforcement-learning system or an autonomous exercise prescription engine. Those would be separate capabilities requiring their own implementation and evaluation. They should not be inferred from the presence of difficulty scaling.

Tracking claims must match what the device measures

Reahap runs on Meta Quest. A development brief should name the supported headset, input method and movements that the application needs to detect. “Motion tracking” alone is too broad to serve as an acceptance criterion.

For any measurement presented to a clinician, the team needs to explain its source and limitations. A value derived from a tracked controller is not automatically a validated measurement of the whole body. Accuracy figures from a different sensor, laboratory setup or software product cannot establish Reahap's accuracy.

Useful engineering checks include consistent input handling, clear tracking-loss states, session interruption and recovery, and the correspondence between recorded events and what appeared in the headset. If the product will make a clinical measurement claim, that claim needs a defined validation process beyond a normal application QA pass.

The clinician dashboard is part of the product

The headset is only one side of Reahap. Its dashboard gives clinicians a view of patient session data and progress, and supports program adjustments.

That changes what the team needs to design. Session identity, exercise settings and progress must remain understandable across the headset and dashboard. A clinician reviewing a session needs enough context to interpret what the software recorded. An interrupted attempt should not silently look like a completed exercise.

For a future integration, exports, documentation formats and access permissions would be requirements to confirm with the buyer. The existence of a dashboard alone does not establish compatibility with a particular electronic health record, payer workflow or clinical reporting standard.

Our MedSim virtual patient platform has a related product-design concern in education: faculty need to author and assign cases and review student work. MedSim's educational workflow and Reahap's rehabilitation workflow are different, but both require usable tools around the immersive experience.

What a delivery review should verify

A useful review of a VR rehabilitation software build covers the complete workflow:

  • Can the intended user understand the task and the available controls?
  • Does each interaction respond consistently on the agreed hardware?
  • Are configuration and difficulty changes bounded by the approved specification?
  • Are tracking loss, pausing and incomplete sessions represented clearly?
  • Can the clinician locate and interpret the corresponding session data?
  • Are device requirements, known limitations and the scope of testing documented?
  • Are claims about accuracy or outcomes supported by evidence for this product and intended use?

These questions help separate software delivery from claims that need clinical validation. Engagement is a design goal; a product description should not convert that goal into a measured improvement without data.

Explore the project

The Reahap case study shows the delivered platform, stack and project film. If you are commissioning a similar application, our VR development services cover scoping, interaction design, Unity implementation and testing against agreed hardware and requirements.

Discuss your project with Virtual Verse Studio. Bring the intended users, exercise workflow, supported devices and clinician requirements; we can use those to define a reviewable software scope.

  • VR Rehabilitation
  • Gamification
  • Healthcare XR
  • Immersive Therapy
  • VR App Development
Mohamed Essam
Mohamed Essam
Co-Founder & CTO

Co-founder and CTO of Virtual Verse Studio. Leads technical direction and client delivery, with deep hands-on expertise in Unity, Unreal Engine, AR/VR, multiplayer systems, and XR architecture — shipping immersive products since 2018.

Keep reading

Related articles.

Build with us

Interested in building something like this?

From VR training to WebGL experiences and beyond — tell us about your project and we'll scope it honestly: timeline, budget range, and the right platform.