Skip to content
July 13, 2011 / Daniel Freeman

Tutorial 5: Deploying to mobile devices

So far, we’ve built some Mobile applications using MadComponents and Pure ActionScript.   Now we’re going to learn how to deploy them to mobile devices (Android, iPhone, iPad, etc..).  If you’re using a new version of Flash CS5.5, or Flash Builder 4.5, then you’ll already know how to do this from the application.  But If you haven’t yet rushed out and bought the latest upgrade, then read on… because you can use Adobe’s FREE Flex SDK tools.

One Core, Many Flavours

MadComponents is IDE agnostic, so you might have built your application using Flash, or Flash Builder (Flex), or a third-pary free IDE such as AXDT or Flash Develop.  Because MadComponents is based on standard ActionScript, with no AIR-only features, you might even test the core of your mobile application in the browser.

This is what I do.  I divide my AIR Mobile projects into two parts, separating the AIR and non-AIR code.  First I develop a core ActionScript project.  No exotic AIR classes.  It runs in the browser, or anywhere, and you don’t need Adobe’s latest development tools to develop it.

Now I can extend this core, or derive several variants from it if I wish.  One for iPhone, One for Android, One for desktop AIR, One for the browser, etc.

So now if want to add AIR mobile classes, to handle accelerometer events, or utilise the sqlite database, or whatever – I put this AIR code in a separate class.  It extends the top class of my core project, and makes it specific to mobile deployment.  You can use free command-line tools to build this project if your IDE doesn’t support AIR.

Anyway, this is the way I structure my AIR projects.  It may, or may not suit you.

Adobe’s free Flex SDK

You can get the latest release version of Adobe’s free Flex SDK from

(There are downloads for MacOS and Windows.  I’m not sure what the situation is for Linux now.  Anyone? – can you leave a comment if you know).

Once you download this folder, you may or may not want to move it somewhere convenient in your filesystem.  On my Mac, I’d move it to the Developer directory.

Optionally, set a path to the “bin” folder.


amxmlc is the compiler for air applications.  Let’s assume your top application class is called, inside a MadProject folder.

1. Start up your terminal / command-line window.

2. Set the directory to your MadProject project folder.  For example,

cd /Users/danielfreeman/Desktop/MadProject

3. Compile the project.  This creates a familiar .swf file.  Let’s assume that you also want to include the MadComponentsLib, you would write:-

/Developer/flex_sdk_4/bin/amxmlc  -library-path+=MadComponentsLib0_5_5.swc

i. I’m assuming that the path to amxmlc is /Developer/flex_sdk_4/bin/.  But if you’ve put the Flex SDK somewhere else, change the path appropriately.  If you’ve set up a path, you can omit the path.

ii. I’m assuming that you’re using MadComponentsLib0_5_5.swc.  But if you’re using a later version, change this filename.

iii. I’ve assumed that there’s a copy of the .swc library inside the MadProject folder.  Alternatively, set a path to where it is.

When you type this command into the terminal window, it should create your MadProject.swf file.

Android application.xml

We’re going to use adt to create a .apk file for android.  But first, we’re going to make an application.xml file:-

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<application xmlns="">
 <description>MadTest example</description>

This is a very simple template that you can apply to your own projects.   For more information about further options, refer to the documentation at  Or you can take a look at samples/descriptor-sample.xml in the Flex SDK you downloaded.

The options for <aspectRatio> are portrait or landscape.  This determines the initial orientation of your application when it is run.  If you set the <autoOrients> parameter to false, then it will stay in this orientation, and it won’t adjust to device orientation.

Android Permissions

For Android applications, you need to specify permissions for various resources that you use in your application.  So if your app uses the internet, or geolocation, or some other privileged resource – you need to give yourself permission.  You need to specify these permissions inside the application.xml file.  You would put the following XML before the </application> tag above.

                <uses-permission android:name="android.permission.INTERNET" />

(More information about permissions here.)

Signing your application

All Android applications must be signed.  We can use Adobe’s adt tool to create a signing certificate:-

/Developer/flex_sdk_4/bin/adt -certificate -cn -validityPeriod 25 myidentifier 1024-RSA myCertificate.pfx mypassword

Where mycertificate and mypassword are strings of your own choosing.  This will create a .pfx certificate file called myCertificate.pfx.  If you want to put your application on an Android market, you must create a certificate that’s valid for at least 25 years, Hence -validityPeriod 25.

Creating the Android app

Now we’ve prepared the three ingredients to make our android .apk app.  The compiled .swf file, the application.xml and the self-signed certificate.  We can use adt to package for Android:-

