android-code-review

Android code review identifies critical and high-priority issues in Kotlin sources across Activities, Fragments, ViewModels, UseCases, and Repositories. It enforces naming conventions, detects memory leaks, validates UI state patterns, and ensures business logic placement aligns with MVVM architecture compliance.

Memory leaks in Android stem from improper Scope usage, lifecycle issues, and incorrect reference handling. Code review detects these patterns and proposes fixes by identifying where lifecycle-aware components should replace static references and where scope boundaries need enforcement.

In MVVM, UseCases contain business logic implementation while ViewModels orchestrate and delegate. Code review ensures business logic doesn't leak into ViewModels or UI layers, validates sealed class UI state patterns, and confirms proper separation of concerns across architectural layers.

Android code enforces PascalCase for types and classes, camelCase for variables and functions, and descriptive names across all identifiers. Code review validates these patterns alongside lifecycle method naming and state variable clarity in MVVM and MVI implementations.

Code review applies to both Kotlin and Java Android files. It handles all standard Android components—Activities, Fragments, ViewModels, UseCases, Repositories—regardless of language, applying consistent architectural and naming standards across mixed codebases.

Code review works on PR diffs for focused change analysis or full module audits for comprehensive architectural validation. Both approaches detect the same critical issues—naming violations, memory leaks, UIState misuse, and incorrect logic placement—with scope adapted to input granularity.