Advanced Mobile Framework / FAQ

Definition.xml is the main file. In that file you define Tabs, type of Tabs (predefined Views) and Icons.

If you want to define About Tab, in definition.xml add:

  
    About
    assets/icon/tab/star_160.png
    assets/icon/tab/star_240.png
    assets/icon/tab/star_320.png
    TextImageView
    About.xml
  
  
    Models
    assets/icon/tab/star_160.png
    assets/icon/tab/star_240.png
    assets/icon/tab/star_320.png
    MenuView
    Models.xml
  

and for viewType add TextImageView value.

You have to create new XML called About.xml which will be imported into TextImageView.

Free version is only "demo" what can be built with AMF. To get full feature list please click on this link, and go on the bottom of the page.

If you want to have translations for your application first thing you have to do is import local settings inside your FlashBuilder directory. You can do that by executing script copylocale. How to do that?

• Open Command Prompt on PC, or Terminal on Mac
• Go to Folder: /Applications/Adobe Flash Builder 4.6/sdks/4.6.0/frameworks/locale/
• Run:  /Applications/Adobe Flash Builder 4.6/sdks/4.6.0/bin/copylocale en_US hr_HR

instead hr_HR put your own language that you ant to use e.g: fr_FR for French

Generate an iOS developer certificate or an iOS distribution certificate (*.cer), as required. Note: To deploy an application to a device, you need a developer certificate. To deploy the application to the Apple App Store, you need a distribution certificate.Generate an iOS developer certificate

1. Log in to the iOS Provisioning Portal using your Apple ID, and select the Development tab.
2. Click Request Certificate and browse to the CSR file that you generated and saved on your computer (step 3).
3. Select the CSR file and click Submit.
4. On the Certificates page, click Download.
5. Save the downloaded file (*.developer_identity.cer).

Generate a Certificate Signing Request (CSR) file (*.certSigningRequest). You generate a CSR to obtain a iOS developer/distribution certificate. You can generate a CSR by using Keychain Access on Mac or OpenSSL on Windows. When you generate a CSR you only provide your user name and email address; you don’t provide any information about your application or device.Generating a CSR creates a public key and a private key as well as a *.certSigningRequest file. The public key is included in the CSR, and the private key is used to sign the request.

For more information on generating a CSR, see Generating a certificate signing request.

After installing Flash Builder, and downloading AMF, it is time to "activate" your Advanced Mobile Framework. How to setup your AMF Free or AMF Enterprise into your development Environment? It is quiet easy, and every average PC / Mac User can do it very easy. Just fallow 6 easy steps, and in 5 minutes or less you will be ready to work on you next ultra-mega-cool mobile project. So, are you ready? lets go... ;)

---

Step 1.

Download and Install FlashBuilder 4.6.1

---

Step 2.

Download AMF Free or AMF Enterpreis version from here

---

Step 3.

Open Flash Builder
On Mac -> Go -> Applications -> Adobe -> Flash Builder
On PC -> Start -> All Programs -> Adobe -> Flash Builder

 

---

Step 4.

Go to File -> Import Flash Builder Project

 

---

Step 5.

Click Browse Button, and find on your local drive file that you downloaded from here

 

---

Step 6.

Click Finish

 

 

---

Voila, you have successfully import AMF into your development environment. Now let's go to work and build some cool Android and iPhone applications. If you don't have any idea, check our Blog for latest update, and you will get idea what kind of application you can build in no time.

After importing AMF platform into Flash Builder 4.6 (you can see on this tutorial how to do it), find assets folder under AMF project.
Assets folder is under AMF_1 -> src -> assets

Under assets folder you can find XML folder. Under xml folder open Definition.xml  file.

In Definition.xml file you can set the number of Tabs (Max 5). If you have only one Tab, Tab bar will not be shown

Check the example:

<?xml version="1.0" encoding="UTF-8"?>
<root>
<tab>
<label>About</label>
<icon160>assets/icon/tab/star_160.png</icon160>
<icon240>assets/icon/tab/star_240.png</icon240>
<icon320>assets/icon/tab/star_320.png</icon320>
<viewType>TextImageView</viewType>
<viewDefinition>About.xml</viewDefinition>
</tab>

