 |
|
|
| Customer Review: |
|
1: This should be your SECOND iPhone programming book !
Erica Sadun is known for her iPhone reengineering since the beginning of (iPhone) time. This book sums up her experiences with iPhone programming, starting from the toolchain times. She shows a lot of tricks you won't see in the standard books. But to really enjoy this book, you should know iPhone programming at least basically. This is NOT a methodical introduction for complete beginners, but a collection of iPhone programming concepts and gems for people who already understand the basics. So, if you buy this book to LEARN iPhone programming, you will certainly be disappointed. But if you buy this book to IMPROVE your iPhone programming skills, you will really like this book a lot.
|
2: Erica Sadun's aptitude makes this a MUST buy!
Erica Sadun's inherit capability to write beautiful and self-explanatory code is evident in the iPhone Developer's Cookbook. These aren't the same cookie-cutter examples you have come to expect from most sample applications out there. This text contains examples for applications which the real world has come to expect out of iPhone developers. Erica pushes the limits of the developer API and it shows that her expertise on the subject is nothing short of a virtuoso. This makes for excellent reference material to keep by your side while developing iPhone applications!
|
3: Solid Recipes
The author provides plenty of solid recipes to help the new iPhone developer get their application vision together. The only reason why I hold back the fifth star, is that I wish the book had a bit more for the advanced iPhone developer. More meat about using Core Animation or SQLite would have been nice.
|
4: Must have
Excellent book with many sample code. I hope the author prepares a newer edition with more recipes.
|
5: Impractical - not the right way to get your feet wet with the iPhone
One change in the way this book is written would make a world of difference:
Use the classes and views in the way that they are supposed to.
Putting every line of code in the main goes against the very grain of the programming model and makes the reader waste a LOT of time in trying to adapt the examples in the book to anything that could be created in real life.
Object Oriented programming is not new, I have seen many books resolve the issue of displaying classes before.
On top of being unable to draw any use from this book, I feel cheated by the author and I feel like the only reason why she wrote it this way is to be able to send the book to print quickly and cash in on all the fools like me who are trying to learn how to program the iPhone early on.
|
|
|
