Building a Mobile Design System
summary
Builds a mobile design system for QuickBooks Self‑Employed over 1.5 years, starting from concrete choices: fonts and colors enums plus asset catalogs, UIKit-based reusable views, and a named custom ActionButton API that switches styles for save/delete. Mentions Epoxy as an Android example, reports deleting lots of unused components, and emphasizes two outcomes: faster feature shipping and tighter designer‑engineer workflow, with the caution to avoid over‑componentizing when it’s unnecessary.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:52What is a Design System
- 3:15Who Does This Benefit
- 4:45Where Is This Applicable
- 5:52Getting Started
- 7:19Basic Building Blocks
- 8:01Custom Fonts and Colors
- 9:49Custom UI Components
- 13:59Epoxy
- 15:45Keeping everyone on the same page
- 17:22Lessons learned
related talks
26mHow we engineered our design system
51mDesigning Buildable Mobile Apps - iOS App Development
27m"Design Systems from 0 to 1"
15mDesigning Buildable Apps
36mConsistency is Key - Working with a Design System
20mDesign Systems for the Rest of Us
37mLet your design evolve, adopt a Design System!
55mFrom Design to Swift: Best Practices in App Development - ROUNDTABLE