The Android Handbook uses realistic interview questions as a structure for learning how experienced Android engineers reason.

The interview is the entry point, not the destination. Each page answers the question first, then explains why the concept exists, the mental model worth remembering, the production trade-offs that matter, and what stronger engineering judgement looks like in practice.

Our mission

The goal is to help developers build knowledge they can use both in interviews and on real Android teams. Rather than memorising APIs or isolated answers, the handbook focuses on ownership, lifetimes, boundaries, state, failure modes, trade-offs, and the design decisions behind the platform.

Teach the reasoning, not just the mechanism.

The handbook begins with Android fundamentals and grows into Kotlin, coroutines and Flow, Jetpack Compose, architecture, networking, persistence, testing, performance, security, background work, system design, and other areas Android engineers are expected to reason about.

Question groups

• Android Fundamentals — build the mental model behind Android's application model and core components.

More sections will appear as reviewed material is published.

How to use the handbook

Start with the interview-ready answer and try to explain it aloud in your own words. Then use the rest of the page to understand the problem behind the API, the production implications, and the follow-up questions an interviewer may use to test deeper understanding.

You do not need to read everything in one pass. Use the handbook to prepare for interviews, strengthen weak areas, or return later when you need to refresh a mental model.