UPHDB Jeevan Pramaan

What this prototype is for

Usability testing with real pensioners, and showing the Board the full submission journey before a vendor is appointed. Every screen here is a screen the vendor must build.

Jump to any screen

Design decisions, and why

• 16px minimum body text. The primary user is 60–85. Nothing on screen is below 12px, and no action target is under 44px.
• One decision per screen. No screen asks for two unrelated things. Reduces abandonment for first-time smartphone users.
• Consent is a full screen, not a checkbox in a corner. Required under the Aadhaar Act and DPDP Act. It must be readable and refusable.
• Hindi first, English available. Language is chosen before anything else and persists.
• Failure states are designed. Face auth genuinely fails for elderly users — cataracts, tremor, poor light. The retry path and the offline fallback matter as much as the happy path.
• No Aadhaar number displayed after entry. Masked to last 4 digits everywhere downstream.

What the vendor must replace

• Face capture screen — swap the simulation for the AadhaarFaceRD intent (Android) / SDK call (iOS). This is the only screen with a hard licence dependency.
• Certificate ID — currently generated locally. Must come from a signed backend response.
• Pensioner lookup — currently fixture data. Must query the UPHDB pension master.

Handover note

The auth step is isolated in a single function so the RD service integration replaces one module, not a rewrite. The rest of the flow — validation, consent capture, state, screens — carries forward as specification.