Project / Public-service applications
GoMUSI.
A request, through its next steps.
A service application has two sides: the person submitting information and the people reviewing it. GoMUSI connects service information, forms and the steps a request moves through.
The product
GoMUSI organises public-service information and applications around forms and a sequence of service steps. Its interfaces include service selection, submissions, review and submission details.
Administrative tools support the management of services, forms and ordered flow or wizard steps.
My contribution
I worked on the frontend and backend. The scope includes applicant-facing interfaces and the application services behind forms and service flows.
The administrative side is part of the product scope: teams need to manage what applicants see and the stages a service requires, rather than relying only on a fixed public form.
Selected product flows
- A catalogue of services and their requirements.
- Multi-step application and information collection.
- Submission details, progress and review.
- Administrative form, service and flow management.
For a similar project
This work is relevant to a business or institution replacing disconnected forms with a structured application process.
That experience also applies to application portals, intake workflows and administrative tools that need to work together.
The interface
Application and review interfaces.
Select an image to enlarge it; use Actual size to inspect small details. The existing web application, captured locally with synthetic API responses. These selected crops show the service flow, applicant form, tracking and an unsaved administrative draft. No real application is submitted.
A project in mind?
Tell me what you’re building.
Share the problem, who will use the product and what you already have. We can discuss the scope and whether I can help.