I have no idea why anyone would give this book 5 stars. I honestly dislike giving poor reviews, but after reading it, and passing the time I could have requested a Kindle refund, I felt it was necessary to assist others thinking about purchasing this book. Here are my complaints about this book, and why you should not purchase it.
1. The Source download for the book does not match the text always, and is cause for great confusion in following the author's steps.
2. The Author leaves out key steps/parts from time to time and someone with little experience would encounter errors when building the project
3. I've read several books and taken college classes on iOS programming, and the author takes a different approach than I'm used to, so I find it hard to follow at times.
4. I wish the sample chapter wasn't just background on iPad, so I could have seen a sample project before purchasing.
5. There is no published Errata for the book online, not even a user forum to discuss the code errors.
6. Some sections in the book do not work, while you build the same project from the downloaded source code, and it builds fine.
7. Not all the code works, but builds OK. For example, in the Dudel project, setting stroke widths, only works on the pencil tool, but no other tool.
8. Not all the downloaded Projects from each Chapter Build, and give compiler errors and warnings. So hard to double check your own work.
9. Memory warnings appear on Downloaded Source and Following book's code.
10. Following the book on the VGA out chapter will not work, but the downloaded source does.
11. In one chapter Author says to delete a XIB file, while the Source Downloaded still has it, and includes a Text file telling you to delete it. Why not just have it read to go?
12. Various Typos: Text says to create FileListViewController.h/.m while book code says FileListController.h/.m
13. Author references Frameworks, but doesn't always tell you to add to project. Some chapters it is mentioned, some not.
This book definitely has not been checked for errors and inconsistencies. I wish others in their reviews alerted me to these fallacies so I would not have purchased this book. What a waste of money.
Hopefully this will help someone else out in the future. If the Author corrects the mistakes and creates a detailed Errata and Forum, I would be happy to change this review. Or, better yet, issue a new revision to correct the mistakes.