J. Rawlings said
Whats with all the complaining about how the api's and device capabilites SHOULD be??? who cares, keep your opinions to forums and blogs, no one wants to read about this who is starting out. Leaves a bad taste in your mouth as soon as you start reading.. asked myself the question, why is this guy even writing about the topic if he's so annoyed with the constraints?! Forget it, too frustrating to make any constructive progress.
Biff said
I have all the iPhone programming books - Apress, PragProg, Hillegas, et al. This is easily the worst of all of them. This is the only iPhone book I wish I hadn't spent money on. Other reviewers have already commented on the disjointed writing and confusing approach this book exhibits so I won't rehash more of the same. The most disappointing thing for me is that O'Reilly used to be my #1 choice for technical books. Never again.
Rice-a-roni - The San Francisco Treat said
I program for a living and this book lives up to the typical O'Reilly high-quality level. I just reached the end of an all nighter, struggling with a problem that this book solved for me in 3 minutes. A reader looking for a "coloring book" style, step by step, how-to book will be disappointed. Serious professionals looking for serious professional guidance will be glad they bought this book. Good work and thanks.
Reggie Burnett said
While this book is not as comprehensive as some have wanted, I found it to be a nice beginners tutorial to writing iPhone applications. The book starts out with an objective-C primer. Since objective-C has such an "interesting" syntax this is badly needed, even though I come from a strong programming background.
Each section includes a reasonably complex sample that puts that section's material to use. Most of the sections also include a "Further Study" area that gives you some homework. This is where the user can expand his knowledge through research and working with the tools.
The book jumps around a bit by first going over simple UI patterns, then spending time talking about audio services and networking, only to come back and spend more time with UI controls, only to jump back into audio/video. Still, one has to remember that this is a reference book and not a novel so jumping around is ok.
The sample applications that I have tried so far are ok and I feel like I have a much better grasp on how the iPhone system works.
This book is not an XCode or Interface Builder tutorial.
Kyle Saunders said
I was fairly new to Mac OS and iPhone development. I had done a little bit of Mac OS development in the past year. This book was exactly what I was looking for in terms of getting more familiar with iPhone development.
The issue of digging under the hood, and not using Interface Builder for everything, was something I wanted. People should know what IB is doing for them. The concept of delegates should not be too confusing to anyone looking to do significant Mac/iPhone development.
Comments