Angelina Andronova·Aug 6Two things called “State”: how mutableStateOf and StateFlow really work underneathYou have two imports open. Both types have a .value. Both are “observable.” Both hold a single piece of state that something else reacts…
Angelina Andronova·Aug 2Surviving process death: Android vs KMP vs FlutterEvery mobile OS will eventually kill your app to reclaim memory — silently, with no warning. Three frameworks, three very different answers…
InProAndroidDevbyAngelina Andronova·Jul 26How Many Trees Does Your Framework Need?Android Native vs KMP vs Flutter — a series comparing how the three mobile stacks solve the same problems differently. Part 4: the data…
Angelina Andronova·Jul 22One Tap, Three Threads: Where Does the Work Actually Run?Tap a button, and somewhere behind that tap, real work has to happen — parse a file, decode an image, chew through some data. Do that work…
Angelina Andronova·Jul 18The Compose Clinic: Three Symptoms, One PatientThree developers walk into the clinic.
Angelina Andronova·Jul 17One Badge, Three Deliveries: How Android, Flutter, and Compose Keep Your UI in SyncAndroid Native vs Flutter vs KMP — a series comparing how the three mobile stacks solve the same problems differently. Part 2: state…
Angelina Andronova·Jul 16Compose Doesn’t Redraw Everything — Here’s Who DecidesDrag a slider in a Compose app and watch it track your finger perfectly, 60 times a second. Every fiber of your instinct says this should…
InProAndroidDevbyAngelina Andronova·Jul 16One Tap, Three Machines: How Android Views, Flutter, and Compose Actually Render Your UIAndroid Native vs Flutter vs KMP — a series comparing how the three mobile stacks solve the same problems differently. Part 1: rendering…A response icon1A response icon1