Identity application

Build with Vlak
NorthmereResident services · Fictional municipality
Local demo
Step 1 of 3 · Your details

Let’s start with you

We’ve filled in a fictional applicant so you can try the process.

Document type
Used only in this local sample receipt.

You can return to these details before creating your receipt.

About 3 minutes
Opening local draftFictional records · No government connection

Complete the applicant details → attach sample evidence → review → create a local receipt

View source

Inside the interface

A fictional municipal service that guides an applicant through their details, supporting evidence, and a final review. A quiet progress rail keeps the full process visible while the working screen concentrates on one decision at a time. The resulting receipt belongs to this browser, with no government submission or identity verification.

Use the fictional applicant or edit the sample fields. Add and remove sample evidence, return to earlier steps, and create a local receipt. The draft is saved in this browser when local storage is available; no information is sent to a government service.

Use this as a starting point

Build with Vlak

Install the components, add the stylesheet, and bring your own content. The study’s source shows how the pieces fit together.

React componentsCSS includedMIT licensed
Install the package
npm install @noorddev/vlak-react
import "@noorddev/vlak-react/css";

Start with your coding agent

A ready-to-use brief with this study, Vlak’s components, and the design guide.

Component modifications

  • Input and Select form the applicant screen. Native validation gates the next step; the same draft survives step changes and reloads when browser storage is available.
  • Evidence checklist actions attach named fictional records. The application owns their state and permits removal before review; the component never claims upload or verification.
  • Identity document becomes a clearly marked specimen inside a square review region. Application status records the local receipt and explicitly keeps government submission outside the demo.
  • At 640px and below, the desktop process rail becomes a compact step indicator. Applicant, evidence, review, and receipt occupy one focused screen with an independently scrolling body and pinned Back and Continue actions. Inputs remain 16px and controls at least 44px at 320px wide.