Back to portfolioUNILOCKER / CASE STUDY

MOBILE DOCUMENT WALLET

UniLocker

Important documents.
Closer to their owner.

A DigiLocker-style document wallet connecting multilingual entry, account creation, document discovery and issued records with virtual identity and access consent. Across 17 supplied screens, the experience moves from getting started to retrieving records and sharing an identity.

Discipline
UI/UX design
Platform
Mobile app
Current scope
17 supplied screens
Context
South African document examples

THE DESIGN CHALLENGE

More than a folder
on a phone.

A document wallet needs to answer three questions: where is my record, how can I present or share it, and who can access it? The design challenge is to connect account setup, discovery and identity handoff without overwhelming people with administrative language.

The supplied screens suggest a multilingual, identity-led experience with South African document examples. This case study analyses the visible UI and its design trade-offs; it does not claim user interviews, measured adoption, legal acceptance or a verified security implementation.

THE EXPERIENCE

Enter. Find. Identify. Control.

  1. 01

    Getting started

    Brand introduction, language, account entry and registration.

  2. 02

    Finding documents

    Personal dashboard, catalogue discovery, filters and issued records.

  3. 03

    Identity & trust

    Profile, document details and virtual ID sharing, download and print actions.

  4. 04

    Control & activity

    Account preferences, access requests and notifications.

SCREEN EXPLORER

The details behind each decision

01 / Getting started

Establish a recognisable document-wallet identity

The globe-and-lock mark introduces UniLocker on a quiet mint background. A restrained splash screen gives the product a recognisable entry point before the more functional choices of language and account access.

Design consideration

A branded entrance should remain brief. The supplied static screen does not show loading duration or transitions.

01 / 17
Splash / Supplied UI design

DESIGN RATIONALE

Access and trust share the same interface.

Language before complexity

Put language selection at the entrance and make it available again in the account hub. Validate translations and longer labels before expanding the locale set.

Retrieval before exploration

The personalised dashboard prioritises issued records and utility shortcuts; the discovery screens offer provinces, categories and filters. Keep search scope explicit so catalogue documents are not mistaken for records already held.

Identity with a usable handoff

A readable document view establishes context, while the dedicated virtual ID makes QR sharing, downloading and printing easy to locate. Trust labels and legal-equivalence copy still need technical and jurisdiction-specific verification.

Control at the point of access

Place requester, document and decision together. A complete consent journey should also explain duration, access scope, confirmation and how to revoke permission.

DESIGN OUTCOME

From account entry
to identity handoff.

The 17-screen design connects account creation, personalised retrieval, catalogue search, issued records, virtual ID export and consent decisions. Its strength is the continuity between finding a record and knowing what to do with it. The supplied set documents this design scope, not measured product performance; verification, recovery and post-approval states remain areas for validation.

What to validate next

  • Can people complete registration and distinguish catalogue search from records already issued to them?
  • Do they understand what QR sharing exposes, what an access approval allows and how to revoke it?
  • Are language choice, form validation, text contrast and touch targets accessible across locales?
  • Are identity claims legally appropriate to the region, and do failed verification, export and account-recovery states explain what happens next?

These are proposed validation questions, not completed research or measured outcomes.