android-kotlin-advisor

Android Kotlin Advisor

1. Choix d'architecture

Contexte	Pattern recommandé
App simple, 1–3 écrans	MVVM + Repository (StateFlow)
App Compose multi-écrans	MVI (état immuable, sealed class UiState)
Large équipe / multi-feature	Clean Architecture + multi-module Gradle

Structure recommandée multi-module :

app/
feature/home/
feature/profile/
core/data/
core/domain/
core/ui/
build-logic/               ← convention plugins partagés

2. UI avec Jetpack Compose

Toujours préférer les composables stateless (state hoisting) :

// BON : state hissé, composable testable et réutilisable
@Composable
fun LoginForm(
    state: LoginUiState,
    onEmailChange: (String) -> Unit,
    onSubmit: () -> Unit,
) { ... }

// MAUVAIS : état caché dans le composable, non testable
@Composable
fun LoginForm() {
    var email by remember { mutableStateOf("") }
    ...
}

Checklist Compose :

• Material 3 BOM : implementation(platform("androidx.compose:compose-bom:2025.05.00"))
• Dynamic Color (Android 12+) : dynamicLightColorScheme(context)
• Navigation : NavHost + NavController, arguments typés via NavType
• Éviter LocalContext.current profondément imbriqué → passer en paramètre

3. State management

// ViewModel pattern recommandé
@HiltViewModel
class HomeViewModel @Inject constructor(
    private val repo: PostRepository
) : ViewModel() {

    private val _uiState = MutableStateFlow<HomeUiState>(HomeUiState.Loading)
    val uiState: StateFlow<HomeUiState> = _uiState.asStateFlow()

    init { loadPosts() }

    private fun loadPosts() = viewModelScope.launch {
        repo.getPosts()
            .catch { _uiState.value = HomeUiState.Error(it.message) }
            .collect { _uiState.value = HomeUiState.Success(it) }
    }
}

sealed class HomeUiState {
    object Loading : HomeUiState()
    data class Success(val posts: List<Post>) : HomeUiState()
    data class Error(val msg: String?) : HomeUiState()
}