Android-apper drar nytte av arkitekturmønstre som separerer ansvar og forbedrer vedlikeholdbarhet og testbarhet — særlig MVVM (Model-View-ViewModel, Googles anbefaling), MVI (Model-View-Intent), og Clean Architecture. Å forstå disse er viktig for å bygge godt strukturerte apper.
MVVM — Model-View-ViewModel (anbefalt)
MVVM separates the UI from logic and data:
VIEW (Activity/Fragment/Compose) → displays UI, observes the ViewModel, forwards events
VIEWMODEL → holds UI state + logic; exposes observable state (LiveData/StateFlow);
survives config changes; NO Android framework/UI dependencies (testable)
MODEL → data (repositories, data sources)
→ The View observes the ViewModel's state and updates reactively. Google's recommended
pattern (using Architecture Components).
