Designing for both iOS and Android—the right way
summary
Argues for a platform-first approach with concrete examples from Arc Search and WhatsApp and measurable trade-offs: richer animations, fewer custom components, better built-in accessibility, and faster updates when leaning on iOS and Android SDKs. Shows specific swaps—Arc Search voice search redesign, moving primary actions to a floating button, adapting tab switchers—and gives a three-step workflow: audit + follow Human Interface Guidelines and lean on the SDK so product and engineering time savings feel believable.
AI-written summary · about
chapters (11)
- 0:00Cross-platform design challenges
- 1:42Platform-native apps success
- 3:29Cross-platform design limits
- 7:06Embracing native constraints
- 8:28WhatsApp case study
- 9:13Myths about cross-platform design
- 11:22Native design benefits
- 13:50Arc Search examples
- 16:19Arc Search adaptations
- 18:08Steps to native design
- 19:33Conclusion
related talks
36mKeynote: Android First
27mAndroid First
16mThe Android Experience seen from an iOS dev's perspective
12mDesigning a high quality app with the latest Android features
14mDesigning apps for large screens
48mAndroid 101 for iOS Developers – Two Sides of the Same Coin
44mKeynote - The Future of Android...And How to Prepare For It
44mAn iOS Developer's Guide to Building Android Apps