The Wrong Patients Are Using Health Apps
The global digital health market is projected to reach $550 billion by 2028. Most of that investment targets people who are already healthy — fitness trackers, meditation apps, meal planners. The patients who need digital health the most — elderly, post-surgical, managing chronic conditions — are the ones least served by the current design paradigm.
Consider the typical total knee arthroplasty patient: 68 years old, moderate digital literacy, in significant post-operative pain, possibly living alone, using a phone their child set up for them. This patient needs to report pain daily, photograph their wound, and complete a set of exercises — for 4 to 12 weeks.
Now consider the typical health app: small fonts, nested menus, account creation with email verification, complex dashboards, and notifications that require contextual understanding to act on.
The mismatch is structural, not incidental. We are asking the patients with the lowest digital fluency to use software designed for the highest.
The 30-Second Rule
When we built iRehab's patient-facing PWA, we started with a single design constraint: every daily task must be completable in 30 seconds or less.
Not 30 seconds to navigate to the right screen. Thirty seconds total — from opening the app to submitting data. This constraint shaped every decision:
Pain Report: 10 Seconds
The patient opens the app. The dashboard shows today's tasks. They tap "Report Pain." A single screen appears with a 0-10 numeric scale. They tap a number. Done.
No body diagrams. No multi-page questionnaires. No "rate your pain on the following dimensions." A single number, once a day, is clinically sufficient for trend detection — and it is the maximum complexity a patient in acute pain will tolerate.
Wound Photo: 15 Seconds
Tap the camera icon. Take a photo. The app compresses it client-side (max 1920px, quality 75%) and uploads to secure storage. No cropping, no filters, no "add a description."
The photo lands in a calendar view — one cell per day, each showing a thumbnail. Over weeks, the grid tells a healing story that no single clinic visit can capture.
Exercise Session: 20 Minutes (But Initiated in 5 Seconds)
The daily exercise session is the longest task, but initiation is instant. The app shows today's session (morning or evening, auto-selected by time of day) with 4-5 exercises. Tap to start. Each exercise shows sets, reps, and expandable instructions. Complete or skip (with reason). Progress bar advances. Session done.
We write more about the clinical protocol design and why adaptive sessions matter. Here, the point is simpler: the patient never has to decide what to do. The system decides. The patient just shows up.
Design Decisions That Look Obvious (But Aren't)
No Passwords
Our patients cannot reliably remember passwords. Some cannot reliably type them on a phone keyboard. We use magic links — the surgeon generates a QR code or sends a link via LINE. The patient taps it once, and they are authenticated for 90 days.
For return visits, the fallback is national ID + birthday. Two pieces of information every patient knows, entered on a simple numeric keypad.
No Onboarding Wizard (Almost)
We reduced onboarding to three slides: (1) your doctor is watching your progress, (2) you will report pain and take wound photos daily, (3) you will receive exercise prescriptions. Swipe, swipe, done.
The instinct in product design is to explain everything upfront. For elderly patients, this creates anxiety. They do not need to understand the system — they need to trust that their doctor is behind it.
Large Touch Targets, Everywhere
Every interactive element is at least 44x44 pixels — Apple's minimum recommended touch target. Most of our buttons are larger. This is not just accessibility compliance. Watch a 75-year-old with arthritic fingers try to tap a 32px button on a phone, and you will never design small buttons again.
No Tabs, No Hamburger Menus
The app has three screens: Dashboard, Exercise, and Progress. Navigation is a bottom tab bar with large icons and text labels. There is no hamburger menu, no settings page (settings are handled by the care team), no profile to manage.
Every screen that does not directly serve a daily task is a screen that can confuse.
The Photo Calendar: Compliance Through Visibility
One of our most effective engagement features was not planned as a gamification mechanic. It is a calendar.
The wound photo calendar shows the current month as a grid. Days with photos show a thumbnail. Days without photos show an empty cell. The visual pattern — filled, filled, filled, empty, filled — creates a natural motivation to avoid gaps.
We added a streak counter: "7 days in a row." No badges, no points, no leaderboard. Just a number that goes up when you are consistent and resets when you are not.
The clinical value is equally important. A surgeon can open any patient's photo calendar and see four weeks of wound healing in one glance. No scrolling through a list. No asking the patient "how does it look?" The photos speak.
Milestone Celebrations: Acknowledging Effort
At key recovery milestones — triggered by achievements like completing the first exercise, maintaining a consistency streak, or reaching a new rehabilitation phase — the patient receives a full-screen celebration message. For example, at two weeks post-surgery:
"Day 14 — Two weeks of recovery. Your consistency is building the foundation for long-term mobility. Your doctor is tracking your progress."
These messages are deliberately simple. They acknowledge the patient's effort (not their "performance"). They remind them that their doctor is watching. And they create temporal landmarks in what otherwise feels like an endless, painful recovery.
The doctor can copy the milestone message and paste it into a LINE chat with one tap — adding a personal touch without composing a new message.
What We Learned
Completeness beats accuracy
A patient who reports pain as "4" every day (even if the true value varies between 3 and 5) is more valuable than a patient who agonizes over the exact number and stops reporting after a week. We optimized for daily completion rate, not measurement precision. The trend matters more than any single data point.
Morning sessions have 40% higher completion
Patients who exercise in the morning are significantly more likely to complete their session than those who exercise in the evening. This is why we default to showing the morning session first, and why we split protocols into two manageable sessions rather than one long one.
The caregiver is the hidden user
Many of our patients do not use the app alone. A spouse, child, or caregiver helps them navigate. We designed for this: large text, high contrast, no private data on the main screen, and a flow that can be guided verbally ("tap the blue button, then the camera icon").
Offline matters
A patient recovering at home may have unreliable internet. The app shell is cached by a service worker and loads instantly on repeat visits. When data cannot sync, a stale-data indicator appears — but the patient can still view their exercises and report pain. The data syncs when connectivity returns.
The Simplicity Tax
Every feature we did not build was a deliberate choice. We do not have:
- Social features (patients do not want to share their wound photos)
- AI-generated encouragement (elderly patients are not motivated by chatbots)
- Detailed analytics dashboards for patients (they want to know: am I on track? Yes or no)
- Video exercise demonstrations (bandwidth-heavy, and a static image with text instructions tested better in our cohort)
Each of these features is reasonable in isolation. Together, they would create the kind of complex, feature-rich app that 30-year-old designers love and 75-year-old patients abandon.
Simplicity is not a limitation. For this population, it is the feature.
iRehab is designed for post-surgical patients aged 60-80 and is live in clinical settings. For information about clinical partnership, contact us. For the clinical protocol behind the exercises, read 34 Exercises, 5 Phases.