Begin with the event
“I lost my licence” is a usable starting point. A department name, form number, or administrative category is not.
Selected work / systems in context
Better Software Begins with a Clearer Journey.
These projects range from a public-service prototype to focused business websites. The common work is not decorative polish. It is deciding what a person needs to understand, what should happen next, and how the digital path should carry that intent.
Build What Moves India submission
Parivahan, Reorganised Around Intent.
A citizen rarely arrives thinking, “I need the duplicate driving licence service.” They arrive because a licence was lost, damaged, or stolen. The prototype starts with that event and resolves it into the correct service.
This is a functional, independent prototype built with synthetic identity, document, payment, appointment, and notification providers. It is not an official government service or a claim of production integration.
Explain before applying
Fees, documents, timing, online steps, offline requirements, and state differences appear before identity verification begins.
Make recovery part of the path
Document correction, pre-approval, failed-payment retry, appointment differences, and status history are treated as ordinary workflow states.
Designing for a difficult moment
Fewer Unknowns Before the First Form Field.
Losing a licence creates uncertainty before the website opens: Which service applies? Which documents are needed? Will an office visit be required? What happens if a file is rejected or a payment fails? A portal increases cognitive load when it makes the citizen translate that situation into administrative language before offering help.
The redesign keeps choices literal and the route predictable. A muted blue, green, warm orange, and off-white palette was chosen to feel quieter than a warning-heavy interface. Colour supports hierarchy, but the main calming device is procedural: tell people what lies ahead and keep the current state visible.
These are design hypotheses embodied in the prototype, not measured claims about citizen outcomes. The next responsible step would be usability research with real people, including users under time pressure and people who rely on assistive technology.
Evidence in the build
- English and Hindi journeys
- Delhi and Uttarakhand rule configurations
- Keyboard skip navigation and text-size controls
- A 320 px / 200% text reflow check
- Document correction with version history
- Payment retry and application status tracking
The architecture separates service rules from interface code and defines replacement points for production identity, storage, payments, appointments, and notifications. That makes each journey trackable without pretending the prototype owns the government systems behind it.
Focused web delivery
Small Websites Still Need a Complete Operating Path.
A basic website is only basic in scope. It still needs a clear offer, responsive design, versioned code, a dependable route for enquiries, and a hosting setup someone can maintain after launch.
Manufacturing website
Elza International
A focused company website for an OEM manufacturer, with a clear visual identity, catalogue discovery, validated enquiries, and a GitHub-backed delivery path.
GitHub-backed version control and deployment workflowValidated lead collection routed into Google Forms
Developer portfolio
apnatva.dev
A personal portfolio with three presentation modes, one underlying body of work, a direct hire route, and a validated lead-collection endpoint.
GitHub-backed version control and deployment workflowValidated lead collection routed into Google Forms
A practical hosting option
Start with Hosting That Fits the First Release.
Hosting should match the application’s runtime, traffic, deployment method, backups, and maintenance needs. If Hostinger fits that assessment, our referral link provides 20% off hosting.
Affiliate disclosure: Brownsmith Dynamics may receive a benefit if you purchase through this link.
From journey to implementation
Bring the Workflow, the Difficult Moment, or the Unclear Path.
We can turn it into a clearer interface, a trackable system, or a practical first release with a responsible path to production.