Navigating the MV* Mess
summary
Argues that ATAM/ARID validate high-level architecture but teams lack low-level validation, and recommends lightweight intermediate architectural reviews that run ATAM steps at module level. Uses a utility tree to turn six quality attributes into prioritized scenarios (example: minimize main-thread IO is low effort high impact), and lists concrete techniques: offline support + data sync + client caching for availability, Android App Bundles for subset deployability, and ML‑filtered logging to stop sensitive data leaks.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:28How Did the Journey Started for You
- 11:14Usability
- 16:12App Security
- 19:44Quality Attributes
- 25:23The Atm Life Cycle
- 28:48Functional View
- 29:06Code View
- 29:18Development View
- 45:55Evaluate Partial Architectures
- 48:29Model View Presenter
- 50:06Model View Intent
- 50:51How Do You Pick a Pattern
related talks
31mArchitectural journey
32mEffective Android Architecture
44mAI Architecture Thinking: From Idea to Impact
42mIngredients for a healthy codebase (en)
38mAgile Architecture
33mFrom Enterprise Architecture to Software Design - Critical Thinking
31mPatterns for Safe Refactoring of Android Apps
57mSoftware Architecture: The Hard Parts