How Do I Design Apps for Elderly People?

Designing for older adults is one of the most clarifying disciplines in digital product work. It strips away assumptions. The gestures, type sizes, interaction patterns, and onboarding flows that feel natural to a designer in their thirties were built on decades of accumulated digital habit that many older adults simply do not share. When you design for someone who has never owned a smartphone, or who came to touchscreens in their sixties, you discover very quickly which parts of your design are doing real work and which parts were always relying on familiarity to paper over poor choices.

The demographic reality is plain enough. People over 65 are one of the fastest-growing groups of smartphone users, and they are not a niche audience. They book travel. They manage health appointments. They pay bills, video-call grandchildren, and do their shopping online. They are using apps whether those apps were designed for them or not, and when the experience fails them, they do not always assume the app is at fault. They assume they are.

Gesture complexity is a hidden barrier

Swipe interactions, long-press menus, and pinch-to-zoom all require a degree of coordination that becomes more variable with age. Where a standard UI relies on a swipe to reveal an action, an older adult may not know the gesture exists, may not execute it cleanly enough to trigger it, or may trigger it accidentally and not understand what happened. The safer approach is to make primary actions available through a direct tap on a clearly labelled button, and to treat gestures as shortcuts for users who have already discovered them, not as the only route to an action.

Design every primary action so it can be completed with a single tap on a target at least 48x48px. If an action currently lives behind a swipe or long press, add a visible alternative that requires no gesture knowledge.

Cognitive Load and Information Architecture

Cognitive load is the amount of mental effort a user has to spend to understand and navigate an interface. Every decision they have to make, every new piece of terminology they encounter, and every step they have to hold in working memory while completing a task adds to that load. When the load exceeds what the person can comfortably hold, they make errors, they give up, or they lose confidence in the product.

Working memory capacity does change with age, and the effect is meaningful for app UX design. Screens that present too many choices at once, flows that ask users to remember information from a previous step, and navigation structures that require a mental model of how the whole app is arranged all create friction that falls harder on older users than on younger ones. The principle of progressive disclosure, showing only what the user needs at the point they need it, is the baseline.

Terminology carries more weight than designers expect

Words like "dashboard", "feed", "profile", and "sync" carry meaning only if you already know the conventions of digital products. On one project, we reframed terminology within a product so that the language matched the user's existing mental model rather than the platform's internal logic. The interaction pattern stayed the same. The words changed. The drop-off through that section of the flow fell noticeably. For older adult users with less exposure to app conventions, the labels on things matter as much as the layout of them, and plain language is the design doing its job.

Read every screen aloud using only the words as written. If you have to explain what a label means while reading it, the label has failed. Replace it with the explanation.

Onboarding at the Right Pace

Onboarding is where many older adult users decide whether a product is for them. A long list of permissions, a multi-screen carousel of features, and an immediate demand to create an account can combine to make the first thirty seconds feel overwhelming before the user has seen any value from the product at all. Research from Think with Google found that 21% of users will give up on an app if they cannot get it right away, and for older adult users who may already be approaching the product with some anxiety about digital tools, the threshold for giving up is often lower.

The better approach is to delay demands and lead with value. Let the user do something useful before asking them to register. Introduce features one at a time, at the moment they become relevant, rather than explaining the whole product upfront. When you do ask for permissions, explain in plain English what you are asking for and why the app needs it. An older user who does not understand why an app is asking to access their contacts or their location is very likely to refuse, and very likely to leave.

Pace the learning curve deliberately

A well-paced onboarding flow introduces one new concept at a time and confirms the user has understood it before moving on. This does not have to mean long tutorials or mandatory walkthroughs, which can feel patronising. It means building the complexity of the interface progressively, so early tasks are simple and success builds confidence that carries the user further into the product. Celebration of small wins matters here, small, genuine signals that the user has done the right thing, because they reinforce the feeling of competence that older adults may not naturally feel in a new digital environment.

Error Recovery and Forgiveness

Errors are inevitable. The question is what the product does when they happen. For older adult users, an unhelpful error message does more than frustrate. It can feel like confirmation of a fear they already had: that technology is too complicated for them, that they have done something wrong, that they have broken something. That emotional response is a real design problem, and it is largely preventable.

