[jondwillis]

What would you like "us" to focus on? As for MVP variations and RxJava, those are useful tools. MVP variations are often for organization and writing more modular, testable code. RxJava and other Rx implementations are useful for describing data flows and transformations while also making complicated asynchronous problems more manageable.

[Nandi]

MVP & Rx are good, no doubt. But there are a crazy amount of Pundits preaching different variations and thanks to the internet an early developer/beginner is confused. I have spent several hours helping others rectify basic mistakes. There should be some serious and well-documented approaches to achieve something (a performant app in this case). Decay is also important. As frameworks mature and android itself moves ahead, old documentation or answers which no longer have relevance should be purged. Android documentation itself boasts old sample codes, while the framework has deprecated some of them. The problem which OEMs faced are being resolved now, but the reality is it will take another year or two for it to come live. In 2013 Huawei had come up with its own extension to segregate its own modification with vendor and base; very sure that's not getting removed at least in the next 1 year.