📰 Dev.to · Hoang Son

Coroutines are how we write async code today. But underneath them — underneath everything in Android — is a 15-year-old threading model that's still running eve

Three mechanisms, three different guarantees. Using the wrong one means either losing state when you shouldn't, or over-engineering when you don't need to. Here

Week 1 of my 100-day Senior Android series is done. Here's what I covered, what actually surprised me, and the one question I couldn't answer confidently until

Application, Activity, Service — three types of Context, each with different lifetimes. Using the wrong one is one of the most common sources of memory leaks in

Tasks and back stacks are how Android manages your navigation history at the OS level. Understanding them explains bugs that feel impossible to reproduce — and

Fragment has TWO separate lifecycles: the Fragment itself and its View. Mixing them up is one of the most common sources of memory leaks and crashes in Android

onCreate, onStart, onResume... you know the callbacks. But there are 3 real-world scenarios that the standard diagram never shows — and they're exactly what sen

Activity, Service, BroadcastReceiver, ContentProvider. You've used them for years. But do you know *when not* to use each one? The answer reveals a lot about se

I've shipped Android apps used by millions. So why am I going back to basics? Here's the honest answer — and what I'll share over the next 100 days.

Hey there, design warriors and code slingers! Ever feel like you're trapped in a never-ending loop of...

Chào mọi người, Hôm nay, tôi sẽ kể cho bạn nghe một câu chuyện có thật về việc tôi xây dựng một thư...