Adaptable architecture for agencies
summary
A practical agency architecture that fuses Clean Architecture and MVP claims to let a small team ship 2–3 apps per month across short‑lived kiosks and multi‑year products. It uses RxJava, Dagger2, OkHttp and Retrofit plus a repository layer and MVP UI, applying the RxJava cache operator for long requests, a Guava presenter map to survive orientation recreations, and a template skeleton distribution instead of a monolithic JAR. After a year of use the code is cleaner, reuse increases and productivity improves.
AI-written summary · about
chapters (31)
- 0:00Intro
- 1:28Android Framework
- 2:48Web Architecture
- 3:31Key Values
- 4:13Interchangeability
- 5:23Adaptability
- 6:23Unit tested
- 7:24Research
- 7:54Solid Principles
- 10:21Uncle Bob
- 10:32MVP Pattern
- 11:28Clean Architecture
- 12:22Architecture Example
- 13:01Planning
- 13:56Development
- 15:17Dependencies
- 16:04Data Layer
- 17:15Data Sources
- 18:08Repository
- 19:42dargor
- 20:15schema
- 21:36presenter
- 23:36Tsq
- 25:48Common use case
- 27:20ReQuest
- 27:30Landscape mode
- 29:10Rich Java operator
- 29:29Model wrapper
- 30:16Recap
- 30:59Archive vs Template
- 33:56Next talk
related talks
36mModern Architecture of Android Apps — Archetype
33mMobile app architecture
26mApp Architecture Then and Now: Lessons from the DroidKaigi Conference App History
42mArchitecture Round Table
31mArchitecture metamorphosis: a real case study
22mReactive, Clean Architecture and Android Architecture Components, a solid formula for a MVVM based a
42mHands on MvRx: Building Real Apps
18mArchitecture is vital to build an app. But what is that concretely?