Download Adobe AIR Latest Version for Windows and Mac – Adobe AIR stands for Adobe Integrated Runtime (AIR). This application is created by Adobe which is a cross-operating runtime application. This application is needed when you want to develop desktop or mobile applications. This app uses an ActionScript 3 programming language with Adobe Flash technology as well as a combination of HTML 5, CSS and Javascript with WebKit technology. The first version of this app and its SDK (Software Development Kit) was first released on February 25, 2008. The first version of this app is called as Apollo. The next version which is version 2.7 released on 14 June 2011.
Recently, the Adobe developer team has announced that this app can be compatible with the most popular operating system which is Android. With such compatibility, people who work as application developers can use Flash Builder or Flash Professional CS5 with this Adobe app too. They can create an interesting app. Moreover, the app developers can use both old and new code to build Air app for Android.
Some Advantages of Adobe AIR
Since this app is a cross-platform, this Adobe app can run on Windows, Mac OSX, Android, and iOS as well.
Because this app uses Flash technology, the user can create a unique and differentiated look. You can also add animation, sound, and video as well.
Free SDK and the IDE (Integrated Development Environment) is also free. So, if the user wants to build applications with this Adobe app then they do not need to pay.
This app also supports SQLite database which is a database that does not require a server to run it.
AIR Native Extensions allow the user to connect to this Adobe app with other programming languages to perform certain tasks.
This app supports 2D and 3D.
The main program executable is unst00.exe. The software installer includes 10 files and is usually about 37.54 MB (39,363,570 bytes). Adobe AIR Updater.exe is the automatic update component of the software designed to download and apply new updates should new versions be released.
To create an application with Adobe AIR, the user needs
SDK
A Software Development Kit or Packages provided to create an app by using this Adobe app. This package is provided by Adobe and it is free.
IDE
An Integrated Development Environment is a Software used to build programs, ranging from the text editor to writing script, compilation, debug and many more. There are many IDE options for this Adobe app such as Adobe Flash Professional and Adobe Flash Builder which are Software Paid. If you want free software, you can use FlashDevelop. In addition, this Adobe app can also be compiled via command line (CMD).
Some Disadvantages of Adobe AIR
There are many people who think that Adobe Flash is only for animation. However, this app which uses Flash technology can be used to develop an app. So, there are many people think that this Adobe app is just to create animation only.
Less well known in some countries. So, if there is a problem with the app, the user will have to find the solution on their own or look at forums abroad on the internet. This can be bothering some people.
The choice of database is limited. So, the solution is to create AIR Native Extension to perform processing to another database.
That’s the review for Adobe Air, we hope that it helps you to know more about the software.
As of AIR 2, you can use ADT to create native application installers for distributing AIR applications. For example, you can build an EXE installer file for distribution of an AIR application on Windows. You can build a DMG installer file for distribution of an AIR application on Mac OS. In AIR 2.5 and AIR 2.6, you can build a DEB or RPM installer file for distribution of an AIR application on Linux.
Applications installed with a native application installer are known as extended desktop profile applications. You cannot use ADT to package a native installer for an AIR application if the application descriptor file does not support the desktop extended profile. You can restrict this profile using the supportedProfiles element in the application descriptor file. See Device profiles and supportedProfiles.
You can build a native installer version of the AIR application in two basic ways:
You can build the native installer based on the application descriptor file and other source files. (Other source files may include SWF files, HTML files, and other assets.)
You can build the native installer based on an AIR file or based on an AIRI file.
You must use ADT on the same operating system as that of the native installer file you want to generate. So, to create an EXE file for Windows, run ADT on Windows. To create a DMG file for Mac OS, run ADT on Mac OS. To create a DEB or RPG file for Linux, run ADT from the AIR 2.6 SDK on Linux.
When you create a native installer to distribute an AIR application, the application gains these capabilities:
It can launch and interact with native processes, using the NativeProcess class. For details, see one of the following:
Communicating with native processes in AIR (for ActionScript developers)
Communicating with native processes in AIR (for HTML developers)
It can use native extensions.
It can use the File.openWithDefaultApplication() method to open any file with the default system application defined to open it, regardless of its file type. (There are restrictions on applications that are not installed with a native installer. For details, see the entry for the File.openWithDefaultApplication() entry in the language reference.)
However, when packaged as a native installer, the application loses some of the benefits of the AIR file format. A single file can no longer be distributed to all desktop computers. The built-in update function (as well as the updater framework) does not work.
When the user double-clicks the native installer file, it installs the AIR application. If the required version of Adobe AIR is not already installed on the machine, the installer downloads it from the network and installs it first. If there is no network connection from which to obtain the correct version of Adobe AIR (if necessary), installation fails. Also, the installation fails if the operating system is not supported in Adobe AIR 2.
Note: If you want a file to be executable in your installed application, make sure that it's executable on the filesystem when you package your application. (On Mac and Linux, you can use chmod to set the executable flag, if needed.)
Creating a native installer from the application source files
To build a native installer out of the source files for the application, use the -package command with the following syntax (on a single command line):
This syntax is similar to the syntax for packaging an AIR file (without a native installer). However there are a few differences:
You add the -target native option to the command. (If you specify -target air, then ADT generates an AIR file instead of a native installer file.)
You specify the target DMG or EXE file as the installer_file.
Optionally, on Windows you can add a second set of signing options, indicated as [WINDOWS_INSTALLER_SIGNING_OPTIONS] in the syntax listing. On Windows, in addition to signing the AIR file, you can sign the Windows Installer file. Use the same type of certificate and signing option syntax as you would for signing the AIR file (see ADT code signing options). You can use the same certificate to sign the AIR file and the installer file, or you can specify different certificates. When a user downloads a signed Windows Installer file from the web, Windows identifies the source of the file, based on the certificate.
For details on ADT options other than the -target option, see AIR Developer Tool (ADT).
The following example creates a DMG file (a native installer file for Mac OS):
The following example creates an EXE file (a native installer file for Windows):
The following example creates an EXE file and signs it:
Creating a native installer for an application that uses native extensions
You can build a native installer out of the source files for the application and the native extension packages that the application requires. Use the -package command with the following syntax (on a single command line):
This syntax is the same syntax used for packaging an a native installer, with two additional options. Use the -extdir extension-directory option to specify the directory that contains the ANE files (native extensions) that the application uses. Use the optional -migrate flag and MIGRATION_SIGNING_OPTIONS parameters to sign an update to an application with a migration signature, when the primary code-signing certificate is different certificate than the one used by the previous version. For more information see Signing an updated version of an AIR application.
For details on ADT options, see AIR Developer Tool (ADT).
The following example creates a DMG file (a native installer file for Mac OS) for an application that uses native extensions:
Creating a native installer from an AIR file or an AIRI file
You can use ADT to generate a native installer file based on an AIR file or an AIRI file. To build a native installer based on an AIR file, use the ADT -package command with the following syntax (on a single command line):
This syntax is similar to the syntax for creating a native installer based on the source files for the AIR application. However, there are a few differences:
As the source, you specify an AIR file, rather than an application descriptor file and other source files for the AIR application.
Do not specify signing options for the AIR file, as it is already signed
To build a native installer based on an AIRI file, use the ADT -package command with the following syntax (on a single command line):
This syntax is similar to the syntax for creating a native installer based on an AIR file. However there are a few of differences:
As the source, you specify an AIRI file.
You specify signing options for the target AIR application.
The following example creates a DMG file (a native installer file for Mac OS) based on an AIR file:
The following example creates an EXE file (a native installer file for Windows) based on an AIR file:
The following example creates an EXE file (based on an AIR file) and signs it:
The following example creates a DMG file (a native installer file for Mac OS) based on an AIRI file:
The following example creates an EXE file (a native installer file for Windows) based on an AIRI file:
The following example creates an EXE file (based on an AIRI file) and signs it with both an AIR and a native Windows signature: