AAD certification — Jetpack Compose vs. XML layouts on the actual exam?
I'm preparing for the Associate Android Developer certification and I'm trying to figure out how much time to spend on Jetpack Compose vs. traditional XML layouts. My current role uses XML almost exclusively, so I'm comfortable there, but from what I've read the exam has been shifting toward Compose. I've got about 6 weeks to prep and I'm studying 1–2 hours a day after work, which isn't a huge amount of time to get Compose up to speed if it's heavily weighted.
My practice test scores are around 70–74% on the Google-provided materials. The areas where I'm consistently dropping points are UI state management, the ViewModel/LiveData vs. StateFlow distinction, and anything touching the navigation component with deep links. I've been building Android apps for about 3 years but mostly on the feature side — I haven't spent much time with testing, which I understand is a notable portion of the exam.
If you've taken the AAD recently, how would you break down the Compose vs. XML split in what you actually encountered? And how heavily was unit testing with JUnit vs. UI testing with Espresso represented? I want to make sure I'm not spending 70% of my remaining time on something that's only 20% of the exam.
I spent 4 weeks exclusively on Compose after failing my first attempt with 66%. The second time I passed with 77%. The state management model — especially unidirectional data flow and the difference between remember and rememberSaveable — is something you need to be solid on, not just vaguely familiar with.
Room database and coroutines integration showed up more than I expected. I'd set aside at least 4–5 study sessions for async data handling with Kotlin coroutines in the context of Android architecture. That stuff crosses over into multiple question areas.
The navigation component with Compose Nav was on my exam and it catches people off guard. Make sure you understand how to pass arguments between destinations and handle the back stack — those specifics came up in at least 3–4 questions.
Took it 4 months ago and passed with 83%. The exam I saw was probably 60–65% Compose at this point. If you're XML-primary, I'd genuinely dedicate most of your remaining prep time to getting comfortable with Composables, state hoisting, and recomposition basics.
Testing was about 20% of my exam — split roughly evenly between unit tests and UI tests. Espresso basics are enough; you don't need to be an expert.
Just passed last month so this is fresh. Honestly the exam had more Compose than I expected, but it wasn't so deep that you needed to know every API cold. What actually helped me was making sure my Kotlin fundamentals were solid first, because both Compose and XML questions tripped me up when I wasn't confident in the language itself. I did a bunch of practice on aad aad kotlin programming fundamentals and it filled gaps I didn't even know I had.
For the Compose vs XML question specifically, I'd say don't abandon XML study. You'll see both. The Compose questions I hit were mostly around state management and remember/mutableStateOf, so if you can nail those concepts you're fine without knowing every composable by heart. Spend maybe 60/40 in favor of Compose if you're starting fresh, but since you're already comfortable with XML you're in better shape than you think.