Start a new topic

studio vs target-manager

studio vs target-manager
1 Comment

I have mostly used to create projects; specify a target-image, add augmentations, and export the entire project as a zip file, named

inside this archive are folders; augmentation, js, target and wtc, as well as index.html


However, much to my surprise, I discovered that double-clicking on a target in the "target-manager" UI invokes a completely different, yet very capable UI for adding/editing augmentations for a target.

As well, exporting the resultant project results in a zip file named "".

The archive, "" has a completely different file/folder structure than ""

Can someone help me understand why I would use one-or-the-other as an export for projects/targets?


Login or Signup to post a comment