Teams Developing Android/iOS Apps Together — Scrum Practices and Beyond
summary
A mobile engineering team builds a single product in Kotlin (Android) and Swift (iOS) and describes concrete practices: shared design documents between Android and iOS reduced documentation cost and centralized bug/knowledge sharing; a regular “dogfooding scrum” event surfaces ~10–20 UX and accessibility issues per run (loading indicators, VoiceOver, tap target sizes) that are then ticketed and fixed. The workflow combines feature flags, trunk‑based merges, a design system, and pair programming to ship safely at scale (~20M MAU).
AI-written summary · about
chapters (16)
- 0:00Cross-platform mobile dev
- 2:09Mobile app structure at Mercari
- 3:33ICE for experiments
- 5:20Documentation for devs
- 7:30Design docs for Android/iOS
- 9:57Shared design docs benefits
- 11:00Implementation strategies
- 12:47Feature flags and rollouts
- 13:51Scrum events and refinements
- 14:33Dogfooding as scrum event
- 16:16Dogfooding feedback and accessibility
- 18:19Cross-platform dogfooding insights
- 19:43Efficient dogfooding sessions
- 21:27Collaboration practices summary
- 22:29Continuous team process improvement
- 23:32Closing quiz
related talks
20mAgile development application for live ops
41mLearning faster
16mSmall Scale Scrumming
40mAgile Software Development: Practice and Analytics
54mEffective SCRUM in Distributed Teams
19mAgile Playground: The Power of Experimentation
51mDon't Kill Agility with Agile Processes
23mAchieving Both Quality and Development Speed in Toyota’s In-Vehicle Control Software — The Full Practice of Scrum × Test-Driven Development