Jetpack Compose is absolutely amazing. It has a great community (kotlinlang slack - compose channel), a huge power behind it and there already is quite a number of very decent tutorials on it.
On one hand one may argue that XMLs are simpler. I would say that this is pretty much never the case - they are more familiar. Jetpack Compose seems to be successor of Android (at least1) UI development, so students may find it very motivating that they are being taught the new thing that may as well be the norm in the future. While some of the concerns regarding usefulness of teaching (potentially) outdated tools are inherently wrong, one must remember that students' motivation plays a big role in courses.
Additionally, there is an advantage to Compose that cannot be overlooked - it uses Kotlin. The very language used for expressing parts of the system (mobile application) matters. A lot. So now, instead of learning Kotlin, learning XML and learning how to bind the two, students can... simply learn Kotlin. Yes, they need to learn which functions to invoke in Compose, but they would've had to do it with XML too. Just with tags, not functions.
It would seem like Compose is the clear winner here, but (in my opinion - unfortunately) it is not the case. Compose is a very young framework. Its adaptation will take a long time and, if your goal is to prepare your students for being able to work with mobile development as soon as possible, learning XML will be way more beneficial to them.
If it was up to me, I wouldn't focus on aiming to make the students employable as quickly as possible. I would show them things that are more powerful, simpler, more elegant and easier to integrate. I would show them Compose.
1I say at least, because I have been using Compose for things like Desktop development too. It's a little lacking there, but apart from it being a little incomplete (makes sense, since it's a fairly young framework), it is the best GUI library I have ever touched.