Mobile Properties

From FDT Documentation

Revision as of 16:27, 15 September 2011 by Aklement (Talk | contribs)
Jump to: navigation, search



Difficulty: Beginner

Platform: Flash

With FDT5, a new mobile workflow has been introduced. To get started, you'll need to know how to effectively use the Mobile Properties panel.

Accessing The Properties

Open properties.png

To access the mobile properties for you project, simple right click on the project and select 'Properties'.


Once inside the project properties, navigate to FDT Mobile Properties>Android. Here you'll first see the Building tab.

The Building tab is where you set the .SWF and descriptor file you wish to work with.

Properties 01.png

  1. The Enable checkbox will show the platform options.
  2. The Application descriptor associated with this platform will appear here.
  3. Changing the name of the .SWF.
  4. If you wish to change descriptor files, use the Browse button.
  5. Create a new descriptor file. This will use the descriptor file from the currently selected SDK.


The properties tab will differ slightly depending on the platform you wish to use. In general, this is a GUI to edit the descriptor.xml file that is set in the Building tab.

Learn more about using descriptor files here


Properties 02.png

  1. These input fields help manage your application information on the deployed on device.
  2. This area will dynamically change depending on the selected platform. In this example, you edit Android OS permissions here.


Properties 07.png

Digital Signature

Similar to the Properties tab, this tab will be slightly different for Android and iOS. If set, FDT will use this certificate for testing (building via launcher) and for deployment. If it is left blank, FDT will generate a dummy one itself; however, it MUST be set when about to deploy to a Market place.


Properties 03.png

  1. The selected certificate and password are shown here.
  2. If you have an existing certificate you'd like to use, select it here.
  3. Create your certificate here.


Properties 08.png

  1. When testing iOS applications on a device, you'll need a valid provision file and key. Learn more about the process here.
  2. If desired, you can have two separate keys setup. This is handy when you have one provision file for personal use, but you use a separate one for larger distribution.


Set your application icons here. When your icons have been set, make sure that the icons are included within your Package Contents.


Properties 04.png

  1. Resolution for icons that are required for the selected platform.
  2. Choose a valid .png file.
  3. Remove the path to an icon.


Properties 09.png

Package Contents

Properties 05.png When you want to include additional files (e.g icons) you will need to set them here. Not adding the optional files will cause the packaging to fail.

  1. The description.xml & .SWF are needed and cannot be removed.
  2. Here the paths for the icon files set in the Icons tab are set .
  3. Optionally you can choose to include an entire directory (e.g. your entire icon directory).


When you're ready to deploy your application for distribution (or for iOS Ad Hoc) you export it here. This is generally done at the end of your development process when you want all debugging information removed. This will mean a slightly longer compilation process and in the case of iOS, this could be several minutes.


Properties 06.png

  1. To ensure that a non-debug version of your .SWF is generated, you must choose which launcher to execute just ahead of finial packaging.
  2. Where your finial file (.apk or .ipa) is saved to.
  3. For Android, you may choose a store setting where the AIR runtime can be acquired in case your customers don't have AIR installed.
  4. Choose this to have the finial application installed on your device.
  5. Begin the finial packaging process.


Properties 10.png

Get FDT5