Architecture is vital to build an app. But what is that concretely?
summary
Gives concrete takeaways: a timeline from the 1950s to microservices with key years (1979 MVC, 1996 MVP, 2005 MVVM), a simple layered client server → presentation → domain → data example, and explicit Android guidance (Android app architecture from 2017) that marks the domain layer optional and recommends DI. Lists the actual tools to use: ViewModel LiveData DataStore WorkManager and DI via Dagger Hilt, explains how layering prevents a “big bowl of mud,” and uses slides not a live running demo.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:24Why Architecture
- 1:43History of Software Architecture
- 4:00Why do we need Architecture
- 6:36Clientserver architecture
- 7:28Maeuro architecture
- 8:06Layer pattern
- 9:05IEEE 1471 2000
- 10:03MVC
- 12:18App Architecture
- 12:55UI Layer
- 13:14Domain Layer
- 13:34Data Layer
- 14:02App Entry Point
- 14:26App Navigation
- 14:54Dependency Injection
- 15:36Architecture Components
- 15:59Outro
related talks
32mEffective Android Architecture
40mExplaining the App Architecture Guide
31mArchitecture of an Android App
36mModern Architecture of Android Apps — Archetype
47mClean app design with Architecture Components
26mApp Architecture Then and Now: Lessons from the DroidKaigi Conference App History
07mArchitecture: where Science and Art break even
28mDesign Improvements for an Existing App Based on the Guide to App Architecture