Just another point of view - but I find the SDK documentation to be impressive and a good job.
That said, some methods do look like they were written by a developer and could use some editing from an experienced tech writer. Simple proof reading (i.e., QA for docs) alone would go a long way. There are missing words and misspelled words and even places where paragraphs end in mid sentence. Here's a little example I ran into just now in the package description for android.database.sqlite: "use these classes to maange private databases" (maange is misspelled). Yes it is a silly quibble, but there are lots of those throughout. The art of concise and accurate API docs is something most developers are not born with. For instance, following on with point 7 above, in common speech a "parcel" and a "bundle" are the same thing. The API docs for Parcel and Parcelable are brave descriptions but Bundle's doc is a retreat! That "concise" part is where I differ with some of the other comments in this thread. I don't think examples generally belong in the API docs, with rare exceptions - it should be a reference and not a tutorial. Just my opinion. On Nov 3, 4:09 pm, Greg Donald <gdon...@gmail.com> wrote: > On Tue, Nov 3, 2009 at 5:21 PM, Mark Murphy <mmur...@commonsware.com> wrote: > > Google does not get a "30% take on all our app sales" -- that goes to > > the carriers. > > Ahh.. carriers.. companies who get to charge $36 to put a row in a > customer database. > > -- > Greg Donaldhttp://destiney.com/ -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
