I am taking a non-credit class where this book is used as the textbook. I did not have a Kindle at the time but when I saw that is was available on Kindle, I decided to look into that product some more. This book was the catalyst for me getting a Kindle and I simply love the Kindle.
Now, as for the book... I'm a very experienced software engineer (especially in Java) but never did anything with mobile devices or Eclipse. The pace is pretty good but I could do without the author's clever section titles. If it had given some more tips on getting the development environment up and running, I might have been encouraged to use the book without the class.
So, again, this is my first technical book on the Kindle and there are some issues I doubt I would have in the print version. It makes me wonder what kind of a process a book goes through to turn it into a consumable for a Kindle reader. For example:
There are instances where the letter O is used rather than the digit 0 - technical types such as myself are used to such ambiguities in printed material but sometimes the mistakes are inexcusable.
There are some formatting issues with less-than-friendly keywords that OO programming languages are so fond of using. For instance, in a bulleted list of XML attributes which can be used to position widgets in a relative layout, the book lists "android:layout alignParentTop" which should be "android:layout_alignParentTop", "android: layout_align Parent Bottom" which should be "android:layout_alignParentBottom", "android :layout_alignParentLeft" which should be "android:layout_alignParentLeft", etc. The spaces and underscores (or lack thereof) are just as they appear in my Kindle. Not only is the book an unreliable source for the exact name of an attribute but the lack of consistency is very disturbing and frustrating as well. Why is the underscore present in some keywords but not others? It's as if someone didn't give a darn and figured it didn't make a difference as long as they were close with the keywords. When strict adherence is abandoned, the keywords lose their meaning and the reader could completely miss that the author is talking about a keyword.
Some examples presented in a monospace typeface don't appear on the screen well. Sometimes there is a tiny bit of clipping going on that makes the example hard to read on the Kindle.
I suppose I need to try another technical book or two before I reach a judgement about such books on a Kindle. I hope that the technology will improve.
ISBN-13: 978-1430226291
ISBN-10: 1430226293
Why is ISBN important? ISBN 
Scan an ISBN with your phone
Use the Amazon App to scan ISBNs and compare prices.
This bar-code number lets you verify that you're getting exactly the right version or edition of a book. The 13-digit and 10-digit formats both work.
Use the Amazon App to scan ISBNs and compare prices.
Loading your book clubs
There was a problem loading your book clubs. Please try again.
Not in a club? Learn more
Join or create book clubs
Choose books together
Track your books
Bring your club to Amazon Book Clubs, start a new book club and invite your friends to join, or find a club that’s right for you for free.
There is a newer edition of this item:
About the author
Follow authors to get new release updates, plus improved recommendations.
