UX for Older Users: Practical Design Rules That Work

Most apps built in Kuwait are tested on staff in their twenties and thirties. The people who pay the electricity bill, book the hospital appointment and follow up on a government transaction are often twenty or thirty years older. Designing for them is not a separate project with its own budget. It is a set of defaults you either set correctly at the start or repair later at a higher cost.

Fix size and spacing before style

Older users read more slowly and lose their place in dense text. Treat 16px as the floor for body text on mobile, and go to 18px for anything that must be read carefully: payment amounts, appointment details, contract terms. Line height around 1.6 stops lines from crowding each other.

Arabic needs its own check. At the same pixel size, Arabic script looks smaller than Latin and its dots run together when lines are tight. Review the Arabic screen at the size you actually shipped, on a real phone, not zoomed in on a laptop.

One decision per screen

If a screen asks for a password, a verification code and a preferred branch at once, most people will get one of the three wrong and start over. Split the flow, show how many steps remain, and never wipe the fields when someone taps back.

Labels should name the result. "Pay now" beats "Continue". "Save and send" beats "Submit". Skip icons without words: a house symbol with nothing beside it is a guess, and guessing is the point where people close the app.

Build forms that forgive mistakes

• Keep labels above the field and visible after typing starts; placeholder-only labels vanish exactly when they are needed.
• Show the phone number or civil ID the system will use, with an edit option, before anything is sent.
• Do not expire a verification code in thirty seconds. Allow a few minutes and make resend obvious.
• Use dropdowns only for short lists. A picker with sixty items is harder than a plain text field.
• Confirm success on a clear screen with a reference number people can screenshot or write down.
• Avoid hover, long-press and swipe-to-reveal for anything important. Put the action on the screen as a button.

Pre-launch checklist

• Body text at least 16px, headings clearly larger.
• Contrast checked in daylight, not only on a desk monitor.
• Every icon paired with a word.
• Back button keeps entered data.
• Error messages say what to fix, in plain language.
• Primary action within easy thumb reach on a tall screen.
• Arabic and English versions tested separately.

Watch one real person use it

The fastest test costs nothing: sit beside a parent, an aunt or an office assistant over fifty, hand over the phone and stay quiet. Note where they pause, what they tap twice, and what they ask out loud. Five sessions surface most of the problems, and the fixes are usually small.

Q8DM has worked in software, design and training in Kuwait since 1998, and the pattern holds across sectors: what helps a seventy-year-old helps everyone. Larger type, plainer labels and fewer steps reduce support calls for the entire user base.

If older customers struggle with your app or portal, Q8DM can review the flow, fix the worst screens and test them with real users. Start at q8dm.com.