Wireframe Book

The landing screen: greet the citizen, orient them among 200+ services, and route them to anything — a new application, their wallet, a payment, help — in one or two taps.

Three ways a national super app can spend its most valuable surface: on tasks, on status, or on breadth. The choice decides who feels at home on day one.

The Home screen as designed, and a proposed upgrade that folds the review findings in — same skeleton, five precise changes.

The first minute a citizen spends with the state online: arrive, choose a language, prove identity without a password, agree to what's shared, and land ready to act.

The structural options considered for this journey. Sign-in and consent each carry a genuine design decision, explored below; the remaining screens follow a single settled pattern, noted at the end.

The recommended path, from first launch to a ready home screen.

The app's standing rooms: browse the full catalogue of services, and manage your own account. (The Wallet, the third main surface, is documented with the credential journey in section 04.)

Browsing 200+ services is the one genuine design decision here — how a citizen who doesn't know a service's name still finds it. The profile screen follows a settled pattern, shown after.

From "I need something from the government" to a confident start, whichever way the citizen arrives.

Hold the citizen's verified identity and signed credentials in one place — and let them prove any of it in seconds, offline, at a roadside stop or a counter.

The structural options considered for this journey. The wallet home and the credential-presentation screen each carry a genuine design decision, explored below; capture, sync, licence and fuel-quota screens follow a single settled pattern, noted at the end.

The recommended path, from an empty wallet to a credential presented and verified offline.

The wallet's second story: a credential approaches expiry, the citizen renews without re-entering a fact, and the wallet quietly holds the new one.

The field officer's side of the trust model: sign in under RBAC, scan a citizen's presented QR, and get a Valid / Invalid answer in seconds — entirely offline, with a reason the officer can act on and a citizen can understand.

The verification result is the one screen here with a real design decision — everything an officer needs, readable at arm's length, in the second after a scan. Login and scan follow a single settled pattern, shown after.

The officer's path, from portal to a logged result — every step offline.

The surfaces that keep the relationship honest: an assistant that helps in any language, consent that stays revocable, notifications on the citizen's terms, a lock that guards the phone in a pocket, and a payment gateway that never asks a citizen to guess what they owe.

The assistant is the one genuine design decision here — how much the helper does, and in whose language. The four settings surfaces follow settled patterns, shown after.

Consent is not a screen but a relationship: granted once, reviewable always, revocable with honesty, renewed when the terms change.

Find a government service, apply with only the details SLUDI can't supply, pay, and leave with a tracked reference — or route to an office when that suits the citizen better.

The structural options considered for this journey. Service detail, the application form, and payment each carry a genuine design decision, explored below; review, confirmation and tracking follow a single settled pattern, noted at the end.

The recommended path, from opening a service to a tracked application.

Screens the app doesn't have yet — each one already promised elsewhere in this book: the bell that needs an inbox, the payment that files a receipt, the credential that opens a detail, the citizen who loses a SIM. Proposed as additions, never as redesigns.

One shared language for the moments the network fails, data is missing, or the app needs something. The genuine decision: how the app announces being offline.

The bell's destination. Application updates, payment confirmations, expiry reminders and policy changes land here — mirrored by SMS according to the citizen's preferences. The genuine decision: is an inbox a news feed, a case file, or a to-do list?

The proof of the state's word — promised on every paid outcome. A light decision: where does the receipt live, and what does it look like when a citizen needs to show it?

The Wallet's tap-through — what a credential is, where it came from, and what can be done with it, with the QR an explicit choice rather than a surprise. The decision: how much surface the detail deserves.

The day the phone is stolen, the SIM changes, or the number moves on — and the OTP that guards everything can no longer arrive. A full journey, because losing access to government must never mean losing government. The decision: who does the recovering.

The ledger behind the consent manager's promise that "every share is logged" — a settled structure: one chronological ledger, filterable, in plain language. No exploration needed; the design decision was made when consent was.

The destination behind every "Get help" in the book — a settled structure with one rule: the human route leads, and it works even when the app barely does.

The flow behind every "Something wrong? Report it": when the state's record of a citizen is wrong, fixing it must be as designed as using it. A tracked correction request, with the citizen's work never held hostage to the error.

The destination behind Profile's edit button — the calm, signed-in way to change a mobile number or email, cousin to account recovery but without the crisis.

The right to leave, honestly designed: what closing removes, what it cannot, and a ceremony that respects the decision without trapping or shaming.