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...
Building scalable Android apps requires clean architecture—and one of the best ways to manage your UI and logic is by combining MVVM with Jetpack Compose . However, API calls can get messy when not structured properly. In this post, I’ll show you how to build a reusable, clean API call structure using MVVM that works for any screen in your app. We'll use: ViewModel to manage UI-related data Repository for business logic and network State management using mutableStateOf Retrofit for networking This is not tied to any specific screen (like sliders, onboarding, etc.)—you can plug in your own model and API. Why a Reusable Pattern? Apps often repeat the same logic: Show loader Fetch data Handle errors Update UI Instead of repeating it everywhere, we'll abstract it once and just extend or plug in what’s needed per screen. 1. Define a Generic API Result Wrapper This wrapper lets us handle success, loading, and error states in a consisten...
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