Smaller not taller: defeating the mobile app architecture giant
summary
Argues that most projects don’t need a native app and claims the 60% rule: a responsive site suffices. Compares stacks with specifics: iOS via Swift/Xcode, Android via Java/Kotlin, compiled cross-platform (Xamarin, React Native) and hybrid (Ionic/PhoneGap), plus Firebase/SQLite for sync. Describes a real failure: a Xamarin build crashes from a cross-platform garbage-collector conflict that delays shipping, so the team chooses native duplication for reliability. Recommends tests, device QA and planning for up to three store rejections.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker intro
- 2:19Define your desired app result
- 9:18Picking your tech stack
- 16:26Cross-platform compiled approach
- 21:07Hybrid webview development
- 25:51Mobile web and responsive design
- 28:21Handling data in mobile apps
- 30:50Where to place business logic
- 34:45Security considerations for mobile
- 37:14Testing and QA best practices
- 39:24Memory management pitfalls
- 43:40Publishing and app store process
- 47:10Decision tree and final advice
- 53:29Summary and quote
- 54:12Q&A session
related talks
48mMobile App Architecture How to Conquer the Giant!
34mMobile Development, what’s wrong with you?
11mMobile development in 2019: native versus cross-platform
46mCross-Platform Mobile Development vs. Native
01h 00mChoosing The Best Mobile Framework
41mCross-Platform Fireside Chat
54mSucceeding with Xamarin
40mChoosing The Best Mobile Framework