Ask HN: Is it really that hard to iterate in Android Development?

I'm omitting the url to be fair to HN readers, nonetheless this is actually a promoting post to my latest blog entry. If this is unacceptable, feel free to bully me. :)

http://blog.dperini.com/android%20development/2016/10/23/my-approach-to-developing-software-fast-requires-improvements-android-edition

In this post, I am complaining about how hard it is to develop trivial UX in Android using what is enabled by the platform. I tried to share learned experience to be clear about what the existing hassles are. I'd be delighted to listen other people's experiences in this field.

Things that I am having trouble finding solutions are these (partial copy/pasta from the blog):

* A way to reduce amount of work to write new data models. (avoiding reflection is hard)

* A design pattern to express view state without modifying represented data. I don’t want to add view specific bool flags to a model. A state object that wraps the model without modifying it looks dirty but maybe a way to go. It seems dirty when a Fragment needs to persist that state instead of just the data model’s entity object.

* A client generator to be able to benefit from server docs in order to generate client calls (something more lightweight than Swagger and easy to inject into our own HTTP client).

* Much better Intent handling for push notifications and result expecting Activity transitions. Native Android approach looks hideous (or not).

* A way to optimize view count in a RecyclerView cell.

* A way to reduce build times. Multidex looks unavoidable.