Wireframe Design System

Case Study

Wireframe Design System

A shared wireframing language and component library for Ackee's mobile design team

Design System Architect2024

Role

Design System Architect

Timeline

3 Months

Platform

Desktop / Mobile

Tools

FigmaFigma
ClaudeClaude
NotionNotion

Overview

The Challenge

At Ackee, most new mobile projects began with a wireframing phase — but each designer approached it differently, creating inconsistency in handoffs, review quality, and client communication. I was tasked with creating a shared wireframe design system: a common visual language and component library that every designer at Ackee could use to wireframe mobile projects, regardless of their individual style.

Case study detail

Research & Discovery

Key Findings

Finding 01

80% of mobile screens across Ackee's project history used the same 30 core component patterns — a focused library could cover almost everything

Finding 02

The biggest time sink was not component creation, but aligning on annotation and label conventions between designers and developers at review

Finding 03

A two-tier colour system — neutral greys for wireframe elements plus one accent for interactive states — provided maximum clarity with minimal visual noise

VIEW ALL

Design Process

How We Got There

01
Define
02
Research
03
Analyze
04
Design
05
Test

I began with the primitive token layer: a spacing scale (4 → 64px), a type scale (10–32px), and a nine-step neutral colour ramp (white to near-black). From primitives, I derived semantic tokens — background, border, text, interactive — applied consistently regardless of the specific component. Every component auto-layouts and updates cleanly when a primitive token changes.

The library was organised into six categories: Navigation, Layout, Forms, Data Display, Feedback, and Media. Each component included defined variants (default, filled, disabled, error) and was fully auto-layouted. A ready-made annotation layer let designers document specs without building a separate red-line file, cutting review preparation time significantly.

VIEW ALL

Final Design

The Solution

Final design
#1

120+ components across six categories

fully token-driven and auto-layouted for fast customisation

#2

Adopted by the full Ackee design team within two weeks of launch, covering all new mobile project starts

#3

Estimated 2–3 days saved per project in wireframe setup and alignment time across the team

Takeaways

Reflection

Building for other designers is the strictest possible test of clarity. Every ambiguous naming convention, every missing variant, every undocumented exception became a question in my inbox within the first week. The systems that survive long-term in fast-paced agencies are the ones that make the most common task effortless — not the ones with the most components.

Final design detail
PreviousAB Testing in Livesport
NextBuilding My Personal Brand
+
+
+
+
0000 · 0000
Daniel Gratza

Let’s make something great.

Prague-based UX designer

Get in touch