Application DeskMaking a dense register easier to act on.
This separate desktop workspace grew out of the practical difficulty of keeping application records, next steps and evidence understandable. It is also a focused study in UI craft and prototyping in code.
At a glance
- The problem
- Competing panels made records and their next actions harder to scan.
- My contribution
- Designed a shared register, connected status views and interaction states in code.
- The outcome
- A local desktop prototype with search, filters, notes and evidence links.
The problem & my role
Repeated information and competing panels made the next useful action harder to find. Visual refinement also needed to preserve the meaning of data and the reliability of editing.
What I owned
I shaped the hierarchy, register, chart interactions, material treatment and motion through repeated design review and code prototypes. I kept data accuracy and existing workflows as constraints during visual iteration.
- Interface
- Searchable register
- Visualization
- Source-backed status views
- Continuity
- Preserved notes and filters
Key design decisions
Charts and controls filter the same application list rather than creating separate versions of the records.
Outcome & reflection
A working local desktop dashboard brings the application register, activity, work arrangement and outcome views into one workspace. It supports search, filters, notes and evidence links.
The interactive example uses fictional data and a simplified interface. It illustrates the design principles without publishing private application records. The local development interface is not a commercial release.
What I would test next
Evaluate how quickly someone can find the next action and understand the status of a record.