Designing Buildable Mobile Apps - iOS App Development
summary
Argues that start with nouns — build an object model (workspace → board → list → card → label) before visual mockups so data, UI and navigation align; recommends planning navigation to scale (cottage/house/apartment/skyscraper metaphors) and mapping modules up front. Shows tradeoffs: use standard/themed components (Craft example) for maintainability, reserve custom only for unique features (Warby Parker AR); warns against wholesale rewrites (keeps Alamofire vs URLSession tradeoffs) and highlights a working migration: replace one view controller at a time to swap React Native for SwiftUI in months, not years.
AI-written summary · about
chapters (8)
- 0:00Introduction and premise
- 5:25Speakers' backgrounds
- 9:59Start with nouns in design
- 21:41Layout complexity in apps
- 30:56Planning for app growth
- 42:02Building thoughtfully
- 43:04Standard vs custom components
- 49:42Best practices and future-proofing
related talks
43mMajor 🔑s to iOS design
55mFrom Design to Swift: Best Practices in App Development - ROUNDTABLE
18mHow to Make Your App Look Like You've Hired a Designer
20mBuilding a Mobile Design System
42mBeyond White: Embracing the iOS Design Aesthetic
17mThe art of React Native: How to make your app stand out
14mDesigning UIs without a UI designer
27m"Design Systems from 0 to 1"