Previewing and Publishing

Throughout development in Designer you'll want to test your experience on a mobile device. We recommend testing regularly to catch any bugs or issues that you might have accidentally added to your experience.

In the top-right hand corner of Designer there are two buttons: Preview and Publish.

Previewing

Clicking the Preview button will open a Preview Modal where a test QR code and target image will be displayed.

Scanning the test QR code using a QR code scanner (built in to most native camera applications) will launch a preview of your experience. Due to Designer experiences being image tracked, you'll then need to point your device at the target image you uploaded at the start of your Designer project (found to the right of the modal).

Preview modal

Scans of preview experiences are purely for testing purpose and do not count to CPV or analytics.

The test QR code should not be used on your target image or print material as it's only activate for 5 minutes. Please use the trigger assigned to your project.

Publishing

When you have tested your experience and are happy to distribute it, you can click the Publish button. This will deploy your experience to your QR code trigger. You can now share the QR code and target image enabling your end users to scan and launch the experience.

It is recommended that you add the QR code to your target image. To find what makes a good tracking image, check out this article

To check if the experience has been published successfully, you can find a green 'Published' indicator at the top of the scene.

Distribution Methods

Experiences developed using Designer are built to target WebAR and will be launched on a zappar.io domain. All Designer experiences will launch into a Zappar branded splash screen which will prompt users to enable permissions when the launch button is tapped. Designer experiences do not support the Lite Branded Splash Screen or Custom Branded Splash Screens.

Zappar branded Designer splash screen

The launch button is necessary due to browser restrictions as we need a ‘user-initiated event’ in order to:

  • Request permission to access device motion data
  • On some platforms, to request permission to access the camera
  • To play audio

Next article:Keyboard Shortcuts

zapcode branded_zapcode i