Close the Loop: Designing and Developing Together
summary
Big Nerd Ranch documents a concrete process that ships a working Android login feature: start with discovery, produce an app map and wireframes, create a style guide using shared language (atoms → molecules → organisms), then map those atoms to Android XML (colors, text styles, themes) and build only after design exists. Tools used: Zeplin, Pivotal Tracker, Slack, CI. Rule: never implement user-facing features without design. Design QA and sprint retros catch tweaks; process succeeds if the team really buys in and practices empathy.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:55Problem with collaboration
- 3:40Sample app overview
- 4:43Project kickoff meeting
- 6:47Discovery phase
- 8:53Shared language importance
- 9:55Sprint one overview
- 11:38No user-facing features without design
- 12:20Designer’s workflow in sprint one
- 17:17Reviewing each other’s work
- 19:23Sprint two overview
- 20:07Writing user stories
- 24:20Shared language in code
- 27:32Design QA process
- 28:54Investing in people
- 31:01Being responsive not reactive
- 33:27Closing the loop
related talks
37mCoder Meets Designer: Reconciling Design (...)
30mDesigner–Engineer Workflows in Android App Development
39mDesigners x Developers: Is It a Match 💙 or a Fight 🥊?
36mDesign Develop Deploy!
18mWhy Designers Are so Hard to Work With
25mDesigners + Developers = Best Friends Forever?
56mDevelopment and design: all together like Fuenteovejuna
27mRunning a Design Sprint on Android