Q: how does your documentation (not) suck?

A: take a look at android for the not-not-suck side of the question, in many ways. for example, android seems to be fraught with There's More Than One Way To Do It, and the documentation -- as far as i've seen -- mostly utterly fails to clearly explain and delineate the different routes. consider creating a custom view: when do you have to use an inflater? when can you not? what class name should go into your xml? the custom name, or the android superclass of it? etc.

[blogger: conflicting edits.]