To sum it up, it’s an action-thriller set in the medieval age of war-torn eastern Europe filled with empirical struggles between feudalism and aristocratic ideals. It’s not well known that Objective-C played a pivotal role in the dismantling of the populous western caste system responsible for the stagnant performance of current day mobile platform development.

I don’t want to give away too much, but there is a romantic interposition towards the end of the book that will leave readers highly suspicious and apprehensive of Android’s luring siren calls.

… but more seriously, details are below.

iPhone Applications Tune-Up
High performance tuning guide for real-world iOS projects

Details and pre-order @ Packt Publishing: http://loyal.ms/gwGfAa

Book description
The best iPhone applications are the ones that demonstrate smooth, fast, efficient and optimal performance. An application should be designed to run at 200 mph, but operate just as smoothly as it would at 5 mph. Developing an application that supports such a wide range of performance needs is no small task and requires an understanding of the basic elements of performance as well as a strong strategy.

This book covers every aspect of tuning, optimizing, and squeezing every last bit of performance out of an iOS project. From application architecture and design to development and deployment, readers will be guided through the entire process of tuning an iOS application for high performance.

Every line of code presents an opportunity to improve upon the effective performance of an application. This book begins with the fundamentals of performance, demonstrating the impact poor performance can have on the success of an application. Apple’s App Store is riddled with applications that fall just short of success and it isn’t too much of a stretch to attribute many of these failures to a lack of optimization. Readers will be lead through each chapter, learning every aspect of performance tuning from simple syntax tips and tricks to advanced process management, and network and memory optimizations.

In addition to theories, syntax, and detailed code examples, readers will learn to take advantage of Apple’s powerful performance measurement and benchmarking utilities to identify the specific components of an iOS project that might need attention.

Learn the fundamentals of performance driven development to remedy existing performance related issues or design high performance iOS applications from start to finish

Who this book is written for
This book is for iOS application developers who are interested in resolving application performance bottlenecks in both new and existing Xcode projects. Readers should be familiar with the basic concepts and principles of iOS development, Objective-C syntax, and use of Apple’s Xcode development environment.

About
This is the first (to be published) book of its kind and is very much focused on Objective-C tuning practices for all iOS platforms, including the iPhone, iPod Touch, iPad and iPad 2. Performance tuning is a recipe that includes some common sense, a little bit of obvious and of course generous helpings of technical know-how and all around development experience. No matter the size or depth of an iOS project, performance can play a key role in an applications success or failure on the market. iPhone Applications Tune-Up is designed to aid developers in squeezing every last bit of performance from every aspect of an application. A lot of experience and research has gone in to producing a book that highlights the areas in which performance gains are most critical and even commonly overlooked.

—

I have an absolute passion for technology and Objective-C represents this deep focus most simply because it encompasses the highest levels of programming technology and advancements in development languages. iPhone Applications Tune-Up will be the result of more than 1000 hours of my personal time; authoring, researching and generally staring at the screen. At this point I have only a couple of chapters remaining before the re-write and finalization work begins. It’s been a long and enjoyable road up to this point and I look forward to its final release.

Now, go pre-order it! http://loyal.ms/gwGfAa

Enjoy.

~Moses

We need to understand that Cairngorm is not a solution to a problem. It is an architecture to force stricter standards compliance with the MVC concept.

MVC (“Model-View-Controller”) is a concept, and we as developers are free to adhere as closely or as loose to this concept as we like.

Each project will have different requirements for the structure that is used to follow an MVC concept and this is where true developers shine.

Common problems or pitfalls in current languages are solved by the use of well known design patterns, not architectures. Design patterns hand a solution to a developer and allow him/her to integrate it in the most appropriate fashion.

Architectures such as Cairngorm create many layers of communication that for some projects may be perfect but for others just too much. They are heavy, commonly break development standards such as encapsulation and programming to interface as well as create vast amounts of linked classes that are near impossible to re-factor in large projects.

Cairngorm has its benefits if used sparingly, but all too often there is an overkill of usage, in which adding one simple feature can cause an avalanche of class modifications.

I find that I become easily annoyed with the half dozen layers, retyping the same code over and over again in each class component and begin to find myself breaking out of Cairngorm standards after only a few hours of development.

Creating a common standard is a good thing, but isn’t that what the language is in itself? A developer is taught standards, best practices and theories for design and some will expand upon these basics and become experts, while others will become lazy and produce poor results.

Let’s all not be punished by those with poor coding practices and be forced to use these training wheels.

… and don’t get me started on rails.