Good error handling tells the user specifically what went wrong, in plain language, and tells them exactly what to do next. Not "Invalid input". Not "An error occurred". Something closer to "Your date of birth should be in the format day, month, year, for example, 15 June 1948." The Baymard Institute found that 98% of sites do not use specific, adaptive error messages of that kind, which means the bar for doing this well is genuinely low and the opportunity to build trust through it is real.

Undo and confirmation protect confidence

Irreversible actions are particularly alarming to older users who worry about making mistakes they cannot fix. Where an action will delete something, submit a payment, or make a change that cannot be undone, a confirmation step is reassurance. Equally, where actions can be undone, making that obvious, with a clearly labelled button rather than a gesture the user has to discover, removes much of the anxiety that comes with trying something new. The product should feel forgiving. A user who knows they can recover from a mistake is more willing to explore.

Accessibility as a Core Design Priority, Not a Bolt-On

Accessibility is often treated as a compliance exercise, something that happens at the end of a project when someone checks the product against a list of WCAG criteria and fixes the failures. That approach produces products that technically pass a check and practically remain difficult to use. Real accessibility is a design decision made at the beginning, and it changes the product from the inside rather than patching the outside.

We learned this directly on the film industry document portal, where we made accessibility an active design priority from the start, not because the users were older, but because the user base was genuinely diverse and the environment was demanding. The design was large-scale, easy to navigate, and built entirely around getting to information as quickly and simply as possible. That brief sounds similar to any well-run UX project, and that is exactly the point. Accessible design and good design are the same thing when you do them together.

System settings are your ally

Both iOS and Android give users tools to make their devices more usable: larger text sizes, higher contrast, reduced motion, and display accommodations for colour blindness. A well-built app respects all of these. It does not fix its own font sizes in ways that override the system setting. It does not use animations that ignore the reduce-motion preference. It does not break its layout when text size is increased. These are the actual settings that older adults use to make their phones work for them, and building against them is building against your user.

Test your app with the largest system text size enabled and with high contrast mode on. If any screen breaks, clips text, or loses meaning, that screen needs to be rebuilt before the product ships.

Testing With Older Adults, Not Just For Them

A product designed for older adults that was tested only with younger users has a fundamental gap in its evidence base. Designers and researchers who are not in the target age group carry their own familiarity with digital conventions, and that familiarity makes it nearly impossible to experience the product the way an older adult will. You will not notice that the icon is ambiguous, because you already know what it means. You will not notice that the flow is confusing, because you navigated it using knowledge you brought with you.

Research from Nielsen Norman Group suggests that testing with five users uncovers around 85% of usability problems, and that finding holds when those five users are genuinely representative of the people who will use the product. For an app aimed at older adults, that means recruiting older adult participants, not as an afterthought but as the primary test group. This applies to formative research too, the kind that shapes what you build, not just the kind that checks whether what you built works.

Bring in non-target users for contrast

One technique we have used effectively is recruiting users who sit outside the primary target group to surface qualities the target group cannot easily articulate. On a concierge app for a premium property development, we ran focus groups with high-net-worth residents, who were the target audience, and with people from social housing, who would never be customers. The social housing group had the sense of community and neighbourliness we were trying to build into the product. That quality was harder to find in the target audience, and impossible to design for without having observed it directly.

The same logic applies in older adult research: speak to users across the spectrum of digital confidence, not only the ones who are already comfortable with apps.

Conclusion

Designing for older adults is not a specialist sub-discipline that sits apart from mainstream product design. The principles it draws on, clarity, forgiveness, progressive disclosure, accessible contrast, and meaningful onboarding, are the same principles that make any product better for any user. The difference is that older adults remove the tolerance for getting these things roughly right. The margins close. The assumptions that younger users quietly compensate for become genuine barriers.

What we find, working on products across a wide range of sectors, is that the teams who take this work seriously early, who recruit older adults into research from the start, who treat accessibility as a design constraint rather than a compliance check, build products that are more confident in themselves. They know what they are for and who they are for. That clarity shows in every screen.

Resizable text is widely considered the most common accessibility feature developers implement, and it is also the most basic. If that is where the conversation stops, the product has barely started. The real work is in the flow, the language, the error states, the onboarding, and the testing, and it pays off in a user group that is large, growing, and consistently underserved by the products built without them in mind.

If you are designing a product for older adults, or if you have a product that is not working for them as well as it should, let's talk about your design approach.

Frequently Asked Questions