📱 Android Interview Preparation — Strengthening Android Fundamentals

As part of my ongoing Senior Android interview preparation, I’ve been revisiting core Android concepts — focusing not just on memorizing definitions, but on understanding how things work, why they exist, and what trade-offs they have.

Here’s what I’ve been revisiting:

🔹 Activity & Fragment Lifecycle
Activity lifecycle — onCreate → onDestroy
Fragment lifecycle vs View lifecycle
viewLifecycleOwner
Configuration changes & Activity recreation
Process death & state restoration

🔹 Architecture & Presentation
MVC vs MVP vs MVVM vs MVI
Clean Architecture — Presentation, Domain, Data
Repository pattern
ViewModelStore
ViewModelStoreOwner
ViewModelProvider
ViewModel across configuration changes

🔹 Lifecycle & State
LifecycleOwner
LiveData & MutableLiveData
MediatorLiveData
observe() vs observeForever()
setValue() vs postValue()
Multiple updates & value coalescing
StateFlow vs SharedFlow
Hot vs Cold Flow
State vs Events

🔹 Background Processing & Concurrency
Main/UI thread
Threads
Handler & Looper
Message/Runnable queue
ANR
Android background execution limits
WorkManager
One-time vs Periodic Work
WorkManager constraints
WorkManager vs Foreground Service

🔹 Navigation & Android Core
NavGraph
NavController
NavHost
Safe Args
Navigation back stack
popUpTo() & inclusive
Cold vs Warm vs Hot app start
Android App Bundle (AAB)
Explicit vs Implicit Intents
Passing data between Activities
The real difference in senior-level interviews?
It's not just knowing the API.
It's being able to explain:
👉 Why does this component exist?
👉 How does it behave internally?
👉 What happens during configuration changes or process death?
👉 What are the alternatives?

I'm continuing to revise, practice explaining concepts, and connect the theory with real Android development.
Learn → Implement → Question Trade-offs → Explain Simply → Revisit

#Android #AndroidDevelopment #Kotlin #Jetpack #AndroidInterview #MVVM #CleanArchitecture #StateFlow #LiveData #Learning #SeniorAndroidDeveloper