https://blogs.mobilebytesensei.com/ 2026-09-14 weekly 1.0 https://blogs.mobilebytesensei.com/blog/ 2026-09-14 daily 0.9 https://blogs.mobilebytesensei.com/blog/state-holders-pattern/ 2026-09-14 monthly 0.8 https://blogs.mobilebytesensei.com/posts/state-holders-pattern/hero.png Not every state holder is a ViewModel https://blogs.mobilebytesensei.com/blog/architectural-layering/ 2026-09-13 monthly 0.8 https://blogs.mobilebytesensei.com/posts/architectural-layering/hero.png The UI layer has two halves, and merging them is why screens become untestable https://blogs.mobilebytesensei.com/blog/compositionlocal/ 2026-09-12 monthly 0.8 https://blogs.mobilebytesensei.com/posts/compositionlocal/hero.png CompositionLocal is not dependency injection, and using it that way hurts later https://blogs.mobilebytesensei.com/blog/saving-ui-state/ 2026-09-11 monthly 0.8 https://blogs.mobilebytesensei.com/posts/saving-ui-state/hero.png rememberSaveable survives what remember doesn't — and it isn't a bigger remember https://blogs.mobilebytesensei.com/blog/state-hoisting-pitfalls/ 2026-09-10 monthly 0.8 https://blogs.mobilebytesensei.com/posts/state-hoisting-pitfalls/hero.png Six parameters deep and none of them are used here https://blogs.mobilebytesensei.com/blog/state-hoisting-in-viewmodel/ 2026-09-09 monthly 0.8 https://blogs.mobilebytesensei.com/posts/state-hoisting-in-viewmodel/hero.png The ViewModel is not the default place for state. It's the place for state that outlives the screen. https://blogs.mobilebytesensei.com/blog/state-hoisting-basics/ 2026-09-08 monthly 0.8 https://blogs.mobilebytesensei.com/posts/state-hoisting-basics/hero.png State hoisting is one question: who else needs to know? https://blogs.mobilebytesensei.com/blog/three-phases/ 2026-09-07 monthly 0.8 https://blogs.mobilebytesensei.com/posts/three-phases/hero.png Composition, layout, drawing — and why reading a value in the wrong one costs frames https://blogs.mobilebytesensei.com/blog/side-effects-intro/ 2026-09-06 monthly 0.8 https://blogs.mobilebytesensei.com/posts/side-effects-intro/hero.png Your composable ran four times. So did your network call. https://blogs.mobilebytesensei.com/blog/lifecycle-of-composables/ 2026-09-05 monthly 0.8 https://blogs.mobilebytesensei.com/posts/lifecycle-of-composables/hero.png A composable's lifecycle is three events, and none of them is onDestroy https://blogs.mobilebytesensei.com/blog/recomposition/ 2026-09-04 monthly 0.8 https://blogs.mobilebytesensei.com/posts/recomposition/hero.png Recomposition doesn't re-run your screen. It re-runs the scopes that read what changed. https://blogs.mobilebytesensei.com/blog/first-composable/ 2026-09-03 monthly 0.8 https://blogs.mobilebytesensei.com/posts/first-composable/hero.png What @Composable actually does to your function https://blogs.mobilebytesensei.com/blog/thinking-in-compose/ 2026-09-02 monthly 0.8 https://blogs.mobilebytesensei.com/posts/thinking-in-compose/hero.png Thinking in Compose: you can't reach into the UI any more, and that's the point https://blogs.mobilebytesensei.com/blog/setup-and-bom/ 2026-09-01 monthly 0.8 https://blogs.mobilebytesensei.com/posts/setup-and-bom/hero.png Compose has two version problems, and the BOM only solves one https://blogs.mobilebytesensei.com/blog/adb-install-r-stale-screenshot/ 2026-08-31 monthly 0.8 https://blogs.mobilebytesensei.com/posts/adb-install-r-stale-screenshot/stale-composition.png adb install -r doesn't kill your app, so your screenshot is a lie https://blogs.mobilebytesensei.com/company monthly 0.5 https://blogs.mobilebytesensei.com/contact monthly 0.5 https://blogs.mobilebytesensei.com/privacy yearly 0.3 https://blogs.mobilebytesensei.com/terms yearly 0.3 https://blogs.mobilebytesensei.com/refund yearly 0.3 https://blogs.mobilebytesensei.com/support yearly 0.3