I’m working with our Senior AR Developer, Chris, this week on a new blog that’s designed to support the ZapWorks community in optimizing their AR experiences.
It’s going to focus on general tips and Studio functionality that helps keep the package size of your AR experience down, while still delivering really cool, informative experiences for your users.
Would be great to know:
Are there any particularly aspects of AR optimization that you’d like to know more about?
What are some of the techniques you use that the community could benefit from?
Look forward to hearing your thoughts - hopefully this will be a really useful bit of content for the ZapWorks community <3. Any feedback or topic suggestions for future blogs, always welcome .