Matrix: Overview | Matrix Features | How It Works

Matrix offers an effective 4-step process for hosting and distributing any mobile application:

Create an Application Template:

Using the Application Manager tool from within Matrix, clients create what’s called an “Application Template.” For example, if you have developed a mobile game called Defender, even though you may have myriad versions of that game for various devices, you would create only one Application Template for the game. This Application Template can be described as an “umbrella” which holds all the various versions of the game underneath it.

Upload Versions:

Once you have created an Application Template, you can use the Version Uploader tool to upload an infinite number of versions of the application. Going back to the Defender game example, let’s say you created 3 versions of the game to accommodate different handsets (of course, in reality a professional mobile application developer would create dozens of versions):

Version 1: J2ME MIDP 1.0 NOKIA optimized
Version 2: J2ME MIDP 1.0 Motorola-optimized
Version 3: Windows Mobile

Using the Version Uploader tool you would upload the files for each of these different versions.

Configure Device Associations:

In our example, you have uploaded 3 versions of the Defender game – two J2ME versions, and a Windows Mobile version. Now, you must use the Device Associations tool to set up the “rules” for hosting these versions of your application in a handset-intelligent manner. These “rules,” or associations, can be as broad or narrow as you like. Our device database includes a frequently updated list of nearly 1,000 devices which you can create associations with. You may also add your own devices and device properties using a user friendly interface.

There are two ways to specify Device Associations using Matrix:

1.) Individual Device Association: You may associate individual devices to a particular version of your app. For example, if you wanted to handpick only a few Windows Mobile handsets on the market which you developed your Defender game for, this method would be appropriate.

2) Device Property Assocation: You may associate all devices with a specific property or set of properties to a version of your application. Properties include things such as:

- J2ME support & version
- Operating System
- Screen Size
- Manufacturer

Since you can combine multiple device properties when creating a Device Property Association, creating advanced serving rules for your application is as easy as using a drag and drop tool. For example, you could assign version 1 of the Defender game to all devices with J2ME MIDP 1.0 support with screen sizes of 128x160 or smaller that are running SymbianOS, and made by Nokia.

Distribute the Application:

Once you have configured the device associations for your Application, you are ready to set up distribution methods for the application. Matrix provides a number of methods to help you effectively distribute your application via WAP, WAP, and SMS:

1.) Web-2-Mobile: This tool generates javascript forms for you to install on a website in order to distribute the mobile application. The forms prompt the user to enter his phone number and carrier. Upon doing so, the user is sent an SMS with a link to the mobile application (if you are billing for the mobile application, first he is sent a pin-code which he must enter onto the website for “double opt-in”.) Once the user follows the link using his mobile phone browser, our Mobile Application Server determines the target device parameters and serves the appropriate version of your application, as determined by the Device Associations you configured.

2.) WAP-2-Mobile: This tool generates XHTML and PHP code which can be embeded on a WAP Site in order to distribute the mobile application. The forms prompt the user to enter his phone number and carrier. Upon doing so, the user is provided with a link to the mobile application (if you are billing for the mobile application, first he must click an “I Agree” link first). Once the user follows the link, our Mobile Application Server determines the target device parameters and serves the appropriate version of your application, as determined by the Device Associations you configured.

3.) SMS Keywords: This tool generates live SMS Keywords which can be used to distribute the mobile application in a very consumer friendly manner. For example, you could create a keyword called DEFENDER to distribute your Defender game. You would advertise the keyword, urging people to “Text DEFENDER to 23907” (note that the ‘23907’ is known as a Short Code and is used for application-2-person SMS messaging). Once a consumer texted the keyword, he would be provided with a WAP link to download the application. Once again, our Mobile Application Server determines the target device parameters and serves the appropriate version of your application.