android-dev

Structure your Android project with clean architecture using the repository pattern for data persistence, implement MVVM with a single state class for simple screens, and use Compose as the recommended UI toolkit with interop for legacy UI.

You should refactor from MVVM to MVI for complex screens requiring robust state management. For simple screens, use MVVM with a single state class, while managing UI state with StateFlow or Compose State.

Set up KMP shared code by using Ktor for network operations and SQLDelight for local storage, ensuring Android-only dependencies are excluded from shared code to maintain platform independence.

Hilt is used for dependency injection in Android projects with KSP annotation processing. For KMP projects, Android-only dependencies like Hilt are not used in shared code, keeping shared modules platform-agnostic.

Manage Gradle best practices by utilizing version catalogs, Kotlin scripts, and implementing baseline profiling to ensure production-grade performance and consistent dependency management across your Android project.

Yes, you can use Kotlin serialization for network models in your KMP project. Ktor handles network operations while Kotlin serialization manages data parsing, ensuring type-safe network communication across platforms.