Anko – Pleasant Android development in Kotlin
> XML is parsed on the device wasting CPU time and battery<p>It was my understanding the XML was compiled into a binary format for faster parsing on device, am I wrong on that?<p>EDIT: 
<a href="http://en.wikipedia.org/wiki/Android_application_package" rel="nofollow">http://en.wikipedia.org/wiki/Android_application_package</a> "resources.arsc: a file containing precompiled resources, such as binary XML for example." Ah yes, I think it does.<p>> Most of all, it allows no code reuse.<p>If we are talking code reuse in terms of having one common bit of layout that is used across several different layouts, actually you can: <a href="http://developer.android.com/training/improving-layouts/reusing-layouts.html" rel="nofollow">http://developer.android.com/training/improving-layouts/reus...</a><p>Also, the Android view system as it stands is incredible flexible.<p>You can provide different layouts and style rules for different screensizes and device configs - an kinda equivalent to the webs responsive design using CSS media queries.<p>Also, every view component is just a Java class. As well as allowing you to create your own class from scratch that you can just use as part of a view, you can also extend an existing view class and just change one bit of it's behaviour.<p>I don't especially mean to have a go at Anko - sorry. It's just that I think the Android views are actually pretty good, and certainly when I'm working on Android apps this isn't one of the major problems I have!