Design System
Zendr is a multi-surface product ecosystem: Web ERP dashboard, Mobile App, Staff Portal, and B2B Ordering Portal. Early design work across these surfaces resulted in repeated patterns, inconsistent interaction decisions, and duplicated engineering effort. To scale faster, we needed a unified design system that could support multiple teams, platforms, and release cycles - without slowing down product growth. The system was built to be practical, repeatable, and developer-led, thus focusing on real workflows and shared components rather than purely visual consistency.
Year
2025
Service
System Design
Category
Design
Tool
FigJam, Figma, Confluence, JIRA
Core Goals:
Reduce time-to-ship for new features and product surfaces.
Unify UI patterns across desktop and mobile to avoid relearning.
Enable engineers to build without waiting for new screens or mocks.
Key Principles:
Token-first foundation → Colors, typography, spacing defined once.
Shared interaction patterns → Lists, forms, modals, nav, selection states.
Responsibility split → Design defines systems, engineering owns scalable implementation.
Foundation:
Scaleable color token system for light/dark modes + semantic states.
8px spacing system that works fluidly across canvas sizes.
Typographic scale optimized for data-heavy layouts and compact UI.
Patterns:
Tables & data grids optimized for density, scanning, and inline actions.
Detail views with consistent header hierarchy and action groups.
Mobile navigation system structured around quick actions vs browsing.
Components:
Buttons, inputs, cards, list items, alerts, tags, nav bars — each built once, reused everywhere.
Designed to be swappable: one component works across web, mobile, staff portal, and internal tools.
Product & Delivery:
Reduced design-to-dev handoff time by 40%
Enabled 3× faster feature rollout across platforms
Simplified onboarding for new designers + engineers
Team & Collaboration:
Shared vocabulary → fewer meetings, clearer feedback
Reduced subjective debates → decisions grounded in system logic
Empowered engineers to prototype independently
Business Value:
Allowed the company to scale product surfaces without scaling team size linearly
Increased product consistency → improved user trust and usability
Created a defensible UX moat against legacy ERP competitors
