yeah, I have checked that out. As much as I dislike xml, I don't think I want to place my layouts in my code though. From what I have seen, Anko's answer to h

yeah, I have checked that out. As much as I dislike xml, I don't think I want to place my layouts in my code though. From what I have seen, Anko's answer to how to handle buckets is 'just do it by code'. I need to see how it works for very complex layouts. I have written several very complex UIs that I don't think would be expressed easily with Anko. Again, I should really have a try, it seems to bring some niceties that I would have to write custom ViewGroup code to do with the base framework. However my argument had more to do with the Android's API surface area than the UI in particular. How much does having to deal with a pure java API for something like Chromecast (again, insert any android API instead) hampers Kotlin code style ?