Cloud Infrastructure Platform
ClappIt
ClappIt is a cloud infrastructure platform — clusters, pods, services, data sources, alerts and network traffic in one product. I simplified its workflows for both technical and non-technical users, through clearer information architecture and navigation, and reusable UI components and design patterns across its modules.
- Role
- UX Designer
- Timeline
- 2023–2024
- Format
- Project summary
Infrastructure, for more than infrastructure engineers
The same product had to make sense to the engineers running it and to the people who only needed to know whether it was healthy.
- Many kinds of infrastructure object — clouds, clusters, projects, apps, services — each with its own state.
- Operational signals — health, performance, errors, alerts, traffic — competing for attention on one screen.
- Users with very different technical depth working from the same interface.
What the dashboard shows
Each decision below is visible in the dashboard design above.
Navigation by infrastructure object
A persistent rail — Dashboard, Clouds, Cluster, Projects, Apps, Teams, Settings, Services — so a user always knows which layer they are in.
Cluster context in the header
Provider, cluster, node status, nodes available and last update sit together, with Refresh, Kill and Clone beside the context they act on.
Severity-coded alerts
Critical, High, Medium and Low, with a legend, timeline and severity filters, and acknowledge or dismiss inline.
One reusable panel pattern
Title, filter, refresh, overflow menu and a “View all” exit — the same shell for pods health, application performance, services, data sources, errors, alerts and network traffic.
Status in words, not only colour
Healthy, Poor and Warning are written out next to their colour, so state is readable without relying on colour alone.
Workspaces as tabs
Namespaces open as tabs at the foot of the workspace, so switching context does not mean losing it.
Structure first, then a system
- Simplified complex cloud-infrastructure workflows for technical and non-technical users.
- Restructured information architecture and navigation around the objects users actually manage.
- Created reusable UI components and scalable design patterns across product modules.
What this project demonstrates
- Complex technical products
- Infrastructure workflows
- Information architecture
- Reusable UI patterns
This is a summary rather than a full case study. A walkthrough of the work is available on request.
Want to work together?
Let's make complex technical products usable.