The SDK will enable app developers to create apps for multiple platforms at low cost. “Adobe AIR 2.6 enables me to develop once and publish across multiple platforms. There are slight tweaks required for each platform (Android vs iOS) but we’re talking about a few minutes not weeks. The majority of the optimizations revolve around screen sizes which would be an issue regardless of the development tool. If I were targeting Android and iOS natively vs Adobe AIR I would expect my costs to be at least 80% higher; and much closer to 100 – 150% higher should maintenance and updates be required for each platform,”says Charlie Schulze, President and co-founder, Woven Interactive, LLC.

What AIR 2.6 brings for iOS?

• New features like multitasking, Retina display and front and back camera support.
• iPhone developers can build applications that capture audio with the microphone and make use of the graphics hardware method used in AIR for Android using OpenGL ES2.
• AIR Developer Tool (ADT), a tool used for compiling application in the AIR SDK, to package AIR files, native desktop installers, AIR applications for Android and iOS.
Interested iPhone developers can download AIR 2.6 from here.

Source- Adobe

Related Posts

• April 25, 2011 -- Incentivised app download ban may push iPhone developers to iAd. (0)
• February 4, 2011 -- Scaleform to showcase UI Technology for iOS application developers at Mobile World Congress. (0)
• September 21, 2011 -- Appcelerator launches Open Mobile Marketplace for Android and iOS app developers. (0)
• September 14, 2011 -- iPhone developers can relax, Jobs resignation has little impact on Apple, says study. (0)
• September 8, 2011 -- MapText releases mapping SDK for iPad & iPhone developers. (0)

There was a case where what ever I did, did not work. Many attempts to install using iTunes after trying to change certificates, provisioning profiles have failed. Even the “iPhone Configuration Utility” failed to install the app. I had actually lost all hopes getting it installed on this device. But after a little prayer and just a little hope left, it just worked.

Why did it work? I do not have any answer. Can’t still figure it out. And that was the first time I tried installing an Adhoc build on a device for a Windows user!! Is it really so hard?

Could not install application on device: Error: A signed resource has been added, modified or deleted.

The image that you see here, is another failed attempt at installing an Adhoc build for a Windows user. But this got resolved real quick.

The reason: Mac allows file names to contain some special characters (like ‘*’) which are not valid on a Windows PC. This is one thing you can check if you come across errors of above kind. But not all of them will be the same as above.

If any one else has faced a similar problem and found a definitive solution, let us know here.

Related Posts

• September 21, 2009 -- Apple Announced App Store Resource Center for iPhone App Developers (0)
• August 26, 2009 -- Memory Issues in iPhone OS 3.0 : Sample Code (2)
• August 24, 2009 -- Custom URL schemes and Launching other applications — Best Practices for iPhone OS 3.0 (1)
• December 20, 2011 -- iPhone app developers rushing-in to submit apps before shut down. (0)
• December 12, 2011 -- Apple Seeds iOS 5.1 Beta 2 to iPad and iPhone App Developers. (0)

Here comes iSimulate from vimov to your rescue. People at vimov have created a really useful utility for developers to test their applications which employ GPS and Accelerometer on the iPhone Simulator. Lots of time saved between installs right!!

iSimulate is an application which you download and install on your device to send accelerometer and GPS details to the app running on the iPhone Simulator. The app must of course embed the iSimulate library to be able to receive those details. All it takes to install the iSimulate app on your device, embed the library in your application and start using it is just around 5 minutes.

The newer releases of iSimulate even support video streaming. You can actually see the game or app on your iPhone or iPodTouch even though it’s running on the iPhone Simulator. This enables you to provide very accurate touches to the Simulator. This is a giant leap forward from it’s first days where you had screen filled with Accelerometer graph to simulate touches!!

iSimulate really makes testing your apps easy and quick. Go get your apps on to AppStore that much quicker!!

Related Posts

• August 24, 2009 -- Custom URL schemes and Launching other applications — Best Practices for iPhone OS 3.0 (1)
• December 20, 2011 -- iPhone app developers rushing-in to submit apps before shut down. (0)
• December 12, 2011 -- Apple Seeds iOS 5.1 Beta 2 to iPad and iPhone App Developers. (0)
• November 29, 2011 -- Apple seeds iOS 5.1 beta to iPad and iPhone app developers. (0)
• November 21, 2011 -- Study highlights revenue advantage for iPad and iPhone app developers. (0)

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

• July 20, 2011 -- Box announces new APIs for iOS and Android, global challenge for app developers. (0)
• July 1, 2011 -- AddThis SDK available for iPhone app developers. (0)
• May 19, 2011 -- Adknowledge and Ansca Mobile join hands to make it easy for iPhone developer. (0)
• May 10, 2011 -- Microsoft releases Azure tools for iPhone developers. (0)
• April 5, 2011 -- Survey offers key insights on app development for iPhone developers. (0)

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)
• September 19, 2011 -- Mobile Cloud Computing: Should iPhone app developers fly to the cloud? (0)
• July 20, 2011 -- Socialize releases SDK for Android and iOS app developers. (0)
• July 20, 2011 -- Box announces new APIs for iOS and Android, global challenge for app developers. (0)

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)
• January 7, 2011 -- iPhone’s customer loyalty highest in the market (0)
• August 5, 2010 -- Game Center not supported on iPhone 3G and second Gen iPod Touch (0)
• August 5, 2010 -- Report says iPhone 3GS drops more calls than iPhone 4 (0)