Apple released iPhone SDK 3.1.2 on Thursday Oct 8, the release email sent to iPhone App Developers by Apple states this:

iPhone SDK 3.1.2 is now available on the iPhone Dev Center. If you have updated your iPhone app development devices to iPhone OS 3.1.2, you will need to download and install the new iPhone SDK to continue your iPhone app development.

A version of iPhone SDK 3.1.2 is also available to developers who are running Mac OS X Snow Leopard. Please ensure you select the appropriate SDK based on your iPhone app development environment.

iPhone SDK 3.1.2 is now available

Related Posts

• March 30, 2010 -- iPhone OS 3.2 GM Seed – Now Available for iPhone Developers (0)
• March 20, 2010 -- Apple Now Accepting iPad Apps (2)
• September 21, 2009 -- Apple Announced App Store Resource Center for iPhone App Developers (0)
• August 24, 2009 -- Custom URL schemes and Launching other applications — Best Practices for iPhone OS 3.0 (0)
• August 18, 2009 -- Effective ways of handling Interruptions in iPhone App Development (8)

It is a known and acknowledged fact that user’s experience with your iPhone app is of paramount importance in keeping them glued to it. Towards that, handling interruptions gracefully in an iPhone app plays a key role.

iPhone being a “one app at a time” device, apps get interrupted by incoming Phone Calls, SMSs, Calendar Events, Alarms or Push Notifications from other apps on the device.
The iPhone SDK provides a few methods in UIApplicationDelegate which can be implemented to handle the interruptions and keep user’s experience as flawless/seamless as possible.

The Interruption
- (void)applictaionWillResignActive:(UIApplication*)application

This method lets your application know that it is about to be interrupted by the iPhone OS. The name of the method suggests that your app will no longer be active, and will not respond to any user actions until the interruption is taken care of. An interruption like an incoming phone call or an SMS can either be accepted or dismissed by the user, and this is where you have to perform all tasks necessary to resume if the user chooses to leave the application. If the app was a game, it could save any game state needed for a resumption later.

The Resumption / Interruption Dismissed
- (void)applicationDidBecomeActive:(UIApplication*)application

When your application is about to become active again, this method is called by the iPhone OS. If the user decides not to leave the application and dismisses the interruption this is a good place to allow the user resume using the application. Since the application has not yet been closed, all the required state to resume is still in memory and continuing using the app is really as simple as a Pause/Resume feature.

The Interruption Accepted
- (void)applicationWillTerminate:(UIApplication*)application

If the user decides to leave the application or accepts an interruption, this method call from the iPhone OS notifies us of that intention. This is the place where you save all necessary state of the app/game to resume later.

The best place to save all game/app state to resume later is “applicationWillResignActive”. The simple reason being, all iPhone interruptions need user’s input to either accept or dismiss the interruption. This action from the user might needs a few seconds of his/her time to understand what the interruption is and what to do with it. This duration should be just enough for a well written application to save all state. Whereas, in the case of the application being closed by the user, iPhone OS wouldn’t wait for the app to complete saving state. The time available is really short and many applications might fail to save state.

Since there are multiple reasons and ways for an app being closed, state saving method calls need to be placed both in “applictaionWillResignActive” and “applictaionWillTerminate”. But ensure you don’t waste precious time in saving app state at both places. If the user closes the application by pressing the “Home” button, use “applictaionWillTerminate” to save state and necessary cleanups. If the application is being closed due to an interruption, save state in “applictaionWillResignActive” and perform any necessary cleanup in “applictaionWillTerminate”.

So, make it a point to use various UIApplicationDelegate methods to maintain user experience and reusability of the app. Keep your users glued to your application or game and return to it after an interruption.

For more tips and strategies on iPhone App Development, click here. For iPhone app marketing tips, try this link.

Related Posts

• October 9, 2009 -- iPhone SDK 3.1.2. released for iPhone app Developers (1)
• August 13, 2009 -- iPhone development tip for iPhone OS 3.0.1 (4)
• July 30, 2010 -- iAds now pitched for all iPhone Developers (0)
• June 30, 2010 -- 10 exciting news for iPhone Application Developers June 2010 (1)
• June 24, 2010 -- Microsoft allures iPhone and iPad game Developers to make apps for WP7 (0)

Many of my friends woke up to a rude shock when they found that their devices updated to iPhone OS 3.0.1 were not supported by iPhone SDK 3.1 Beta 3 for development.

If you too are experiencing the same problem, here is the solution to continue iPhone development with iPhone SDK 3.0 for your iPhone running iPhone OS 3.0.1.

1. Log-in to your MAC with an Admin account and launch the Terminal application (You will find it in /Applications/Utilities)
2. Copy and Paste the following line into the Terminal window
ln -s /Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.0\ \(7A341\) /Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.0.1

Note: If you have not installed iPhone SDK 3.0 in the default location “/Developer”, replace the “/Developer” directory in the above line as appropriate.

You can download the iPhone 3.0.1 Advisory guidelines document from iPhone Dev Portal

Related Posts

• April 12, 2010 -- iPhone OS 4 Brings Multitasking to iPhone 3GS Users Only (0)
• August 18, 2009 -- Effective ways of handling Interruptions in iPhone App Development (8)
• July 30, 2010 -- iAds now pitched for all iPhone Developers (0)
• July 29, 2010 -- Apple trying to fix slow processing of iOS 4 on iPhone 3G (0)
• June 30, 2010 -- 10 exciting news for iPhone Application Developers June 2010 (1)