VisionVision · not available today. Satin never runs on banking or payment pages.
Where OwnUX is goingPublic services in every citizen’s own words. Each person’s language and reading level.
Vision: the OwnUX SDK is in development and doesn’t support forms like these yet. Screens on this page are illustrative.
Request a copy of a birth certificate
Part A · Particulars of registrant
A1. Full name of registrant (as entered in register) *
A2. Date of occurrence of birth (DD/MM/YYYY) *
A3. Place of occurrence (hospital / institution / residence) *
Particulars must be furnished exactly as recorded. Any discrepancy may delay processing of the application.
Language
Reading level
Set once by the citizen. Honoured everywhere. Interface DNA is the citizen’s own profile. Your service reads only what they share.
Their language. Labels, help text and messages in the language they chose, from the translations your team approves.
Their reading level. Official, standard or plain wording, always keeping the meaning of the original.
One question at a time. Short steps for people who want guidance, the full form for those who don’t.
Larger text, stronger contrast. Visual settings applied on every page of the service, not one page at a time.
Keyboard or pointer. Keyboard-first interaction for people who don’t use a mouse, with the same shortcuts on every form.
Dates their way. Date format and week start from their locale, so 03/04 is never a guess.
Letters and notices
Notices people can act on. The same letter, at the reading level each person asked for.
Your content team writes plain and standard versions beside the official one. OwnUX shows each person the version their Interface DNA asks for. Reference, deadline and consequence never change.
- Your team writes and approves every version.
- Facts, dates and references stay identical across versions.
- Every notice ends with one clear next step.
Ref. BC-2026-48113. With reference to your application for a certified copy of an entry in the register of births, it is hereby notified that the documentation submitted is incomplete. The applicant is required to furnish proof of current residential address, in one of the prescribed forms, on or before 14 November 2026, failing which the application shall be deemed to have lapsed and no further action will be taken.
Words
69
Words per sentence
17
The department stays in charge. OwnUX changes how a service reads, never who decides or what the law requires.
Locked surfaces. Declarations, fees, payments and identity checks are listed in your manifest. OwnUX never re-renders them.
Your rules and records. Eligibility, validation and permission checks stay in your backend. OwnUX holds no permissions of its own.
Your design system. Screens use your own components and tokens, so every page still looks like your service.
Your rollout. Roll out to a share, keep a holdout group, and switch OwnUX off from your code.
In developmentThe OwnUX SDK is in development. Today’s alpha runs in our Reference App, works with React and covers tasks. Forms like the one above need capabilities beyond the alpha; talk to us to help shape them.
From one form to the whole service. How a department adopts OwnUX.
- 1
Write a manifest
List the actions OwnUX may offer, how risky each is, and the screens it must never touch.
- 2
Bring your components
Map OwnUX’s building blocks to your own design system and tokens, so every screen stays recognisably yours.
- 3
Pass conformance
Run ownux test. L1 checks the manifest. L2 checks actions execute, verify and fail safely, including denied permission.
- 4
Roll out and measure
Start with a share of people and a holdout group, then compare completion against those without OwnUX.
Questions, answered.
No. This page is about the OwnUX SDK, which your team builds into your own service, where people set their preferences. The Satin extension is a separate product for work apps, in development: Jira Cloud first, then Linear.