OKOuday Khaledinexpert-android-playbook.hashnode.dev·Apr 21 · 18 min readThe Strict-MVI Playbook: How Staff Android Engineers Structure Jetpack Compose at ScaleA strict-MVI feature exposes exactly one public entry point, send(intent), and one observable output, StateFlow<State>. Everything else — reducer, middlewares, channels, cancellation keys — is an implementation detail negotiated behind that contract....00
OKOuday Khaledinexpert-android-playbook.hashnode.dev·Apr 21 · 8 min read10 MVI Anti-Patterns Senior Android Reviewers Reject on SightStrict MVI on Android fails in the same ten ways in every codebase. This article is the pocket cheat sheet senior reviewers keep open during a pull-request pass. Each entry is a smell, a bad snippet, a good snippet, and one sentence explaining why it...00
OKOuday Khaledinexpert-android-playbook.hashnode.dev·Apr 21 · 8 min readThe Android Testing Pyramid That Strict MVI Unlocks80% of your presentation tests live in the reducer tier and run in 5ms. The other four tiers exist, but they are narrow on purpose — device-bound work is the rarest thing the pyramid measures. Strict MVI is what makes that shape possible in the first...00
OKOuday Khaledinexpert-android-playbook.hashnode.dev·Apr 21 · 8 min readPure Reducers in Kotlin: Why Your Android Unit Tests Should Run in 5 MillisecondsReducer unit tests clear in about five milliseconds each, with no dispatcher setup, no MockK, no Turbine, and no ViewModel. That speed is not a micro-optimization — it reshapes the test pyramid, moves 80% of Android presentation tests to pure JUnit, ...00
