Mobile Development 35 min read

Designing Elder‑Friendly Banking Apps: Practical Guidelines and Real‑World Cases

This article explains how to create senior‑friendly banking mobile applications by following the "Mobile App Elderly Design Specification", covering entry design, perceptibility, operability, understandability, compatibility, and security, and provides concrete examples from major Chinese banks.

Zhaori User Experience
Zhaori User Experience
Zhaori User Experience
Designing Elder‑Friendly Banking Apps: Practical Guidelines and Real‑World Cases

1. Elderly Version Entry Design

1.1 Embedded Elderly Interface

Enter the elderly version by embedding a special interface within the original app, usually placed in Settings. Many banks follow an "all‑in‑mobile" approach, offering quick switches from various locations.

Common Switch Names

ICBC: "Happy Life" version; Bank of China: "Years of Affection" version; Everbright Bank: "Simple Love" version; Gansu Bank: "Elder" version; Alipay: "Elder Mode"; China Merchants Bank/WeBank: "Elder" version; Agricultural Bank of China/Pay on behalf: "Large‑Font" version; Ningbo Bank/Cloud QuickPay: "Care" version, etc.

Common Switch Locations

1) Top‑level page "Version Switch" button; 2) Drop‑down plus sign on first‑level page; 3) My‑page → Settings → "Version Switch".

Typical click paths include:

Home → Version Switch Icon → Elder Version

Home → Version Switch Icon → Version Selection → Choose → Elder Version

Home → Drop‑down → Version Switch Icon → Elder Version

My‑page → Settings → Version Switch → Elder Version

Transition Page Design

Some banks provide dedicated transition pages that describe each version, giving users a mental expectation before switching.

1.2 Separate Elderly App

Some companies develop a standalone elderly app (e.g., Kugou, UC, Baidu Maps/News, Tencent Maps/News, Sina Weibo). Banking products have not yet launched separate elderly apps.

2. Perceptibility

2.1 Font Size Adjustment

Font Type

Sans‑serif fonts are clearer for seniors; use bold weight to improve legibility. Chinese fonts such as Source Han Sans or Microsoft YaHei are recommended, while serif fonts like Song or Kai are discouraged.

Font Size

The specification suggests a minimum of 18 dp/pt for main text. Some guidelines calculate a minimum of 16 dp/pt based on reading distance. Designers should adopt the larger size when possible.

Adaptation Rules

Avoid clipping; ensure text wraps or ellipsis appropriately.

Scale containers proportionally with enlarged text.

Maintain fixed horizontal spacing; vertical spacing can scale proportionally.

2.2 Line Spacing

Paragraph line spacing should be at least 1.3×, with paragraph spacing larger than line spacing.

2.3 Contrast

Text and icons must have a contrast ratio of at least 4.5:1 (or 3:1 for large text) to meet WCAG AA/AAA standards.

2.4 Color Usage

Do not rely solely on color to convey meaning; combine with underlines, bold text, or icons.

2.5 Captcha

Use clear image captchas with zoom options; avoid complex non‑text captchas for seniors.

2.6 Icon Design

Scale icons proportionally and pair them with descriptive text.

3. Operability

3.1 Component Touch Area

Touch targets should be at least 60 × 60 dp/pt for main components in embedded versions, and no less than 44 × 44 dp/pt for others.

3.2 Gesture Operations

Prefer simple gestures: single‑tap, vertical/horizontal swipe, pinch‑zoom. Avoid multi‑finger gestures.

3.3 Sufficient Interaction Time

Provide longer display times for messages (e.g., toast from 3 s to 5 s) and use persistent dialogs instead of transient pop‑ups.

3.4 Floating Windows

Close buttons must be placed at top‑left, top‑right, or bottom‑center with a minimum touch area of 44 × 44 dp/pt.

3.5 Convenient Data Entry

Offer limited options and defaults.

Prefer selection over typing.

Use photo/QR code scanning for long inputs.

Auto‑fill related fields.

Provide history of frequently used items.

3.6 Shorten Operation Paths

Simplify navigation, reduce hierarchy depth, and provide progress indicators for multi‑step tasks.

4. Understandability

4.1 Prompt & Guidance

Show prominent onboarding prompts when the elderly version is first installed or activated, and clearly indicate how to return to the standard version.

4.2 Voice Function

Integrate AI‑driven voice input, real‑time assistants, and speech feedback, while allowing volume and speed adjustments and supporting dialects.

4.3 Plain Language

Use everyday wording, clear error messages, and actionable prompts (e.g., "Please enter a 12‑digit account number").

4.4 I‑Model Layout

Adopt a simple vertical layout that keeps the visual focus within two transitions.

4.5 Concrete Imagery

Prefer realistic photos over abstract illustrations to improve trust.

5. Compatibility

5.1 Assistive Technologies

Ensure the app works with screen readers and other assistive devices without disabling functionality.

6. Security

6.1 No Promotional Content

Prohibit ads and inducement buttons in the elderly version to protect vulnerable users.

6.2 Build Trust

Display security badges, mask sensitive data, and add anti‑fraud tips to reassure seniors.

Chapter Summary

Key takeaways: 1) Font size ≥18 dp/pt; 2) Strong contrast; 3) Concrete images; 4) Action‑oriented verbs; 5) Familiar icons and wording; 6) Rich colors; 7) Click over swipe; 8) Click over typing; 9) Multi‑modal (voice) support.

Bank Product Case Studies

1. ICBC – "Happy Life" Version

Entry: multiple top‑level switches and My‑page → Settings. Exit: similar paths. Highlights: consistent entry/exit, simplified layout, voice assistant at prime position, curated features for seniors.

2. China Merchants Bank – "Elder" Version

Entry: My‑page → Settings → Elder version. Exit: Home → bottom‑pull → standard version. Issues: hidden entry, no prompt on activation.

3. Bank of China – "Years of Affection" Version

Entry: Home → version or My‑page → Settings. Exit: My‑page → standard version. Strengths: clear entry design, initial guidance; Weakness: exit lacks confirmation.

4. Agricultural Bank – "Large‑Font" Version

Multiple entry points, consistent exit, clear layout, voice assistant, strong color contrast.

5. Ningbo Bank – "Care" Version

Minimalist page, removed bottom tab bar, but floating voice button is hard to use; limited adaptation on sub‑pages.

6. Ping An Pocket Bank – "Large‑Font" Version

Clear structure, senior‑focused features (anti‑fraud guide, elder insurance), concrete icons with text, full sub‑page adaptation.

7. Cloud QuickPay – "Care" Version

Simplified layout, double‑confirmation on exit, but sub‑pages lack large‑font adaptation.

8. Jiangsu Bank – "Happy Living" Version

Consistent entry/exit, concise layout, one‑click help, voice introduction, anti‑fraud guide, calendar mode for seniors.

Conclusion

The article reflects extensive research on accessibility and elderly‑friendly design, emphasizing the importance of larger fonts, high contrast, concrete visuals, simple gestures, and trust‑building security measures. It encourages designers to adopt these practices to improve digital inclusion for older adults.

user experienceaccessibilitysecurityDesign Guidelinesmobile bankingelderly design
Zhaori User Experience
Written by

Zhaori User Experience

Zhaori Technology is a user-centered team of ambitious young people committed to implementing user experience throughout. We focus on continuous practice and innovation in product design, interaction design, experience design, and UI design. We hope to learn through sharing, grow through learning, and build a more professional UCD team.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.