Updated Signatures

If you use recording and/or playback signatures to increase the security of your CameraTag products you will need to update your signatures when upgrading to v16. You can read all about the new signature process in the app signature docs

Splitting The CameraTag Products

We have traditionally bundled all of the CameraTag embeds (camera, microphone, photobooth, player, wall, photo) into a single JS file which contained a single JS Class named CameraTag. The time has come to give each product its own JS file and its own JS Class. Starting with v16 each CameraTag embed can be loaded separately. This will slightly change the JS API: moving class methods (such as setup, fire, observe) from the previous monolithic CameraTag class into the new product specific classes. Below is a before and after example of some simple code to load a <camera> and then fire an alert once it's initialized.

BEFORE:

<script src='//staging.cameratag.com/api/v16/js/cameratag.js' type='text/javascript'></script>
<link rel='stylesheet' href='//staging.cameratag.com/v16/css/cameratag.css'></link>

<camera id="myCamera" data-uuid="[YOUR_APP_UUID]"/>

<script>
  CameraTag.observe("myCamera", "initilized", function(){
    alert("initialized!")
  })
</script>

NOW:
(Note the change of the JS URL from cameratag.js to camera.js and the change of the JS class from CameraTag to CameraTagCamera:)

<script src='//staging.cameratag.com/api/v16/js/camera.js' type='text/javascript'></script>
<link rel='stylesheet' href='//staging.cameratag.com/v16/css/cameratag.css'></link>

<camera id="myCamera" data-uuid="[YOUR_APP_UUID]"/>

<script>
  CameraTagCamera.observe("myCamera", "initilized", function(){
    alert("initialized!")
  })
</script>

New NPM Modules and React Components

We have introduced 12 new packages to the NPM to make including CameraTag in your product even easier.