World Wide Developer Conference 2012

The Apple World Wide Developer Conference (WWDC) 2012 will take place from June 11-15 in San Francisco, CA, providing an opportunity for developers to tap into Apple’s latest innovations in iOS and Mac OS development.

Such is the demand for this event, the tickets sold out within two hours of becoming available on April 25! If you, like me, aren’t lucky enough to be attending, don’t despair–Apple will make slides and videos of the major presentations available through the developer website. It’s not quite the same as being there, but still an incredibly useful resource for every iOS programmer.

If you have already registered to download the Software Development Kit (SDK), you can get a taste of what will be available from the 2012 event by reviewing the material from last year. With over 80 presentations of between 40 minutes and an hour, these materials are a gold mine of information because they include the most up-to-date thinking and techniques direct from Apple’s engineers.

The documentation available for the iOS SDK, either from the website or via Xcode is excellent but, inevitably, struggles to keep up with the most cutting edge tips and tricks from the WWDC presentations. Specific examples I’ve used from last year’s event include things like the use of Automatic Reference Counting (ARC) and the use of iCloud for synchronization of Core Data stores between devices. These topics do now have documentation available but, if you want the freshest view of what’s becoming available in iOS, the WWDC 2012 materials are worth looking out for.

Of course, to make use of the WWDC materials effectively, you do need some experience of iOS programming. They are a perfect follow-on resource after attending Learning Tree’s iPhone® and iPad® Programming: A Comprehensive Hands-On Introduction or Building iPhone® and iPad® Applications: Extended Features courses.

Richard Senior

Type to search blog.learningtree.com

Do you mean "" ?

Sorry, no results were found for your query.

Please check your spelling and try your search again.