In the Intel® XDK development environment, once you have completed debugging and testing your app you can use the Build tab to make packages suitable for submitting to a variety of app stores. There are two types of app builds available:
- Build a Mobile App creates a native app package suitable for submission to an app store for download and installation onto a mobile device.
- Build a Web App creates an HTML5 package suitable for submitting to web app stores or for placement on a web server.
Build a Mobile App
You can choose from a variety of targets when building your app for a native operating system, including Google Android*, Apple iOS* and Windows 8*.
Click the
button corresponding to the target for which you wish to build. This connects you to the build server and uploads your project files to your account on the Intel XDK build server. Once there, the build server may request additional information to complete the build process. These additional screens typically require an app name, icon and splash screen images, and any certificates needed to sign the app. In some instances, you may be required to have a developer's license to complete the build process. Also, in some cases the build process may ask you to copy files and/or keys from the build server for use with app store submission.
NOTE: The Intel XDK build service will NOT submit your packaged app to a store but, it does provide you with a package that is suitable for store submission. If you wish to submit your app to a store, you must do that outside of the Intel XDK.
There are two basic hybrid HTML5 web app containers that can be built in the Mobile App section of build targets: standard Intel XDK containers and Apache Cordova* Beta containers.
In addition, there are two unique hybrid HTML5 Web App containers: the Crosswalk* for Android container and the Tizen* container.
All build targets create a hybrid HTML5 web app package that can be submitted to an app store and installed on a mobile device. The Crosswalk for Android container includes its own HTML5 runtime engine, based on the Crosswalk project (see Using Crosswalk). All other applications utilize the built-in webview (aka embedded browser) that is part of the target mobile device firmware to execute (render) your hybrid HTML5 web app. For example, Android packages use the Android browser webview built into the Android device, iOS packages use the Apple Safari* browser webview built into the iOS device, etc.
Standard Intel XDK Container Builds
The standard Intel XDK container builds are based on the original appMobi* hybrid HTML5 container and support the full Intel XDK API, the appMobi services API and the standard Cordova 2.9.0 API. These builds include all the targets listed in the Mobile App section of the build page except: the Crosswalk for Android, the Tizen and the Cordova for "*" targets.
Details regarding how to use the standard Intel XDK containers are provided in the links below:
- Google* Android step-by-step build tutorial.
- Apple* iOS step-by-step build tutorial.
- You will need your app id from the Apple* iOS Dev Center.
- See this screenshot walk-through for information about the iOS build process.
- See this screenshot walk-through for information on exporting your P12 Certificate.
- Microsoft* Windows 8 step-by-step build tutorial.
- Microsoft* Windows Phone step-by-step build tutorial.
NOTE: The Nook* and Amazon* build targets are minor variations of the standard Intel XDK Android build target; use the instructions for the Android build target as a guide for these two build targets.
Beta Cordova Container Builds
The Beta Cordova build targets are based on the standard Cordova CLI 3.x build system. These build targets are compatible with standard Cordova (aka Adobe PhoneGap*) build systems and, in addition to support for the core Cordova 3.x API, also support a subset of the Intel XDK APIs, via a set of custom Cordova plugins. These build targets do not support the appMobi services API.
At this time, these targets require a hand-built intelxdk.config.xml file be included in your project to direct the build process and specify the plugins (APIs) required by your application. Please start with Using the Intel XDK “Cordova for *” Build Option for details on how to use these build targets.
NOTE: The Windows 8 target refers to applications built for the Windows 8 "Modern UI" environment. Windows 8 Phone is used to designate Windows Phone devices.
Crosswalk for Android Container Build
Information on how to build apps for the Crosswalk for Android container are described in Using the Intel XDK “Crosswalk for Android” Build Option. Like the Cordova build targets, this build target also supports the core Cordova 3.x APIs and a subset of the Intel XDK APIs. It also does not support the appMobi services API.
Unlike the Cordova and standard Intel XDK apps, the Crosswalk container includes a custom runtime engine for executing your hybrid HTML5 application. For this reason it is significantly larger than packages built using the other build targets. This build option creates two processor specific packages (an x86 APK for use on x86 Android devices and an ARM APK for ARM Android devices).
For technical and legal reasons the Crosswalk runtime engine is only available for Android 4.x devices.
Tizen Container Build
See this tutorial for help if you wish to build a Tizen* application.
NOTE: HTML5 application packages are standard ZIP files. If you are curious as to what is added to your app when a build is performed, you can "unzip" the app package and inspect its contents. However, if you modify the contents you will invalidate the application package signature; modifying a package after it has been built is not advised.
Build a Web App
There are fewer web app targets because there is less overhead require to put an HTML5 app on the web. These are mostly convenience builds that add manifest files and, in some cases, support libraries to your app package. You can "unzip" these packages to see what has been added and to better understand what these builds do.
Click the button for your target of choice. This connects you to the build server and uploads your project to your account in the Intel XDK build server. Once the build server has your code, it will request any additional information necessary to complete the process and add the internal infrastructure necessary to host your code as a web app on a server.
See this tutorial for information about building a Google Chrome web application.
Legal Information
329657-002US