Major 🔑s to iOS design
summary
Promised takeaway: start with actual API responses and real photos not lorem ipsum, sketch on paper, then prototype on-device to reveal cramped text and cut names. Tools mentioned: Sketch and Craft for injecting JSON, Google Forms to collect test data, export 1x/2x/3x assets or use PDFs/vectors. Case studies compare airline and fitness apps to show when custom controls help and when they confuse. Build an ugly, data‑filled prototype quickly and measure whether the interaction actually works.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:21Do you have to have a "beautiful" app with intuitive UI for it to be successful?
- 3:53Start with real data
- 8:47Put it on a phone
- 10:12Don't reinvent the wheel
- 11:31Know the ingredients
- 13:48What about custom actions?
- 26:54Beating Design Block
- 27:04Murder your darlings
- 30:01Make something ugly
- 30:46Leveling up
- 36:28Study the masters
- 38:15Questions?
related talks
42mBeyond White: Embracing the iOS Design Aesthetic
51mDesigning Buildable Mobile Apps - iOS App Development
45mDesign Tools and Handoffs*
22mDesigned. an introduction to design for developers
49mDesign Tools - Closing the Gap Between Design and Development
40mTen Pro Tips for Prototyping
40mThink Like a Designer
41mA look at modern protoyping: Sketch, Pixate and more
