Introducing Zappar WebAR


#1

You may have noticed that since our latest major ZapWorks update, we’ve begun talking about our mobile WebAR beta - particularly if you’ve been involved in the recent discussions on the ZapWorks community forum.


This is a companion discussion topic for the original entry at https://www.zappar.com/blog/introducing-zappar-mobile-webar/

#2

Is WebAR already compatible with IOS and Safari?

Thank you


#3

Just tried the WebAR with my existing content (created in ZapWorks Designer) however I am getting limited content - namely sound, and a couple of interactive buttons. No video/animation, no images or photo albums, no ‘e-card’ - tried it out on an AR book page and also two business cards. I used iOS 12.3.1 Safari on iPhone X


#4

Tried it with my existing content, one project in Studio and one in Designer - neither are showing video. One is a business card, one is a magazine layout.

iOS 12.1.4 Safari, iPhone 7 Plus


#5

In my case I can say that the new IPOD Touch works well:

But not in my previous iPOD Touch 9.3.X

So it would be ideal to indicate from what version or device WebAR is compatible.


#6

IPhone 7 Pro here. Good times with the Webar!

One of my experiences, an interactive 3D Godzilla, worked flawlessly! Our Ghost Game, which makes use of world,positioning, only got so far before choking. I get it: beta!

The Zapteam has worked so hard and so quickly over the last year, I have no doubt it will accommodate all content soon.

One suggestion: make the webar UX more seamless. Perhaps eliminate the button they need to click on first loading an experience.

Also, I scanned a QR code and then had to scan my Zapcode. Perhaps confusing to the user. Can this be made easier?

Great work, and vital I think in keeping Zapworks alive. Very exciting.


#7

Hi everyone - thanks so much for all the feedback and sharing your experiences with Zappar WebAR. It’s incredibly useful for our development team, so we’ll be pouring over it and getting back to you all soon. As this is still very much a beta, there’ll be some inconsistencies between different models of phone, but we’ll be looking into this as we go and as more users report their experiences to us :).

@donnav - on the ‘launch’ button for launching the scanner, this is an Apple requirement. There needs to be an explicit action by the user in order to access the device camera, so we would be unable to remove this I’m afraid.

If the QR code is set up to launch the WebAR deeplink, then the experience will launch automatically without having to scan the zapcode. Check out our documentation here for more info: https://docs.zap.works/general/launching-experiences/