Ask HN: What's the best SDK documentation you’ve ever read?
1–10 of 51 posts
Re: Ask HN: What's the best SDK documentation you’ve ever read?
#2Re: Ask HN: What's the best SDK documentation you’ve ever read?
#3Re: Ask HN: What's the best SDK documentation you’ve ever read?
#4Re: Ask HN: What's the best SDK documentation you’ve ever read?
#5Re: Ask HN: What's the best SDK documentation you’ve ever read?
#6Why? They are comprehensive, detailed, consistent, systematically presented, clearly explained and professionally written. Microsoft documentation has sadly gone steeply downhill since.
Re: Ask HN: What's the best SDK documentation you’ve ever read?
#7- Very good overview pages.
- Everything is cross-referenced.
- Almost everything comes with an example of how to use it.
- It's a wiki, so you can edit it yourself if you find anything lacking.
Re: Ask HN: What's the best SDK documentation you’ve ever read?
#8Re: Ask HN: What's the best SDK documentation you’ve ever read?
#9I know there are lot of hate for Java but I find Java Doc very complete and helpful.
It's been this way for decades and the presentstion has remained largely consistent the whole time.
Re: Ask HN: What's the best SDK documentation you’ve ever read?
#10The Android SDK is well documented with examples throughout and hyperlinked to examples and posts which explain some content in greater depth.
For example, I remember getting frustrated because of the docs for a setTextSize method, with the helpful description “sets the text size”. Nice. Very helpful that it didn’t mention what unit the parameter was, especially since (after experimentation) it turns out the unit is not the one you would expect for a font size.
The API docs were full of that kind of ‘documentation’, setX: “Sets X”.
If you are writing documentation, please explain what method parameters and return values actually mean, what the units used are. Especially if uses a unit no one expects. For example: font sizes are usually specified in points, if you expect them to be specified in pixels you should absolutely mention that.