ART Runtime
ANDROID › System
How ART compiles and runs apps: AOT, JIT, profiles, dex, and GC.
Interviewers use ART to probe whether you understand what actually executes your code on a device and why startup and jank behave the way they do. Expect questions connecting AOT/JIT/profile-guided compilation to real performance wins, plus baseline profiles, dex/multidex, and garbage collection basics. Strong answers tie the runtime model to concrete metrics like startup time and frame rendering.
What this covers
- ART vs Dalvik: AOT/hybrid execution model versus pure JIT interpretation
- How AOT, JIT, and profile-guided compilation cooperate after Android 7+
- What baseline and cloud profiles do for cold-start performance
- DEX bytecode, dex2oat, multidex, and the 64K method reference limit
- ART garbage collection basics: concurrent collection and pause behavior
- What 'compiled' vs interpreted vs JITed code means for app speed
Study this topic
- ART Runtime explained: the guided lesson
- 14 practice quiz questions
- 9 revision flashcards
- ART Runtime interview questions and answers