Mobile App Architecture: How to Conquer the Giant!
summary
Updated decision tree maps when to pick native (Swift/Kotlin + Xcode/Android Studio), cross‑platform compiled (.NET MAUI/Xamarin, Flutter, React Native), hybrid webview (Ionic/Cordova) or a PWA, based on concrete constraints: offline need, device features, budget and data location. Uses numbers: 71% Android users globally, React Native 42% market share, cross‑platform compiled 28%. Describes a fintech build on an open banking API, a garbage‑collector crash in a cross‑platform beta fixed by reusing objects, and publishing reality: plan for three rejection cycles.
AI-written summary · about
chapters (13)
- 0:00Introduction and overview
- 1:36Defining the project goals
- 3:13Market research and strategy
- 15:51The native development approach
- 21:04Cross-platform development
- 28:10Hybrid and webview options
- 35:51Mobile web strategies
- 39:23Data handling and user interface
- 45:35Security and vulnerability
- 48:13Testing and bug mitigation
- 51:40Publishing and distribution
- 53:24Mobile Architecture Decision Tree
- 55:00Parting advice and conclusion
related talks
01h 04mMobile App Architecture: How to Conquer the Giant!
26mNative Vs Hybrid Vs Cross‑Platform: Dreams and Realities
32mDemystifying Native Mobile Apps Architecture
22mArchitecture First: Foundations for Long Term Success
28mBuilding a Scalable Android Platform
44mRe-Platforming The Path For Betterment
40mGrowing Pains: Scaling and Re-architecting Apps Under Fire
18mSoftware Architecture Building Better Applications with Architecture Best Practices