Ah, there's the winning question. Thanks for asking.

Developers should not be under any obligation to provide *any* documentation towards their materials. This idea - as presented - provides a means for any developer to attain some level of documentation, in a common area, attached to their application, and in a common enough format that they can have a side of their testing/project team dedicated to keeping that updated.

For those developers who'd love documentation help until their UIs become totally intuitive, this is a win for them.

That being said, if they want to provide it in any other fashion, the key point of keeping it updated and available on the device remains. Without up-to-date documentation, then providing it is worthless to the user - and possibly to the developer as well if they choose at some point to no longer handle maintenance of that application/service.