Anko is the same version through xml, only in another format, where you write in the descriptive language, here in the form of a code, the result is the same and equal opportunities.You can continue to use the classic for Android xml-verst and in writing on Kotlin, Anko is just an alternative tool, not an obligatory condition for UI on Kotlin. I personally believe that UI should be in the descriptive language (XML). First, it shares the business logic and design of the individual. Then the xml-page can be pre-evaluated in a visual editor, and there are all viewing attributes in the form of a table and working with it much more comfortable than the code.As far as you're right, you're doing the same thing in the xml cross, just write in another format, that's the right thing.For binding, there's this official binding support in XML: https://developer.android.com/topic/libraries/data-binding/index.html the instrument is more powerful than Anko, although I honestly didn't deal with Anko, I don't like it.