1. Import the "IRIS Starter Template" into you Sandbox (if you don’t have the latest version, please check with Jenya who can run an export for you)
2. Edit your app name. Go to "Edit App" and rename the "Name" in the "General" tab. Change out your Icon and your Splash-screen for the App.
3. Prepare your data
a) Rename you Data Sources.
-Go into your Data Tab.
-Click on Edit for data source "Iris App Main" (this may have a version number - i.e. "Iris App Main (1)" )
-Rename the file to an intuitive title. e.g. "National Gallery Main"
-Repeat for data sources "IRIS App Slides" and "IRIS App Language"
Note: as of this writing, renaming data sources leaves some items with missing data pointers - ie, in CUSTOM SCRIPTS and where “expressions” are used for images, such as the BACKGROUND IMAGE setting for the KEYPAD VIEW and KEYPAD STOP VALIDATION layer. (Note: the Builder often will point out places where references were lost when you go to the GENERATE screen under the list of WARNINGS.)

While custom scripts may be used in PowerBlocks, if there is a name conflict between a custom script in the PowerBlock and a custom script in the destination app (the app to which the PowerBlock is being imported), the script in the destination app will be used, and the script in the PowerBlock will not be imported. 
b) Update your data 
- The default data sources are all tabular, and can be reloaded by going to the DATA tab, selecting a data source, and clicking the UPDATE DATE button. Make sure you include all relevant fields (such as ‘type’ in the MAIN table) even if you are not using them directly, as there are functional elements that may still depend on using those linkages.
- The language table should be left in even if you do not use the language module as some dependencies are built into the default template behavior. 


With the IRIS Starter Template you already have inherited Battery Activation, Keypad, Audio, Video and Language block features. Determine any additional features you will need that have power blocks (i.e., IRIS Menu, etc), then for additional Power Block to add - 
1. Make sure you are in your Apps tab and have chosen the app that you want to add PowerBlocks to.
2. Click the Powerblocks tab on the lower left. (Iris Powerblocks are prefaced by the term "IRIS")
3. Drag the PowerBlocks that you need into your main view from your PowerBlocks tab on the bottom left.
4. A pop-up dialgue will appear an you will need to hook your existing data sheets to the PowerBlock.
5. Do this for each PowerBlock that you need.


This is the part where you get to roll up your sleeves and stitch the modules together - mostly a process of establishing the flow of screens based on your comp/story board narratives.
Each Power Block includes the views, layers, assets and custom blocks it needs to perform the specific task. What is not included are the entry into the block (i.e., when does the app switch to the view in question) and exits out of the block (i.e., where does the app branch to when it has finished the job of this module?) …
Because exiting the view you are adding often involves setting logic, “PLACEHOLDER VIEWS” are used to provide landing spots to hold the logic in place. To connect the App then, you shift the logic where an action like “SWITCH TO ANOTHER VIEW” goes to the PLACEHOLDER VIEW to the destination view it should really have, such as a MENU VIEW, etc.
For instance, after adding the IRIS VIDEO power block, go into Custom Script GOMEDIATYPE and edit the action for SWITCH TO ANOTHER VIEW when mediatype=video, setting it to now route to the VIDEO View...
You will find there are only a few places that need to be tweaked for any power block, and once you get the hang of this adding power blocks will be fast and easy.


-Change the header and footer graphics for the BATTERY AND KEYPAD ACTICATION VIEW.
-Set the destination for the MENU keypress from the default (sends you to the KEYPAD View) - by going to >Edit App>Event>Iris Menu Tap on the pencil and click on "Switch to Another View" and set the view to the destination desired for the menu key on the IRIS device. i.e. Language View.


Test the App to see if it works! When you go to the Generate screen, you should see only 1 warning message that can be ignored (about the Unrecognized Sys Key in the Custom Block named "Battery Image Battery Check". …) - this one is benign. Any others will alert you to other areas of your App that you should at least check for potential errors.
When you generate the App for testing, checkbox the GENERATE FOR ANDROID and ENABLE QUICK UPDATES checkboxes, to permit faster testing. When your App is working, you will generate again with the ENABLE QUICK UPDATES box NOT checked - so you do not see the “UPDATE?” popup when you enter the App after testing.


A checklist for publishing your commercial build of the App
- For the Commercial App, Edit the Package Name and Certification alias: under EDIT APP>ANDROID set the name for the Commercial App (as it should appear in the Android Market) to a unique and meaningful string - i.e. something in the form‘’ (like com.stadtischegalerie.egonschiele’), and the ANDROID CERTIFICATE ALIAS to ‘com.antenna.iris’
- Set the version number for the App under EDIT APP>GENERAL>CURRENT VERSION (i.e. to 1.0)
- If you want to enable EachScape Reporting (it will need to be on a wifi network for that - which also has the overhead of shortening the battery life), go to EDIT APP>REPORTING and check the box for EACHSCAPE REPORTING.
- Run your final build and test that the HOME key locks as expected - directing the flow to the view you want. 
- Check the ‘back door’ key stroke is operational from the Battery Activation Screen.
- If all looks ok, return to your Build History and click the GENERATE COMMERCIAL BUILD button.
- You will receive the link to the Commercial Build via email. Please test and verify it is working perfectly BEFORE submitting to the Android Market.
- Remember your link to the Commercial Build expires after 10 days. The build itself does not expire. To generate a new link to your Commercial Build, simply go to the Build History for the build in question and copy the DOWNLOAD link under the TRY OUT button.