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

Roll Out to End Users

After performing a final test, you’ll be ready to deploy augmented reality and make it available to end users. Execute the rollout plan you created earlier in the project.

01. Administer credentials to users

Ensure everyone who will use AR has permission to access the AR experience. This step is not required if your AR experience is “public,” in which case no login is required to access and view it.

If your AR experience requires users to log in, provide them the necessary credentials. Earlier in the project, you set up user accounts for administrators and developers (perhaps others, depending on your situation). Now, follow a similar process to create credentials for end users.

If your organization is using single sign-on, work with your IT team to configure and implement it. See the “Prepare for Single Sign-On” chapter of the Installing and Deploying an Experience Service document for more information. Ensure everyone who needs to use AR experiences can successfully log in and access them.

Use ThingWorx Composer to administer user credentials. Use the production environment. Create usernames and passwords for all employees who will use AR. Then, add them to the “Developers” group. Ensure they can successfully view AR experiences using the Vuforia View app.

In many cases, Vuforia View users will also need your organization’s Experience Service URL to view AR experiences. The Experience Service is a secure server where your organization’s AR experiences are stored.

If you’re deploying Vuforia Studio via PTC-hosted Cloud, you’ll find your Experience Service URL in the cloud fulfillment email. If you can’t find this information, contact your organization’s IT team. If they don’t have the email, log a support case with PTC technical support.

If you’re deploying Vuforia Studio on premises, you’re responsible for installing the Experience Service. Your IT team will determine the hostname/IP address where it’s installed.

Recommended Resources

02. Train end users

Ensure everyone who will use AR has the knowledge they need to get started. Follow the training plan you created earlier in the project. End users include anyone at your organization who will use AR to do their jobs. End users will need access to the Vuforia View app and your organization’s chosen device (mobile device, tablet, and/or eyewear devices) to participate in training.

As you conduct training, monitor whether your approach is effective. You may discover end users need more or less guidance, or a different format to learn how to use AR.

Ideally, employees have been notified in advance that the organization is adopting this new solution.

03. Train help desk

To reduce downtime and achieve your project goals, Vuforia Studio and Vuforia View users should know where to go for technical support. Prepare your IT department to support employees using Vuforia Studio and the Vuforia View. PTC recommends establishing a “help desk” within your IT department. Help desk personnel should complete Vuforia Studio training so they’re prepared to answer basic questions and troubleshoot issues.

In cases when the help desk is unable to resolve the workers’ issue, PTC offers technical support: your organization’s Vuforia Studio administrator may log a case with PTC eSupport. Once received, a member of the technical support team will assist them.

Recommended Resources

04. Promote to production

If any issues arose during field and/or user acceptance testing, re-test to ensure they’re fixed. After you have performed all the necessary testing, you’re ready to migrate the experience to a production environment. This step “publishes” your AR experience—making it available to the employees who will use it. Ensure you have a backup in place before promoting to production. If you followed a thorough DevOps process, your work should already be backed up.

To promote to production, the developer will move the code to a production server.

Depending on your use case, you’ll migrate various items to production:

  1. The AR experience: Migrate the AR experience from Studio to your production Experience Service.
  2. ThingWorx entities: If your AR experience incorporates data from other systems or tools, you must migrate the associated ThingWorx entities to production.
  3. Systems or tools: If your AR experience incorporates data from other systems or tools, there may be code within those systems that must also be migrated to production.

Once the application is deployed, notify the project team, stakeholders, and end users. The AR experience is now is available for use.

05. Perform final testing

After you migrate the AR experience to a production environment, test and verify it works correctly. Stress test the system to ensure it can accommodate all your users. Monitor the system closely for a few days after deployment.

If an issue arises, do not make changes to the application in the production environment. First, make adjustments and test them in the development environment. Second, promote the code to the test/QA environment (if you have one) and test thoroughly. Third, promote the code to production.

Did you find this helpful?


Previous Step

Test the Augmented Reality Experience

Next Step

Evaluate the Project

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
  • 日本語
  • 한국어