Optimization of mobile development strategy for maximum business impact
summary
Decision criteria are: concrete claims, measurable outcomes, and tools used. Slides show 1.2–1.5x per-developer gain from process fixes, then a customer case moving to Flutter that reports 3.35→4.65→5.45 overall gain as platforms expand (mobile→web). Evaluation uses three pillars: business requirements, user experience, technology dependencies. Also lists options (native iOS/Android, Flutter, React Native, Kotlin Multiplatform, PWA, Unity) and mentions AI for codegen and testing but without quantified results.
AI-written summary · about
chapters (10)
- 0:00Mobile dev strategies intro
- 1:27Who this talk is for and why
- 3:59Business impact defined
- 5:06Tech vs business goals
- 8:43Dev approaches trade-offs
- 12:21Improving existing strategies
- 16:48Choosing tech three methods
- 19:45Multi-platform expansion
- 21:54AI for dev optimization
- 23:42Key takeaways
related talks
11mMobile development in 2019: native versus cross-platform
40mChoosing The Best Mobile Framework
18mCross-Platform Development as a Native Mobile Developer
33mShould We Flutter?
01h 00mChoosing The Best Mobile Framework
45mFlutter: A journey of productivity and happiness
44mAchieving next-level code between Flutter and the Mobile Web
41mFlutter at Scale: A Roadmap for the Modern Enterprise