Big Buttons or Bust: What 70-Year-Old Hands Taught Me About Touch Targets, Contrast, and Calm UI
I'm a systems and network engineer who somehow became obsessed with pixel sizes on a tablet. Not because I love typography debates — because my mother, Evelyn, kept missing buttons that looked "fine" on my phone and then quietly decided the game (or the device, or technology in general) wasn't for her.
That moment is expensive. You can recover from a confusing level. Recovering from "I am bad at this machine" takes weeks.
This is what seventy-year-old hands, living-room glare, and sofa playtesting taught me about touch targets, contrast, and calm UI — lessons that now live inside ChillBrain, and that apply to almost any app you might hand to an older parent.
Guidelines are a floor, not a finish line
Design specs love to say interactive elements should be about 44–48 CSS pixels. That number is useful the way a speed limit is useful: it stops the worst behaviour. It does not describe comfort.
Watching Evelyn play taught me the comfortable zone for older fingers is closer to 60 pixels for primary actions — and even larger when the stakes feel high (confirm, delete, buy, send). Fingertips flatten with age. Fine motor precision drops. A near-miss that a younger player laughs off reads to a senior as failure.
So the ChillBrain rule became: tiles stay chunky even when the puzzle gets hard. If the board can't fit, we change the layout (fewer columns, more scroll) instead of shrinking the pieces. Scrolling is easy. Precision-tapping a thirty-pixel kitten is not.
I wrote more of the playtest stories — including the overlapping-kitten screenshot that still haunts me — in I Playtested ChillBrain With My Mother.
Contrast is not a theme setting
"Dark mode vs light mode" is a taste conversation. Contrast is a usability conversation.
Nearly every older adult I tested with had some reduction in contrast sensitivity. Living rooms are rarely lit like design studios. Afternoon window glare turns elegant grey-on-grey into fog.
What worked:
- Strong separation between play area and chrome.
- Text that doesn't rely on thin weights for meaning.
- Game pieces that differ in more than hue — shape, colour, and a distinct pastel background behind each type in match-3. Colour alone is a trap; roughly one in ten older players has some colour vision deficiency, and almost everyone sees less contrast than the designer does.
We cut early tile designs that looked sophisticated on my monitor and muddy on her tablet. Elegant lost. Readable won. If you're choosing software for a parent, open it in their actual room at their actual time of day before you declare it "clear."
Calm UI means fewer surprises per second
Younger interfaces often celebrate motion: bouncing badges, auto-carousels, toast notifications stacked like pancakes. For Evelyn, surprise motion competed with the puzzle she was trying to hold in working memory.
Calm UI, in practice:
- Animation can delight, but it must not steal the turn. A tile that pops because she matched it is confirmation. A banner that slides in because marketing wanted attention is an interruption.
- Respect reduced-motion settings without deleting joy. Soften or shorten animation; do not mute the sound that tells her the tap registered. Accessibility settings should make a product kinder, not emptier.
- Put ads outside the play. One respectful banner strip below the game is a different moral category from a full-screen takeover mid-level. Interruptive patterns made her put the tablet face-down. That is a severity rating, not a preference.
I wrote about fair versus greedy free-game patterns in Why Free Games Show Ads. The short version for UI: if your monetisation needs to startle someone into compliance, your UI is already failing someone you care about.
Affordance: if it looks tappable, it will be tapped
In Kitty Sort we briefly shipped a decorative basket that looked exactly as interactive as the real shelves — round, cute, centered. Evelyn tapped it. Her friends tapped it. Of course they did.
The fix was not a tutorial tooltip that scolded seniors for "wrong" behaviour. The fix was visual honesty:
- Decorative things went flatter, quieter, obviously inert.
- Real slots got outlines that light up when they can receive a piece.
Affordance is not decoration. For older players it is the whole interface. If two things look interactive, they will treat both as interactive. Designers who grew up on dense iconography forget how much we trained ourselves to ignore.
Drag and tap are both "correct"
Younger testers dragged pieces immediately. Evelyn taps: one tap to pick up, one tap to place. Neither group discovered the other method alone.
Supporting both — carefully, so drag never steals page scroll — meant nobody had to be taught the "efficient" gesture. Meeting the gesture she already trusted beat training her into mine.
If your older-user product only supports one interaction style, you are not being minimalist. You are picking a demographic.
Labels will be read. Every word.
Younger players skip text. Evelyn reads every label on screen. That means:
- Every word has to earn its place.
- Joke microcopy that confuses once will confuse forever.
- Error language that sounds like a teacher marking a quiz wrong will make someone apologize to the software — I watched that happen after a buzz-and-shake on a failed match-3 swap, and we ripped punitive feedback out of the product.
Neutral or encouraging. Offer help. No shame streak theatre. Confidence, once dented, is slow to rebuild in someone who already suspects gadgets aren't for them.
Sound is confirmation, not wallpaper
On glass screens, tactile feedback is weak. Older players often use sound as proof: the pop that says a match landed, the warmer cue that says something bigger happened, a natural voice celebrating a four-match.
Robotic device voices tested terribly. Ambient music mattered less than sound tied to her action. And again: reduced motion should not silence confirmation. Soften the eyes; keep the ears if she relies on them.
A practical checklist before you hand a parent your app
I use a version of this before I call a ChillBrain build "Evelyn-ready." Steal it for anything you build or buy for someone older:
- Primary tap targets larger than the guideline — then larger again for high-stakes actions.
- Pieces never shrink below thumb size; layout bends before fingers do.
- Difference in at least two channels beyond colour (shape, pattern, label, background).
- Test contrast in their room, not yours.
- Decorative elements look inert; interactive elements look alive.
- Tap-tap and drag both work; scrolling still works.
- Motion is confirmation, not a second product fighting for attention.
- Copy assumes it will be read — kind, short, specific.
- No timers dressed up as "helpfulness." Hesitation is not failure.
- Something human remains — a dedication, a clear author, a sense a person made this for a person.
The longer design rules behind ChillBrain's modes are in From Match-3 to Kitty Sort and What I Learned Designing a Game for My 70-Year-Old Mother.
What this changed in ChillBrain specifically
These lessons are not abstract:
- Match-3 fruits stay big and multi-coded.
- Later boards cap complexity instead of microscopic tiles.
- Kitty Sort shelves advertise usability; decoration stays quiet.
- Helpers and rewarded video are opt-in, never a mid-puzzle ambush.
- The opening dedication to Evelyn stayed — her friends still call it the feature.
If you want to feel the difference rather than read about it, play ChillBrain free in the browser — 450 gentle levels, no timers, built for the hands that taught me to stop shrinking buttons.
If you're a builder (or a son) reading this
You will be tempted to defend the design that looked perfect on your display. Don't. The mis-tap is the bug report. The squint is the contrast ticket. The face-down tablet is production down.
Ship bigger targets. Test in their light. Make honesty visible. Then watch whether their shoulders drop when the interface finally stops arguing with their hands.