Android is Kotlin's flagship platform—Activities, Compose UI, and Gradle with the Android Gradle Plugin. This track stays JVM-focused; full Android requires Android Studio, emulators, and SDK components not available in the playground.
What Android adds
- Activity/Fragment lifecycle or Jetpack Compose UI
- Gradle modules, manifest, resources (
res/) - Coroutines with
Dispatchers.Mainand lifecycle scopes - Networking, Room database, WorkManager—all via libraries
Compared to other UI stacks
Web UI lives in JavaScript frameworks; Android is native JVM with XML or Compose. Server Kotlin overlaps with Java Spring skills.
Important interview questions and answers
- Q: Why Kotlin for Android?
A: Official language, null safety, coroutines, concise UI code with Compose, and Java interop for SDKs. - Q: Can you run Android in this playground?
A: No—needs Android SDK imports and APK packaging; practice locally with Android Studio.
Self-check
- Name one Android UI toolkit (classic or modern).
- What IDE do most Android Kotlin developers use?
Tip: Full Android work needs Android Studio—playground stays JVM main.kt without SDK imports.
Interview prep
- Why not Android in playground?
SDK and Gradle multi-module setup exceed single-file kotlinc sandbox.
- Compose?
Declarative Kotlin UI—learn in Android Studio locally.