Junaio Plugin applications

This web provides an overview on a typical project workflow for a junaio plug-in application developed by metaio. The application has two main parts: the graphical user-interface front-end (iOS and Android app) and the content configuration on the server back-end. The main advantages of a junaio-plugin based application are:

• content is stored on the server and can therefore be udpated/exchanged independently from the iOS/Android applications in the stores
• different from junaio the graphical user interface can be branded by the client

Examples for junaio plug-in based applications are for instance:

• TVMovie Trailer View> ( http://itunes.apple.com/de/app/tv-movie-trailerview/id427967517?mt=8, https://market.android.com/details?id=com.metaio.junaio.plugin.trailer_view&feature=more_from_developer)
• stern AR ( http://itunes.apple.com/de/app/stern-ar/id458602939?mt=8, https://market.android.com/details?id=com.metaio.junaio.plugin.stern_ar)

Table of Contents

Project Details

For each project a few details should be clarified in the beginning:

• Responsible contact persons
• Responsible parties for content creation/delivery
• Go-live date for the application (e.g. magazine in the stores, event, etc.)
  • Please note that for App Store submission a review period of around 1-2 weeks should be planned.

In case a series of content exchanges is planned (e.g. several magazines in a row) a list of the publish dates together with delivery dates for final content and final print layout should be provided.

Application development

In order to create the applications, some input material is required.

• Application name
• Image material for application icon and start screen
• Optional: cover selection view
• Optional: start sound

More information on the formats for input delivery can be found in the following table:

Content and configuration

For content configuration, we need

• Image material for recognition (e.g. jpgs or pdfs of the magazine pages or flyers to be used)
  • Please make sure to send over your desired image material early enough to allow testing by metaio and potential change iterations before going to print.
  • For good recognition and tracking the images need to follow certain constraints, more details can be found here: http://docs.metaio.com/bin/view/Main/UnifeyeMobileMarkerlessConfiguration#Selecting_a_good_target
• Content to be visualized, e.g.
  • videos (should be provided in a higher resolution format like 720p and codec e.g. h264, metaio will then convert and reduce the video accordingly, more information can be found here: http://www.junaio.com/publisher/soundsandvideo)
  • 3D models (should be provided in obj or md2 format with a polygon count suitable for mobile usage, more details can be found here: http://www.junaio.com/publisher/placedmodels)
  • web pages (should be prepared as mobile pages, suitable to be displayed on phones with different screen resolution)
  • sound (mp3 format)

Submission

Once the applications are ready they can be submitted to the Apple Appstore or the Android Market. If metaio should take care of the submission process, we need all the submission details for each store from you, like descriptions, screenshots, submission countries, etc.
Please note, that latest Apple submission guidelines (as of 2011/10/4) ask for clarity with respect to the submitting entity. So it might be reasonable to create your own Apple developer account and share it with metaio so that we can submit the application under your name.

More information on the submission details for Appstore and Android Market can be found here:

http://docs.metaio.com/bin/view/Main/MetaioMobileiOSFAQs#Submission_process_for_the_Appst

http://docs.metaio.com/bin/view/Main/MetaioMobileAndroidFAQs#Submission_process_for_Android_m

Timing

In order to make sure that your applications are available online on time, please include according time for development, testing and submission in your project planning. The following table should be used as guideline.

-- SupportMetaio - 2011-08-05