automotive-architecture

Structure an Android Automotive OS MVVM application by separating UI rendering using Template-based Screens, managing state with ViewModels, and isolating data access through repositories and data sources. This approach maintains clear boundaries between car UI and business logic.

Use Hilt in an AAOS app to inject dependencies into CarAppService, Session, and ViewModel components. This provides lifecycle-aware state handling and ensures screens remain focused on UI rendering while business logic stays separated into maintainable layers.

Fragments are prohibited for UI rendering in Android Automotive OS applications. You must use Template-based Screens within a Session to render UI, ensuring screens remain focused solely on UI rendering while ViewModels handle state management.

Share state between multiple car screens in an AAOS application using shared ViewModel communication patterns. This lifecycle-aware approach allows multiple Template-based Screens to access and observe business logic and data from a common ViewModel.

Android Automotive OS development requires structured lifecycle management for CarAppService and Session components. Proper lifecycle handling ensures ViewModels manage state correctly and dependencies injected via Hilt behave predictably across screen transitions.

The best way to separate data access in an AAOS app is to implement repository and data source layers beneath the ViewModel. This ensures ViewModels handle state management while repositories abstract data operations away from the UI.