Designing Buildable Apps
summary
Concrete rules for making an app maintainable: start with domain objects (nouns and object models) instead of UI-first CTAs, design an intra-app navigation pattern that supports future features, and weigh custom versus standard components with long-term maintenance in mind. Examples include refactoring a 13-year-old Trello mobile app, a renovation anecdote where moving one wall hides plumbing that multiplies effort, and a common cost: designs that turn a 2‑hour task into 20. Practical tools mentioned include Swift, Xcode and Figma; avoid coding too soon.
AI-written summary · about
chapters (6)
- 0:00Welcome and introduction
- 1:45Cross-disciplinary design and building
- 3:33Renovating a 119-year-old house
- 6:40Biggest mistakes in app building
- 10:10Shared understanding in design
- 11:57First conference talk experience
related talks
20mBuilding a Mobile Design System
27m"Design Systems from 0 to 1"
18mHow to Make Your App Look Like You've Hired a Designer
55mFrom Design to Swift: Best Practices in App Development - ROUNDTABLE
36mConsistency is Key - Working with a Design System
53mIndispensable Principles of Crafting Complex Interfaces
38mDesign for Developers
18mWhy Designers Are so Hard to Work With