Develop Your First Vuforia Studio Experience

  Download Success Path IMPORTANT: When saving the file, in the Print window please do the following:
Destination or Printer: select Save as PDF
More Settings: In the Options, be sure the boxes Headers and footers and Background graphics are selected.
Recommended Steps
Overview: Develop Your First Vuforia Studio Experience

Test the Augmented Reality Experience

At this phase, you’ll have a well-developed AR experience that you’re confident functions properly. Preview the augmented reality experience in a real environment. Verify it performs correctly in the real world and is usable before deploying it to the entire organization.

01. Set up development environments

If you have not done so already, set up the development environments required to test and deploy your AR experience. This step differs, depending on whether you’re deploying Vuforia Studio via PTC-hosted cloud or on premises.

02. Perform field testing

Before you deploy AR to your organization, test it under the circumstances or in the environment where it will be used. The purpose of field testing is to find and fix any issues that may arise in a real-world setting. For example, if service technicians will use AR in a factory, test it in the factory—where the wi-fi signal may be less dependable or other factors may make AR more difficult to use.

At this point in the project, you’ve tested the AR experience multiple times. Ideally, you’ve already discovered and addressed most flaws. Still, we recommend scheduling time between field testing and deployment to resolve any issues you may discover.

Perform several test scenarios—try to launch, use, and exit the AR experience; and attempt to add a new user, for example.

Test and verify:

  • Functionality: Does the AR experience function as designed? Can you see all the information you need? Do the components on the screen maintain the proper position as the user moves?
  • 3D models: Do digital 3D models fit the corresponding physical objects when overlaid on top? Do they scale to the correct size?
  • Integrations: Is data flowing between the AR experience and any connected systems?
  • Performance: Is the speed acceptable?
  • Connectivity: Is the wi-fi signal strong enough?
  • Devices: Are the devices you’ll use to view AR experiences working as planned?
  • Tracking: Does the AR experience launch properly? For example, if using model tracking, does the AR experience recognize the object and launch the correct AR experience?
  • Usability: Is the AR experience intuitive to use?

Stress test the system to ensure it can support the inflated population of users who will use the experience after deployment. Simulate several scenarios—including less-likely situations when the system is processing more data than expected.

If you find issues, decide whether to pause deployment until they can be resolved. Depending on the severity of the issue(s), you may choose to deploy AR as-is and fix them later.

03. Conduct user acceptance testing

Test the AR experience with the employees who will soon use it as part of their process. If possible, involve a diverse range of employees from the organization—include people familiar with the depicted process and people learning it for the first time. It’s crucial that you involve employees whose jobs will be affected by AR.

Foster an open environment where employees feel comfortable giving feedback.

Benefits of user acceptance testing:

  • Ensure the AR experience is easy to learn and use
  • Generate excitement and address concerns about AR across the organization
  • Catch last-minute bugs
  • Capture ideas for improvements from people with valuable expertise
  • Ensure the steps in the procedure are captured correctly
  • Obtain early proof of how AR improves upon existing methods

The project leader, UX designer, or other team member can lead this testing. User acceptance testing will elicit invaluable feedback. Document all the participants’ ideas and concerns. Note anything that seemed confusing or difficult to navigate. You may not act on everything prior to deploying AR, but we recommend revisiting this feedback as you expand your AR offerings.

If you find issues, decide whether to pause deployment until they can be resolved. Depending on the severity of the issue(s), you may choose to deploy AR as-is and fix them later.

We recommend you also capture suggestions for expanding AR. Participants may have ideas about procedures, processes, and areas of the business that could benefit from AR technology.

Did you find this helpful?


Previous Step

Compile Documentation

Next Step

Roll Out to End Users

ADDITIONAL RESOURCES

Product Documentation Find detailed technical documentation on Creo+ in our Help Center
Ask the Community Visit PTC's Creo Community to get support Peer-to-Peer, from our product management and assistance teams. Share ideas, give feedback and browse the wealth of information on using Creo+
Technical Support Need help from our support team? Log a case with eSupport using our Case Logger or find an answer using our new Creo Admin Troubleshooter tool. 

Contact Us

Have a question? Submit your contact information and we’ll reach out within 1 business day. You’re never obligated to purchase or commit.
Get in Touch
Cancel
Confirm
  • English
  • 中文 (简体)
  • 中文 (繁體)
  • Français
  • Deutsch
  • Italiano
  • 日本語
  • 한국어