When To Use QR-Code vs. Thingmark

[BenAtLmco]

Hello!  I had a question about when it is appropriate to use a Thingmark vs a QR-code to load an experience.  Is it best practice to use one over the other in certain circumstances?  Are they both equivalent?

My rough understanding is that Thingmarks are good for experiences that will also be using a Thingmark for tracking, but that QR codes may be a better solution for experiences that use model targets.  What are the advantages/disadvantages of using either method from your perspective?

There's been some disagreement on my team about which method is best under which circumstances, so we wanted to ask the experts!

[sdidier · Accepted solution]

Hello BenAtLmco,

A QR Code is unique to an Experience. I would mean by unique a same Experience published in various Vuforia Experience Service will have different QR Code. 

A ThingMark can be linked to open various Experiences or to in various Views to place 3D Model.

Be carreful, a ThingMarks has this filename format and code inside it Domain-ID:ThingMark ID.

So, a ThingMark is linked to a specific Vuforia Experience Service environment.

At the end, a QR Code and a ThingMark are linked to a Vuforia Experience Service environment.

It is important to keep in mind that when migrating Experiences between environments.

Use QR Code or a ThingMark to open an Experience doesn't have any impact in View, in 3D Canvas, when using any Target.

So, we don't have any best pratices to use QR Code and ThingMark.

The only difference is QR Code is unique to an Experience.

Best regards,

Samuel