Okay.. I'm not even sure where to start. So, I'll start where the author does in chapter 2. At random points. And I will switch threads of thought like a rabid ferret on caffeine, just like the author. Oh, wait, no, I want you to GET something out of this review, so I will try and be clear.
I've made it through 2.5 chapters of this train wreck of a book, so maybe it gets better. In chapter 2, he obstensably shows you how to build an iPhone app with Interface Builder. However, it's not complete. He says things like, "Set the buttons correctly, and proceed to the next section." Of course, he doesn't tell you what "correctly" means. And he does have some goal in mind. He jumps between points of view. And ends up with a program that's not functional. No full source provided. When I wrote in to complain about this, they said, "Just download the full source from our website." I did. It doesn't include source for the program in Chapter 2. It starts at Chapter 3.
Moving along to Chapter 3, it gets better. The first program, HelloView (a simple 'load and do nothing' program actually works. The second program, it's obvious he never TRIED it before. He puts two different classes into the same source file. Not great style to encourage, but, we all get lazy and it's a small program. As soon as you move the cursor over the old UIView variable declaration, the entire XCode IDE spins to 100% CPU usage and locks up (which is 100% reproducable). This doesn't happen if you put the classes in separate files. That's not a bug with this book, per se, but he does lead you down the garden path into exercising a bug in XCode. Again, it suggests he never tested his own code.
Now, that's as far as I've gotten, and I bought it on Sunday.