android-development

Build Android applications following Google's official architecture guidance, as demonstrated in the NowInAndroid reference app. Creating a new project? → Read modularization.md for project structure → Use templates in assets/templates/ Adding a new feature? → Create feature module with api and impl submodules → Follow patterns in architecture.md Building UI screens? → Read compose-patterns.md → Create Screen + ViewModel + UiState Setting up data layer? → Read data layer section in architecture.md → Create Repository + DataSource + DAO Use convention plugins in build-logic/ for consistent configuration: See gradle-setup.md for complete build configuration. - Offline-first : Local database is source of truth, sync with remote - Unidirectional data flow : Events flow down, data flows up - Reactive streams : Use Kotlin Flow for all data exposure - Modular by feature : Each feature is self-contained with clear boundaries - Testable by design : Use interfaces and test doubles, no mocking libraries - Create feature:myfeature:api module with navigation key - Create feature:myfeature:impl module with: - MyFeatureScreen.kt - Composable UI - MyFeatureViewModel.kt - State holder - MyFeatureUiState.kt - Sealed interface for states - MyFeatureNavigation.kt - Navigation setup - MyFeatureModule.kt - Hilt DI module - AndroidApplicationConventionPlugin - App modules -...