Fill new look: faster, calmer interface (Bootstrap → Spartan)
Over the past years, Fill has grown quickly—features shipped fast, workflows expanded, and different parts of the product evolved at different speeds. That helped us move, but it also left us with a UI that sometimes felt inconsistent: small visual differences, components that behaved slightly differently from page to page, and more manual UI work than we want—both for us and for you.
We’re changing that.
We’re migrating the product from Bootstrap to Spartan, our design system. This is a foundational UI upgrade focused on one outcome: make it easier to act—with less friction, fewer surprises, and a faster feel across the product. Read more here.
The philosophy
Good enterprise software shouldn’t feel “enterprise.” It should feel obvious.
Our approach is simple:
Clarity over decoration — the UI should explain itself
Consistency over options — fewer patterns, used everywhere
Speed as a feature — the product should feel immediate
Systems over one-offs — less manual tweaking, more reliable UI
Spartan is how we make that real across the whole platform.
What’s changing (and why you’ll notice it)
A more consistent experience
Buttons, tables, modals, forms, and navigation follow the same rules everywhere—so you don’t have to re-learn the UI depending on where you are.
Faster interaction
Cleaner component structure and fewer UI “workarounds” means less latency, fewer layout glitches, and a snappier product feel.
Easier to take action
We’re simplifying spacing, hierarchy, and states (empty, loading, error) so next steps are clearer—especially in high-volume workflows.
Better foundation going forward
This migration reduces the internal “manual twiddling” needed to keep pages consistent, which means we can ship improvements faster—without introducing UI debt.
What stays the same
Your data, permissions, and workflows stay intact
No migration work is required from your side
This is a UI foundation upgrade, not a workflow redesign (unless explicitly communicated in a specific release note)
Rollout timing
We’ll roll this out gradually during Q1 2026:
Pages will update in batches rather than everything changing overnight
You may see some areas updated earlier than others during the rollout window
We’ll keep release notes updated as key sections move to Spartan.
What’s next
Once the foundation is in place, we’ll use Spartan to improve:
information density (more signal, less noise)
navigation speed (fewer clicks for common actions)
workflow guidance (clearer statuses, next steps, and exceptions)
accessibility and quality (keyboard support, focus states, predictable UI behavior)
