Android: practice, test and prove it

Android lifecycle, fragments, intents, permissions, RecyclerView, ViewModel, Room, Gradle and Compose.

FreeNo sign-up to testNo attempts yet

Start the android test Read the first lesson

Android screenings focus on how the system treats your app, not on memorising APIs. Expect questions about what happens on rotation, where to keep data so it survives, how to ask for a permission, why a list scrolls badly, or why a database call crashes on the main thread. Newer tests add a few Jetpack Compose questions about state and recomposition.

This page lets you practise those scenarios in Kotlin. The lessons explain the lifecycle and the architecture pieces most interviews ask about.

Benchmark: The pass mark is 80%, and this skill is commonly screened for Android developer, mobile developer and junior app support roles. Requirements vary by employer.

Lessons

Activity lifecycle, intents and ViewModelKnow what the system does to your screens, how screens open each other, and where to keep data so it survives.Lesson 1

RecyclerView, Room, Gradle and Compose basicsBuild efficient lists, store data with Room off the main thread, add libraries with Gradle and handle Compose state.Lesson 2

Fragments, the Navigation component and passing argumentsManage fragment view lifecycle correctly, move between screens with NavController, and pass data without crashes.Lesson 3

Runtime permissions, background threads and network callsAsk for permissions the right way at the right moment, and keep slow work off the main thread with coroutines.Lesson 4

Interview prep

Android interview questionsQuestions commonly asked to check whether you understand how Android manages screens, threads and data.6 questions

Certificate

Free with an accountA PDF with your name, best score and date. Records this site's tests only.

Common questions

Are the questions in Kotlin or Java?

Code samples use Kotlin, which is the preferred language for new Android work. The concepts, such as the lifecycle and threading rules, are the same in Java.

Do I need Compose or XML layouts?

Both appear in real jobs. Most questions cover concepts shared by both, and a few check basic Compose state handling.

Do I need to know a dependency injection library?

Not for this test. Knowing why ViewModel and Room are separated from the screen matters more than any specific library.

Android test for interviewWhat the screening round looks like, with a 5-question sample.