<tab>
<label>Models</label>
<icon160>assets/icon/tab/star_160.png</icon160>
<icon240>assets/icon/tab/star_240.png</icon240>
<icon320>assets/icon/tab/star_320.png</icon320>
<viewType>MenuView</viewType>
<viewDefinition>Models.xml</viewDefinition>
</tab>
</root>

XMLs can be edited in several ways, but most easiest is editing in Flash Builder. Just Ctrl + Click on MAC or right click on PC on file and after that on Open With Option, and choose Text Editor. On right side (bigger) file will be open.

But you can also edit files in any other Editor, e.g. XML Spy on PC, or Oxygen XML editor.

Under assets folder, find suitable XML (viewType) that you want to have duplicated, right mouse click on it on PC, or ctrl + click on Mac, press Copy option, and than press Paste Option. Dialog Box will be opened, insert new FileName (don't forget to add .xml  at file end.).

Currently we are using this tags in DetailView (only available on Enterprise version):

---

<!-- LOCATION INFO -->
<locationInfo>
<city>Osijek</city>
<county>Osijek-Baranja</county>
<address>Vukovarska 121, Osijek</address>
<lat>45.553029</lat>
<lng>18.721795</lng>
</locationInfo>

---

<!-- CONTACT INFO -->
<contactInfo>
<phone>+38531504499</phone>
<url>http://www.bendek.hr</url>
<email>info@bendek.hr</email>
</contactInfo><

---

<!-- VISITOR INFO -->
<visitorInfo>
<openingHours></openingHours>
<tickets></tickets>
<guidedTours></guidedTours>
</visitorInfo><

---

<!-- 360 Panorama View -->
<extras>
<view360></view360>
</extras>

---

<!-- Image Gallery -->
<images>
<image>assets/image/004_01_a.jpg</image>
<image>assets/image/004_01_b.jpg</image>
</images>

---

<!-- Title Header -->
<header size="3">Restaurant "Bendek"</header>

---

<!-- Subtitle Header -->
<header size="1">115 years of tradition in preparing delicious authentic Slavonian specialties and other gourmet delicacies.</header>

---

<!-- Main Text -->
<text>Opened since 1896. it is the oldest restaurant in Osijek with famous homemade specialties from Slavonia region.</text>

 

Image can be added in TextImageView and DetailsView. It can be added by adding image tag:

<images>
<image>assets/image/007_02_a.jpg</image>
</images>

Image should be deployed into assets/image  folder. It is recommended that image size is: W= 450 px and H= 300 px

Images can be added in TextImageView and DetailsView, by adding image tag:

<images>
<image>assets/image/007_02_a.jpg</image>
<image>assets/image/007_02_b.jpg</image>
<image>assets/image/007_02_c.jpg</image>
<image>assets/image/007_02_d.jpg</image>
<image>assets/image/007_02_e.jpg</image>
</images>

Images should be deployed into assets/image  folder. It is recommended that image size is: W= 450 px and H= 300 px

---

<?xml version="1.0" encoding="UTF-8"?>
<root>
<tab>
<label>News</label>
<icon160>assets/icon/tab/rss_160.png</icon160>
<icon240>assets/icon/tab/rss_240.png</icon240>
<icon320>assets/icon/tab/rss_320.png</icon320>
<viewType>RSSView</viewType>
<viewDefinition>News.xml</viewDefinition>
</tab>
</root>

---

XML file News.xml defines the URL where RSS feed can be found and the way each RSS item is displayed (in this case in WebView):

---

<?xml version="1.0" encoding="UTF-8"?>
<root title="News" showBackButton="false">
<url>http://www.bug.hr/rss/vijesti/</url>
<rssItemView>WebView</rssItemView>
</root>

---

Please note that RSS feed should follow RSS version 2.0 specifications:

Each item is one element of MenuView where title and link are show in list and link is used as URL for WebView

At this point Google Map can only be shown if geo-coordinates (latitude and longitude) are defined inside locationInfo section when defining DetailsView:

---

<?xml version="1.0" encoding="UTF-8"?>
<root title="Hotels">
<!-- LOCATION INFO -->
<locationInfo>
<city>Osijek</city>
<county>Osijek-Baranja</county>
<address>Šamačka 4, Osijek</address>
<lat>45.562094</lat>
<lng>18.680062</lng>
</locationInfo>

---

If both coordinates are set, Map button will appear on action bar – by click on it a WebView opens and shows Google Map with the marker marking the location defined by set coordinates.

---

contactInfo tag can be only defined in XML file which is binded to DetailsView. The following syntax is supported:

---

<contactInfo>
<phone>+38531220700</phone>
<url>http://www.hnk-osijek.hr</url>
<email>blagajna@hnk-osijek.hr</email>
</contactInfo>

---

Three sub-tags are possible:

• phone
• url
• email

---

contactInfo tag can be only defined in XML file which is binded to DetailsView. The following syntax is supported:

---

<contactInfo>
<phone>+38531220700</phone>
<url>http://www.hnk-osijek.hr</url>
<email>blagajna@hnk-osijek.hr</email>
</contactInfo>

---

Three sub-tags are possible:

• phone
• url
• email

---

contactInfo tag can be only defined in XML file which is binded to DetailsView. The following syntax is supported:

---

<contactInfo>
<phone>+38531220700</phone>
<url>http://www.hnk-osijek.hr</url>
<email>blagajna@hnk-osijek.hr</email>
</contactInfo>

---

Three sub-tags are possible:

• phone
• url
• email

---

visitorInfo tag can be only defined in XML file which is binded to DetailsView. The following syntax is supported:

---

<visitorInfo>
<openingHours>Tue, Wed, Fri: 10am – 6pm Thu: 10am - 8pm Sat, Sun: 10am – 1pm</openingHours>
<tickets>Adults: 10 kn Pupils, students and senior citizens: 5 kn Thu and Sun: free access</tickets>
<guidedTours>Previous announcement required.</guidedTours>
</visitorInfo>

---

Three sub-tags are possible:

• openingHours
• tickets
• visitorInfo

---

AMF supports the following views:

• TextImageView – can show headers, text and image(s).
• MenuView – enables definition of list menu
• DetailsView – can show headers, text, image(s), contact info, visitor info, location info, map and 360 panoramas.
• RSSView – shows RSS feed items in list form, click on each item opens URL for that item inside WebView
• RSSItemView – shows content of RSS item’s description tag (without using WebView)
• WebView – shows web page
• SettingsView – change of language

The following XML format acts as data source for TextImageView:

---

<root title="temp" showBackButton="false" showLogo="true">
<images>
<image>assets/image/temp_1.jpg</image>
<image>assets/image/temp_2.jpg</image>
</images>
<header size="1">temp</header>
<line />
<text>temp temp temp temp temp</text>
<image>assets/image/temp_3.jpg</image>
<text>temp temp temp temp temp</text>
</root>

---

Supported tags:

• root – root XML element; defines following attributes:
• title – title which will be shown in title area of action bar; style can be changed in Style.css (.titleText)
• shownBackButton – indicates if back buttons will be shown in navigation area of action bar; valid values are true and false
• showLogo – indicates if logo will be shown in action area of action bar; valid values are true and false; logo images are defined in assets\logo directory
• images – enables definition of image gallery; supports sub-tag image which enables definition of image which will be added to gallery; gallery is browsed by swipe gesture
• header – using this tag it is possible to define header; three header sizes are supported through use of size attribute which can have following values (1 – normal, 2 – bigger, 3 – biggest); header styles can be changed in Style.css (.header1, .header2, .header3)
• line – enables definition of horizontal line
• text – using this tag it is possible to define arbitrary text; text style can be changed in Style.css (.text)
• image – enables definition of single image

The following XML format acts as data source for DetailsView:

---

<root title="">

<locationInfo>
<city></city>
<county></county>
<address></address>
<lat></lat>
<lng></lng>
</locationInfo>
 
<contactInfo>
<phone></phone>
<url></url>
<email></email>
</contactInfo>
 
<visitorInfo>
<openingHours></openingHours>
<tickets></tickets>
<guidedTours></guidedTours>
</visitorInfo>
 
<extras>
<view360></view360>
</extras>
 
<images>
<image>assets/image/temp_1.jpg</image>
<image>assets/image/temp_2.jpg</image>
</images>
<header size="1">temp</header>
<line />
<text>temp temp temp temp temp</text>
<image>assets/image/temp_3.jpg</image>
 
</root>

---

Supported tags:

• root – root XML element; defines following attributes:
• title – title which will be shown in title area of action bar; style can be changed in Style.css (.titleText)
• images – enables definition of image gallery; supports sub-tag image which enables definition of image which will be added togallery;gallery is browsed by swipe gesture
• header – using this tag it is possible to define header; three header sizes are supported through use of size attribute which can have following values (1 – normal, 2 – bigger, 3 – biggest); header styles can be changed in Style.css (.header1, .header2, .header3)
• line – enables definition of horizontal line
• text – using this tag it is possible to define arbitrarytext;text style can be changed in Style.css (.text)
• image – enables definition of single image
• locationInfo – this tag defines section where location information can be defined; the following sub-tags can be defined:
• city – does not affect view (for future use)
• county – does not affect view (for future use)

• address – shown as address inside location information section at the bottom of the view
• lat & lng – geographical latitude and longitude defining the location of described item; if both coordinated are set Map button on action bar is shown
• contactInfo – this tag defines section where contact information can be defined; the following sub-tags can be defined:
• phone – if defined, button is created in contact info section at the bottom of view
• url – if defined, button is created in contact info section at the bottom of view
• email– if defined, button is created in contact info section at the bottom of view
• visitorInfo - this tag defines section where visitor information can be defined; the following sub-tags can be defined:
• openingHours
• tickets
• guidedTours
• extras - this tag defines section where extras can be defined; the following sub-tags can be defined:
• view360 – enables definition of URL where panoramic view is location; if defined 360° button is shown in action area of action bar – by clicking it defined URL is opened inside WebView

The following XML format acts as data source for MenuView:

---

<root title="Shopping" showBackButton="true" backgroundImage="assets/background/list_background.jpg" showLogo="true">
 
<item>
<label>Avenue Mall</label>
<desc>Popular shopping center in which many well-known brands can be found.</desc>
<icon160>assets/image/006_01_thumb_160.jpg</icon160>
<icon240>assets/image/006_01_thumb_240.jpg</icon240>
<icon320>assets/image/006_01_thumb_320.jpg</icon320>
<viewType>DetailsView</viewType>
<viewDefinition>Shopping_01.xml</viewDefinition>
</item>
 
<item>
<label>Portanova</label>
<desc>The biggest shopping centre inSlavonia. Many popular stores like S. Oliver, Mango, Zara and Pittarello can be found there.</desc>
<icon160>assets/image/006_02_thumb_160.jpg</icon160>
<icon240>assets/image/006_02_thumb_240.jpg</icon240>
<icon320>assets/image/006_02_thumb_320.jpg</icon320>
<viewType>DetailsView</viewType>
<viewDefinition>Shopping_02.xml</viewDefinition>
</item>
 
</root>

---

Supported tags:

• root – root XML element; defines following attributes:
• title – title which will be shown in title area of action bar; style can be changed in Style.css (.titleText)
• shownBackButton –indicates if back buttons will be shown in navigation area of action bar; valid values are true and false
• showLogo –indicates if logo will be shown in action area of action bar; valid values are true and false; logo images are defined in assets\logo directory
• backgroundImage – enables definition of background image; if left empty no background is shown on view; background images are defined in \assets\background directory
• item – enables definition of one list one; the following sub-tags are supported;
• label – title text shown for this item; style can be changed in Style.css (.menu)
• desc – additional text shown for this item; style can be changed in Style.css (.menuDesc)
• icon160, icon240, icon320 – using these tags it is possible to defined image for this list item; image can be defined for each DPI value (160, 240, 320); if left empty – no image is displayed inside list item
• viewType – definition of view type which is shown when list item is clicked on
• viewDefinition – XML file which holds definition of view which is shown when list item is clicked on

<?xml version="1.0" encoding="UTF-8"?>
<root>
<tab>
<label>News</label>
<icon160>assets/icon/tab/rss_160.png</icon160>
<icon240>assets/icon/tab/rss_240.png</icon240>
<icon320>assets/icon/tab/rss_320.png</icon320>
    <viewType>RSSView</viewType>
    <viewDefinition>News.xml</viewDefinition>
</tab>
</root>

XML file News.xml defines the URL where RSS feed can be found and the way each RSS item is displayed (in this case in WebView):

<?xml version="1.0" encoding="UTF-8"?>
<root title="News" showBackButton="false">
  <url>http://www.bug.hr/rss/vijesti/</url>
  <rssItemView>WebView</rssItemView>
</root>

Please note that RSS feed should follow RSS version 2.0 specifications:

Each item is one element of MenuView where title and link are show in list and link is used as URL for WebView

visitorInfo tag can be only defined in XML file which is binded to DetailsView. The following syntax is supported:

---

<visitorInfo>
<openingHours>Tue, Wed, Fri: 10am – 6pm Thu: 10am - 8pm Sat, Sun: 10am – 1pm</openingHours>
<tickets>Adults: 10 kn Pupils, students and senior citizens: 5 kn Thu and Sun: free access</tickets>
<guidedTours>Previous announcement required.</guidedTours>
</visitorInfo>

---

Three sub-tags are possible:

• openingHours
• tickets
• visitorInfo

---

iOS
There are certain icon sizes needed specifically for iOS. At the time of this writing, the app-descriptor created when you build a new Flex Mobile project that includes an iOS target does not include XML tags for all of the sizes used for iOS. For instance, you will want to specifically specify these sizes:

• 29×29 shows up in Spotlight search on iPhone or iTouch
• 48×48 shows up in Spotlight search on iPad
• 57×57 home application icon on iPhone and iPod Touch
• 72×72 home application icon on iPad
• 114×114 The iPhone and iPod Touch home screen icon for the 960-by-640–pixel retina display
• 512×512 used to display your app in iTunes

http://devgirl.org/2011/06/20/flexair-for-ios-development-process-explained/

Android
Launcher icons should be 32-bit PNGs with an alpha channel for transparency.
The finished launcher icon dimensions corresponding to a given generalized screen
density are shown below:

• ldpi (120 dpi): 36 x 36 px
• mdpi (160 dpi): 48 x 48 px
• hdpi (240 dpi): 72 x 72 px
• xhdpi (320 dpi): 96 x 96 px

Application Icons in Android Market

If you are publishing your application on Android Market, you will also need to provide a 512 x 512 pixel, high-resolution application icon in the developer console at upload time. This icon will be used in various locations in Android Market and does not replace your launcher icon.

http://developer.android.com/guide/practices/ui_guidelines/icon_design_launcher.html

Header is nice image on top of the application. It is stored under: assets -> background folder
We are supporting 2 size for iOS and for Android devices.

Size for android devices is:
480 x 72px, you should use .png graphic format, and name of file should be header_android.png

Size for iPhone devices is:
480 x 90 px, you should use .png graphic format, and name of file should be header_ios.png

Opening screen (Splash screen) can be found under: assets -> splashscreen folder.Preferred size for image is 800x480 px . For iPhone image will be stretched on 960 x 640 px

Icon files are located in Assets -> Icons. We have separated icons into subfolders for Louncher, Tabs, Menu etc..
There are 3 dimensions that should be included for each icon.

Icons size for buttons:
For big displays  icon should be 48x48 px
For medium  displays  icon should be 32x32 px
For small  displays  icon should be 32x32 px

Icons size for Tabs:
For big displays  icon should be 48x48 px
For medium  displays  icon should be 32x32 px
For small  displays  icon should be 32x32 px

Icons size for Menus:
For big displays  icon should be 64x64 px
For medium  displays  icon should be 48x48 px
For small  displays  icon should be 32x32 px

 

---

<root title="your title" showBackButton="false" backgroundImage="assets/background/list_background.jpg" showLogo="true">

---

if it's left empty, there will be no background image in the view.

Now you can edit text color of your application. It can be easily changed by editing .CSS file. Open Style.css which can be found under src folder. Change "color:" variable in whatever you like. e.g. from color: #ff0000; change it into color: #cccccc;

s|TextArea {
color: #ff0000;

}

.titleText {
color: #ffffff;

.text {
color: #000000;
}

.menu, .rss {
color: #FAFAFA;
}

.menuDesc, .rssDesc {
color: #F2F5A9;

 

Register the Unique Device Identifier (UDID) of the device.This step is applicable only if you are deploying your application to an iOS device and not the Apple App Store. If you want to deploy your application on several iOS devices, register the UDID of each device. Obtain the UDID of your iOS device

1. Connect the iOS device to your development computer and launch iTunes. The connected iOS device appears under the Devices section in iTunes.
2. Click the device name to display a summary of the iOS device.

You can copy the UDID from iTunes using the keyboard shortcut Ctrl+C (Windows) or Cmd+C (Mac).

Register the UDID of your device
Log in to the iOS Provisioning Portal using your Apple ID and register the device’s UDID.

Generate a Developer Provisioning Profile

1. Log in to the iOS Provisioning Portal using your Apple ID.
2. Go to Certificate > Provisioning, and click New Profile.
3. Enter a profile name, select the iOS developer certificate, the App ID, and the UDIDs on which you want to install the application.
4. Click Submit.
5. Download the generated Developer Provisioning Profile file (*.mobileprovision)and save it on your computer.

Generate the Application ID by following these steps:

1. Log in to the iOS Provisioning Portal using your Apple ID.
2. Go to the App IDs page, and click New App ID.
3. In the Manage tab, enter a description for your application, generate a new Bundle Seed ID, and enter a Bundle Identifier.
4. Every application has a unique Application ID, which you specify in the application descriptor XML file. An Application ID consists of a ten-character "Bundle Seed ID" that Apple provides and a "Bundle Identifier" suffix that you specify. The Bundle Identifier you specify must match the application ID in the application descriptor file. For example, if your Application ID is com.myDomain.*, the ID in the application descriptor file must start with com.myDomain.
5. Important: Wildcard Bundle Identifiers are good for developing and testing iOS applications but can't be used to deploy applications to the Apple App Store.
6. Generate a Developer Provisioning Profile file or a Distribution Provisioning Profile File (*.mobileprovision).
7. Note: To deploy an application to a device, you need a Developer Provisioning Profile. To deploy the application to the Apple App Store, you need a Distribution Provisioning Profile. You use a Distribution Provisioning Profile to sign your application.

Generate an iOS distribution certificate

1. Log in to the iOS Provisioning Portal using your Apple ID, and select the Distribution tab
2. Click Request Certificate and browse to the CSR file that you generated and saved on your computer (step 3).
3. Select the CSR file and click Submit.
4. On the Certificates page, click Download.
5. Save the downloaded file (*.distribution_identity.cer).

Convert the iOS developer certificate or the iOS distribution certificate to a P12 file format (*.p12). You convert the iOS developer or iOS distribution certificate to a P12 format so that Flash Builder can digitally sign your iOS application. Converting to a P12 format combines your iOS developer/distribution certificate and the associated private key into a single file.Note: If you are testing the application on the desktop using the AIR Debug Launcher (ADL), you don’t have to convert the iOS developer/distribution certificate into a P12 format.

Use Keychain Access on Mac or OpenSSL on Windows to generate a Personal Information Exchange (*.p12) file. For more information, see Convert a developer certificate into a P12 file.

Generate an iOS developer certificate or an iOS distribution certificate (*.cer), as required. Note: To deploy an application to a device, you need a developer certificate. To deploy the application to the Apple App Store, you need a distribution certificate.Generate an iOS developer certificate

1. Log in to the iOS Provisioning Portal using your Apple ID, and select the Development tab.
2. Click Request Certificate and browse to the CSR file that you generated and saved on your computer (step 3).
3. Select the CSR file and click Submit.
4. On the Certificates page, click Download.
5. Save the downloaded file (*.developer_identity.cer).

Generate a Certificate Signing Request (CSR) file (*.certSigningRequest). You generate a CSR to obtain a iOS developer/distribution certificate. You can generate a CSR by using Keychain Access on Mac or OpenSSL on Windows. When you generate a CSR you only provide your user name and email address; you don’t provide any information about your application or device.Generating a CSR creates a public key and a private key as well as a *.certSigningRequest file. The public key is included in the CSR, and the private key is used to sign the request.

For more information on generating a CSR, see Generating a certificate signing request.

Before you export a mobile application, you can customize the Android permissions. Customize the settings manually in the application descriptor file. These settings are in the block of the bin-debug/app_name-app.xml file. For more information, see Setting AIR application properties.

If you export the application for later installation on a device, install the application package using the tools provided by the device’s OS provider.

1. In Flash Builder, select Project > Export Release Build.
2. Select the project and application that you want to export.
3. Select the target platforms and the location to export the project.
4. Export and sign a platform-specific application package.

You can package your application with a digital signature for each target platform or as a digitally signed AIR application for the desktop.

You can also export the application as intermediate AIRI file that can be signed later. If you select that option, use the AIR adt command line tool later to package the AIRI as an APK file. Then install the APK file on the device using platform-specific tools (for example, with the Android SDK, use adb).