/Developer/flex_sdk_4/bin/adt -package -target apk -storetype pkcs12 -keystore myCertificate.pfx -storepass mypassword MadProject.apk application.xml MadProject.swf

This command will create the Android .apk file.

Installing on an Android phone

We can use Google’s adb tool to install the .apk file on an Android phone.  (Get it here.)  On a Windows PC, you may need a driver to allow your PC to talk to your phone.  There’s an install folder in the SDK, that may be relevant to your system.  On a Mac, it just works.  So if you have a driver, plug your phone into your computer.

First of all, you’ll need to install the AIR runtime for Android.  You’ll find it in the Flex SDK.  (runtimes/air/andoid/device/Runtime.apk)

adb -r install Runtime.apk

You only need to install the runtime once.  Not every time.  Now install your application.

adb -r install MadProject.apk

Building an iPhone application

Now, we’re going to package the same application for iPhone.  Last, time we didn’t make any app icons, so let’s go through that step this time.  And we’ll need an application.xml file for iPhone.

Making Icons

Use an image editor to make an icon, and export four .png files of different sizes.  29×29 pixels, 57×57 pixels, 72×72 pixels and 512×512 pixels.  For test purposes, you can just create blank .pngs.  Put these four images into an icons folder inside your MadProject folder.

iPhone application.xml

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<application xmlns="">

<renderMode> gpu means that we’re going to use hardware accelerated graphics.  Notice how we’ve referenced our four icon files.

Provisioning Profile and Developer Certificate

To export to iPhone, iPad, or Ipod, you need to be a paid-up Apple Developer.  Within the members area of, you can create and download a provisioning profile, and a developer certificate.

Packaging for iPhone

So we have the following ingredients that we will use to make a .ipa file for iPhone.

1. A compiled .swf file.  MadProject.swf

2. An iPhone application.xml file.  applicationiPhone.xml

3. Application Icons.  icon29-icon512.png

4. An Apple developer certificate.  developerKey.p12

5. An Apple provisioning profile.  docProfile.mobileprovision

Use adt to build the .ipa as follows.  (Prior to Flex 4.5 SDK, we used to use a tool called “pfi” (packager for iPhone), but this is now deprecated).

/Developer/flex_sdk_4/bin/adt -package -target ipa-debug -provisioning-profile docProfile.mobileprovision -storetype pkcs12 -keystore developerKey.p12 -storepass mypassword MadProject.ipa applicationiPhone.xml MadProject.swf icons/icon29.png icons/icon57.png icons/icon72.png icons/icon512.png

Ok, that’s a long command to type in.  I usually paste all of these commands into a .txt file that I keep in my project folder.  So every time I want to use it, I copy and paste to pop it into my terminal window.

You can install this .ipa application on your iPhone, iPod, or iPad using iTunes.  For more information about adt, take a look here.

What’s next ?

In the next tutorial we’re going to delve deeper into MadComponent’s capabilities.  Advanced Navigation, Scrolling containers, Tab-based applications, View Flippers, Groups, Pop-Ups, and Sliding Drawers.

Further reading

To find out more about MadComponents, you can read the other related threads on this blog, or download the documentation at

There are also lots of code examples to view or check-out from the subversion repository at

Please subscribe to this blog if you want to catch subsequent tutorials.



Leave a Comment
  1. Richard Tolley / Jul 14 2011 12:28 am

    Another nice tutorial and a great upgrade with 0.55.

    I can’t believe it’s been out for 2 days and I didn’t notice.

    It’s fixed another major problem for me.



  2. Marcus Baffa / Jul 17 2011 3:07 pm


    Very good job

    I am new to MadComponents and Would like to know how can we define a password input field.

    Thanks in advance

    • Daniel Freeman / Jul 17 2011 3:35 pm

      Assuming you’ve given the input an id=”myinput”,

      var input:UIInput = UIInput(UI.findViewById(“myinput”));
      UILabel(input.getChildAt(0)).displayAsPassword = true;

  3. Otrovna Kupacica / Jan 25 2012 6:03 pm


    I really like what you did by now and ofcourse I have a question 🙂
    How do you set splash screen image that it shown while application loads?


    • Daniel Freeman / Jan 26 2012 2:58 am

      You’ll notice that a MadComponents springs to life much faster than a Flex app. So less time to fill with a splash screen image.

      I wish this was an option you could set in the XML configuration file, that utilise low level APIs as the app actually loads – but this isn’t an AIR feature.

      So you just need to addChild() your own image (and possibly resize or centre it too), before you do any initialisation or UI.create(…

      When UI.create() has completed, you can remove the image.


  1. AS3 MadComponents Tutorial Series – Starting Out | Caffeine Industries

To discuss MadComponents/MC3D, join the Facebook group!

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: