Turning a complex admin interface into a consistent, scalable system

Context

Halito! is a SaaS platform that helps users create event websites and manage registrations.

The backend had grown over time and the experience started to feel inconsistent. Patterns weren’t reusable, UI decisions differed between screens, and the interface required extra effort to navigate.

The goal was to redesign the admin so it felt clear, coherent, and easy to extend as the product evolved.

The real challenge

This wasn’t only a visual redesign.

The real challenge was to introduce structure without slowing the team down, and make sure the new UI stayed consistent when new features would inevitably be added.

That meant solving for:

Consistency across pages and states
Navigation clarity inside a feature-rich admin
Reusable patterns so delivery stays fast

In other words: create an interface that users could understand quickly, and developers could extend confidently.

My role

I was responsible for redesigning the backend and building the new interface.

My role included:

UI/UX design for key admin screens and flows
defining a clearer information hierarchy and page structure
frontend development of the redesigned backend (Vue.js)
creating a component library so the system could scale

The aim wasn’t just “a nicer UI”, but a backend that felt predictable and maintainable.

What I focused on

I focused on making the admin feel stable: users should always know where they are, what they can do, and what happens next.

Key areas of focus:

a navigation structure that supports fast scanning and deep workflows
consistent page templates: headings, actions, spacing, states
UI patterns that reduce decision fatigue and improve learnability
component rules that keep the UI coherent once multiple developers contribute

The goal was clarity first, with flexibility built on top.

What changed

The redesign introduced a calmer, more structured backend experience.

Users got:

better orientation through clearer navigation and page structure
more consistency across screens, actions, and states
a dashboard that provides instant context after login

The product became easier to learn, easier to use, and easier to keep consistent as new features were shipped.

Why this approach worked

The redesign wasn’t treated as a one-off project, it was treated as a system.

By pairing UI decisions with a component library, the backend could evolve without drifting back into inconsistency.

Because design and implementation were closely aligned, the intent behind the redesign survived production constraints, and stayed coherent over time.

Takeaway

Admin interfaces don’t become complex overnight. They grow feature by feature.

The way to keep them usable is to introduce structure early: consistent patterns, clear navigation, and a component system that protects the experience as the product scales.