Android Engineer & Kotlin Advocate. 🚀 Deep dives into Jetpack Compose, Coroutines, and Clean Architecture. Turning complex code into scalable solutions. 🛠️✨
Build for Everyone · Part 5 of 5 Previously: Parts 1 to 4 made screens readable, operable, testable, and alive for assistive technology. This final part is about a different kind of inclusion: the hun
Build for Everyone · Part 4 of 5 Previously: Parts 1 to 3 made static screens accessible and kept them that way with tests. This part is about everything that happens after the screen first appears.
Build for Everyone · Part 3 of 5 Previously: Part 1 (“Raising the Floor”) set the baseline rules, and Part 2 (“From Five Stars to One Sentence”) built a custom rating control with real semantics. This
Build for Everyone · Part 2 of 5 Previously: Part 1 (“Raising the Floor”) covered the five baseline rules every screen must pass. Those rules assume standard components. This part is about the ones yo
Build for Everyone · Part 1 of 5 TL;DR Accessibility doesn’t start with exotic APIs. It starts with five properties every screen must have: meaningful labels, 48dp touch targets, readable contrast, m
Every Compose codebase eventually grows the same awkward corner: a composable that needs one heavyweight object, a search session, a player wrapper, a debounced event pipeline, and that object has to
fold() and reduce() look like twins. Both walk a collection, both hand you an acc and the next element, and both collapse everything into one value. Most developers pick whichever name comes to mind f
Picture a Friday afternoon. The debug build of your app is flawless. You cut a release, and within an hour crash reports arrive: a ClassNotFoundException for a payment plugin that definitely exists in
You wrap a network call in withContext(Dispatchers.IO) inside a flow { }, run the screen, and the app dies with IllegalStateException: Flow invariant is violated. Nothing in the stack trace points at
