Getting Real: How We Make Basecamp for Android
summary
Basecamp Android team uses a team of three working in six-week cycles and aims to ship updates twice a month. They build rough sketches into runnable features in days: stock Android components, frequent commits—often check in code every 20 minutes—plus a new image viewer and QA write-ups. They implemented notification bundling and richer previews in about a week, presented it to all 55 employees, and report that the change works and reduced context switching.
AI-written summary · about
chapters (6)
- 0:00Start
- 13:29Kickoff
- 27:11Context Switching
- 35:02Technical Constraints Informing the Design
- 35:51Adding a Confirmation Dialog When You Mark all Notifications Is Red
- 42:21Getting Qa Involved
related talks
36mDesign Develop Deploy!
27mRunning a Design Sprint on Android
40mThink Like a Designer
32mA Designer’s Challenge: Trying Android Engineering
37mBuild your app for success
18mWhy Designers Are so Hard to Work With
25mGetting started on Android UI design hub
34mDesign System Driven Android Development: A Guide to Automation Tools