Ebook: iPhone Cool Projects

I bought this book because I wanted to see code that successful iPhone developers had written. I guess I was looking for "best practices" sort of information and I was hoping that I might get insight on how to tackle some problems I have run into when developing my own applications.

Book Flow

The biggest disappointment in this book is that developers wrote it (I am assuming). The book lacks the continuity you would normally find when one or two people collaborate on an entire book. When a different person writes each chapter, you get seven different styles in this book. I found a couple of the chapters very well written, but the rest I found to be, well, written by developers. I'm not saying that developers are inherently bad at writing, but it takes a certain something to relay information to other developers effectively. Most of the writers of this book just do not have it.

Code Samples

I got very frustrated reading chapters with code snippets from applications the various authors had written. If a working application had been available to provide context to the snippets, then I would have been less frustrated. For example, in Chapter 5, the first 12 pages of the chapter provide code snippets with very brief explanations of what the code is supposed to do. No working example is provided for context. I couldn't even play with the code to see what was going on. It was almost like I was expected just to know the context because I was on the team that wrote the application. The last 10 pages actually create a working sample. I would have rather spent the entire chapter creating the application with better explanations of each step and theory behind the code.

Proofreading

I wish I had a dollar for all the typos I've seen in this book. Again, in chapter 5, page 118 there is a screen shot of the application the author wrote. The caption says it's a screen shot of the application that you will be writing at the end of the chapter. Sloppy.

Conclusion

I feel like I did get some useful information from this book. Was it worth the frustration of reading poorly written text, no context for code snippets, and numerous errors? Not in my opinion.