Mobile app architecture
summary
A 135‑year‑old company (ANWB) chooses a homegrown MVP‑plus variant over trendy frameworks, standardizing five native apps (Swift/Kotlin) used by teams of two maintaining them and aimed at 4.5M members. Architecture uses interface views, presenters, optional navigator and an assembly factory to wire components, dependency injection for test doubles, enum‑based view state, and small mockable verify tests. Result: easier onboarding, gradual refactoring of legacy Objective‑C code, higher unit test coverage, and clearer navigation wiring across iOS and Android.
AI-written summary · about
chapters (11)
- 0:00Introduction to mobile architecture
- 3:23Challenges in app development
- 6:59Introducing MVP Plus pattern
- 10:17Views and presenters explained
- 13:52Assembly as factory pattern
- 17:09Navigation with assemblies
- 21:43Simplifying components
- 23:31State management with enums
- 26:10View models and formatting
- 28:43Cross-app consistency
- 30:05Key takeaways and lessons
related talks
01h 00mMobile App Architecture: How to Conquer the Giant!
37mAdaptable architecture for agencies
31mArchitectural journey
26mApp Architecture Then and Now: Lessons from the DroidKaigi Conference App History
18mArchitecture is vital to build an app. But what is that concretely?
31mArchitecture metamorphosis: a real case study
41mMVI: a Robust and Modern Architecture
47mClean app design with Architecture Components
