Case 02 of 04

A document
you can't lose

Native iOS and Android for NSW Births, Deaths & Marriages — a digital cert with the same legal weight as paper, and a proper verified PDF you can send when daycare or a club asks for proof.

Year
2022 to 2023
Role
UX Designer · Thoughtworks
Biometrics, onboarding, a11y, design library
Client
Department of Customer Service NSW
Outcome
Shipped iOS & Android,
POC & pilot (early childhood centres)
DBC certificate gallery screens

01 / Problem

For a lot of families, a birth certificate is the only ID a child has, and it still lives on paper.

That paper shows up everywhere you need to prove who your kid is: daycare, sport, student numbers, you name it. Copies get knocked back, the original is easy to damage or lose, and after floods or fires people really feel how fragile that one piece of paper is.

The Registry needed parents to get something with the same legal weight as paper, and a simple way to hand over a verified PDF when a school or club asks for proof.

  • Fewer “no, we need the original” headaches at enrolment.
  • One place on the phone instead of rifling drawers or emailing blurry photos.
  • Sharing that still reads as official — not a screenshot of a screenshot.

02 / Approach

Trust was the thing we were really optimising for. At the time, the honest read on government apps was that people felt safer when things were actually native on iOS and Android — not one cross-platform UI that looks like neither — so that’s the direction we took.

I sat with the iOS and Android devs and kept each build feeling like it belonged on that platform. Day to day I was mostly in four areas:

Biometrics & permissions Accessibility (WCAG AA) Onboarding & UX copy Design library

Biometrics and permissions. Face ID, Touch ID, Android biometrics — the full sign-in path — with prompts staged so the first open didn’t feel like twenty pop-ups in a row. If biometrics flaked, you could still fall back to a PIN and keep going.

  • Flows that look like banking and the OS settings helped with the “is this dodgy?” gut check.
  • If a scan failed, you weren’t dumped back to square one.

Accessibility. We hired specialists and ran sessions with people who use assistive tech day to day. I helped frame the research, sat in, then patched the designs from what we heard. WCAG AA behaviour and focus order went into the specs so screen reader paths weren’t an afterthought.

  • No mystery meat controls or focus jumping all over the place.
  • The a11y bar was in the documentation early, not a panic before launch.

Onboarding and copy. First run was mine end to end: account, email check, PIN, biometrics, first cert. I wrote the validation, hints, and errors for the lot (email, passwords, DOB, PIN mismatch, etc.) so a mistake read as “fix this” instead of “you broke it.”

  • You could recover from a typo without rage-quitting setup.
  • Copy stayed blunt: what we’re asking, why, what happens next.

Design library. I put in tokens and components — colour, type, 8px grid, SF Symbols, buttons, inputs, lists, the native bits, plus certificate tiles so more than one cert didn’t turn the home screen into a mess.

Certificate preview screens
Certificate preview in-app before you share anything.
Share drawer
Verified PDF out through the native iOS share sheet.

03 / Outcome

We shipped production iOS and Android apps and ran a proof of concept and pilot with NSW early childhood centres.

Technically it’s MFA, biometrics, multiple certs per account, verified PDFs out through the system share sheet. For parents the pitch is just: the real document lives on the phone, you can share it when someone asks, and we didn’t hand-wave the security bits.

  • Legally the same as paper, just not stuck in a drawer.
  • Orgs get something they can take seriously, not a photo of a creased scan.
  • In the pilot, centre staff and parents actually bought the trust story — that was the test.

Small postscript: digital birth certs have since rolled into the Service NSW app — which is more or less the consolidation we’d argued for on the project. Funny how time works; nice when the roadmap catches up.

DBC iOS design spec showing VoiceOver focus order annotations
Focus order in the shipped iOS kit — screen reader paths spelled out in the docs.
Next case

Events
Creator