• List Price: CDN$ 47.50
  • You Save: CDN$ 10.50 (22%)
Usually ships within 1 to 3 weeks.
Ships from and sold by Amazon.ca.
Gift-wrap available.
iOS SDK Development has been added to your Cart
+ CDN$ 6.49 shipping
Used: Very Good | Details
Condition: Used: Very Good
Comment: Very gently used. Tight binding and clean pages.
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

iOS SDK Development Paperback – Dec 2 2012

See all formats and editions Hide other formats and editions
Amazon Price New from Used from
"Please retry"
CDN$ 37.00
CDN$ 37.00 CDN$ 3.81

Product Details

Product Description

About the Author

Chris Adamson is a writer, editor, and independent developer specializing in media software development for iOS. He maintains a corporate identity asSubsequently & Furthermore, Inc.and writes the[Time code ];blog on media software development, as well as tweeting as@invalidname.

Inside This Book

(Learn More)
Browse Sample Pages
Front Cover | Table of Contents | Excerpt | Index
Search inside this book:

Customer Reviews

There are no customer reviews yet on Amazon.ca
5 star
4 star
3 star
2 star
1 star

Most Helpful Customer Reviews on Amazon.com (beta)

Amazon.com: 3 reviews
3 of 3 people found the following review helpful
Like reading a screencast Feb. 1 2013
By Alex Chaffee - Published on Amazon.com
Format: Paperback Verified Purchase
This book is structured as an paint-by-numbers tutorial. It walks you through a couple of sample applications with full source code (both in the book and for download). It's very thorough, and it's great that they really build a functional app and cover every detail (down to what little Interface Builder widget you need to control-click-and-drag). And the authorial voice is pleasant, helpful and authoritative without being condescending.

Unfortunately, it often misses the forest for the trees. In their rush to explain the next code snippet, the authors often gloss over important concepts and even object names. The verbosity and obscurity of ObjectiveC/Cocoa code is so hard to parse visually (even for experts in other languages) that it's very important to explain not just what the code is doing, but why, and what other design alternatives we had. While their explanations are often satisfactory, they're often not, and even more often are said parenthetically or after the fact. And even their toy app is complex enough -- what with all the callbacks and interfaces and outlets and delegates and notifications and such -- that a few entity relationship or sequence diagrams would have been a great help. Instead, all we got were prose and code and screenshots.

I found myself reading along with the Apple documentation (e.g. [ ... ]l ) while (and ultimately, prior to) reading each chapter and found that Apple's tech writers provided the clarity and context missing from this book. OTOH, this book provided the step-by-step code samples missing from the Apple docs.
A no nonsense approach to learning the key points of Objective-C and iOS Dec 17 2012
By T. Anderson - Published on Amazon.com
Format: Paperback
This book a no nonsense approach to learning the key points of Objective-C and iOS at the speed of light. It is a fast paced sprint through tons of hands on examples.

The books starts off with a nice introduction to Xcode by building a small twitter application using the new iOS 6 Social framework. The twitter application is used as the example in the first 3 chapters and then the rest of the book builds a recipe application.

I have listed the chapters below to give you an idea of the topics covered throughout the book.

Tweetings, and Welcome to iOS 6
Programming for iOS
Asynchronicity and Concurrency
View Controllers
Table Views
Storyboards and Container Controllers
Documents and iCloud
Drawing and Animating
Testing and Fixing Apps
The App Store and Beyond
Wait! I Forgot (Or Never Learned) C!

To me this is not a reference book, but rather a great cover to cover read. There are a lot of books that I don't get far with that are hands on building of an application from start to finish, but this one really kept my interest. The applications being built are at the perfect level of complexity to introduce a ton of topics, but do not bog you down with a bunch of domain knowledge. I hate the books like this that spend 50% of the book explaining the non-technical what and why of what you're building.

I found the chapter on storyboards very cool. The authors take the recipe application built using a pre-iOS mindset using nibs up to this point in the book, and converts it to a storyboard application. They reuse all the view controllers built so far. This is a great chapter for showing the power of the MVC pattern used throughout iOS development.

The chapter on Documents and iCloud does a great job of introducing persistence by implementing the NSCoding protocol. There is no Core Data coverage in this chapter or the rest of the book. I also could not get the iCloud samples from this chapter to run, but I did not spend much time on trying to get it to work.

The chapter on testing provides a nice introduction to unit testing, debugging, and performance testing using Instruments.

I think a reader should have some experience with C or Objective-C before reading this book. Like I said above the authors have a very no-nonsense approach. But I would recommend a little more experience than what the author's put into the Wait! I Forgot (Or Never Learned) C! appendix. C in 7 pages is a bit to no-nonsense!

Over all I found the book a really enjoyable read. I definitely recommend it to anyone that wants to learn iOS through a hands on experience. This book will give you a great foundation to start building on.
Provides relevant examples, needs clearer explanations Aug. 8 2013
By Michael L. - Published on Amazon.com
Format: Paperback
As a Computer Science student who had only been given an introduction to iOS through school, I was looking for ways to advance my skills and eventually have the knowledge required to create an app. While I had this book, I also started watching Stanford's iTunes U course on creating iOS apps so I mostly read about topics not covered by Stanford.

Overall, I benefitted from this book, but I think readers would be better off if a few changes were made. The authors do a good job of including relevant examples that many of today's apps use, such as those examples involving sending tweets and iCloud. This was great because I could actually implement what I learned into an app and have it be a useful feature. It would be great to have more of these kinds of examples (MapKit?) so that I can walk away from the book with the ability to add commonly used features into an app. Also, the authors routinely provided explanations of why they did something in a particular way which helped me to understand their thought process as they were writing the code.

On the other hand, some topics should be explained in terms that are easier to understand. For instance, the section on Instruments did not provide enough background for me to have a true understanding of how it works. Concepts like these deserve to be allocated more pages so that straightforward explanations can be offered.

In all, the book was helpful to me and I am more knowledgeable as a result of reading it. The authors should continue to focus on choosing relevant examples and ensure that they provide clear, easy to understand explanations of advanced concepts.