1) What are the four essential states of an activity? Active – if the activity is at the foreground Paused – if the activity is at the background and still visible Stopped – if the activity is not visible and therefore is hidden or obscured by another activity Destroyed – when the activity process is killed or completed terminated 2) What is a visible activity? A visible activity is one that sits behind a foreground dialog. It is actually visible to the user, but not necessarily being in the foreground itself. 3) When is the best time to kill a foreground activity? The foreground activity, being the most important among the other states, is only killed or terminated as a last resort, especially if it is already consuming too much memory. When a memory paging state has been reach by a foreground activity, then it is killed so that the user interface can retain its responsiveness to the user. 4) What are the four essential states of an activity? Ans. Active, Paused, Stopped and Des...
When you say your app works offline… does it really? A surprising number of Android developers proudly add “offline-first” to their app descriptions. And sure, the app opens without internet. Maybe it even loads a few screens. But dig a little deeper and it becomes clear: most offline-first implementations fall apart fast. Why? Because building an offline-first experience isn’t about just storing data locally. It’s about doing it intentionally , with the right structure, cleanup, and flow. And the culprit behind most of the silent issues? Room Database. Not because Room is bad — but because it's misunderstood. Let’s walk through some of the most common mistakes developers make when using Room in offline-first apps — and what to do instead. Mistake 1: Saving the Entire API Response into Room Many devs take the raw JSON response from their API and store it directly into Room entities — every field, every nested object, even things the app never uses. Why it’s a probl...
Last night, I was discussing artificial intelligence with my dad over dinner. He’s not a tech expert. He doesn’t know what ChatGPT is. He doesn’t follow AI news. But what he said stopped me in my tracks: “AI is like when computers came. Everyone thought we’d lose jobs, but more jobs came. You just need to learn new things. Same now.” Simple. Clear. Wise. And he’s absolutely right—because he lived through India’s computer revolution . And what we’re seeing with AI today? It’s history repeating itself. A Flashback to the 90s: The Computer Panic Back then, people were afraid. Clerks, typists, accountants—entire professions feared they’d be replaced by machines. There were protests. Strikes. Resistance. My dad remembers how even in banks and government offices, there was fear that computers would make humans useless. But what happened? Those who resisted got left behind. Those who learned built new careers. And those who adapted transformed India. Entire cities like Bengal...
Comments
Post a Comment