It’s saturday noon and I’ve got an FDT5 Prerelease version installed (thanks again to Powerflasher). And as I’m about to do some iOS & Adobe AIR performance tests I’m in need of an app.. obviously. So, wouldn’t it be nice to directly check out the new mobile workflow in FDT? It could cost me a lot of time if it’s failing, though. However, I’m pretty sure they’ve tested it once or twice before finally releasing it on October 26! So, whatever you’re going to read from now on can be done by yourself from Wednesday on – because FDT5 will be free.
- Create App ID in DevCenter.
- Create Provisioning Profile in DevCenter.
- Start FDT5.
- Create new mobile project.
- “Launch as FDT mobile Application” – that’s new, cool!
- Target Apple iOS. Ah, it points me to add some information in the project properties.
- Enter app name and ID. Chose Provisioning Profile. Chose Certificate, enter password.
- Browse for icons.
- Click on Launch now and wait two minutes.
- There’s the .ipa file, ready to be installed on your device.
Cool. That was pretty easy! Let’s see what has changed in detail.
Creating a new FDT project
Due to FDT5‘s completely new mobile wizard to create iOS or Android apps it has become a very comfortable, quick and easy way to deploy apps for your device. FDT5 therefore has clearly caught up to current IDE’s workflow and, as far as I can say, even brought it a step further – for example you’re now able to add Native Extensions For AIR directly within your mobile project properties.
Besides I really like these launch configurations. You’re able to set up different configurations for each, SWF and Mobile Application. And it creates debug versions of it, so launching a Mobile Configuration as debug (means press the bug-icon, not the play-icon ;)) automatically deploys it with a WiFi-Debug param, adding your own IP and launching FDT5‘s debugger after it. Starting the app on your device automatically connects it to your PC and you’re fully able to debug the application as with every other SWF. And of course you can simply launch an SWF Application as debug, it will open the ADL with the device’s dimensions.
It becomes especially useful when sharing projects with other team members as you are able to give them the exact same deploy results due to the same launch configs. You do not need to reconfigure device specifactions or pre/post tasks.
Every single information about the app itself can be found in the project properties now. A new tab called “Mobile Properties” has been added and allows you to browse for your certificates, icons, additional files, Native Air Extensions and stuff. It also allows you to directly set up the options for a store- or AdHoc release.
Another little neat feature: Followed by the fact that FDT does not ship with merged SDKs they’ve built in a way to automatically merge an installed SDK with a .zip file. Means, you simply select your current SDK and e.g. chose the AdobeAIRSDK.zip file. FDT then merges both SDKs for you and it’s all fine. Afterwards I’d suggest to add something like _AIR3 to your SDK name, so you can keep track of it.
I’ve tested it with an iPhone and iPad app and it took me 03:54 from downloading the provisioning file to actually see my app on the device. Well done, Powerflasher!
This little video shows some other FDT5 improvements like method extracting. Nothing directly linked to this mobile workflow but definetly worth to watch :)