Log in or register to post comments

Troubleshooting advice for app end users

July 20, 2012 - 7:17am #1

I'm involved in a project developing an AR app for an agency client. They've asked me to provide some information for a 'help' page for the app. I know apps don't usually have help pages, but bear with me...

The only things I can think of that could go wrong with an app that an end user could do anything about, would be low light or too much light reflecting on the AR marker. Is there anything else I've missed?

Do Qualcomm / Vuforia offer any standard guidelines to end users for troubleshooting if their app doesn't work as expected?

I've tested an app in low light conditions and it's really solid - has to get *seriously* dark before it starts to fail. Haven't checked for glare / reflections yet...

I've told the client that we should aim not to have a help page. However, it may be relevant for us to include a message such as "No 3D model? Make sure that <some_helpful_wording_here>".

Many thanks in advance,

Andy

Troubleshooting advice for app end users

July 23, 2012 - 9:34am #3

The Developer's Guide has some helpful information in this regard - https://ar.qualcomm.at/qdevnet/developer_guide/ .

Take a look at the sections on Trackables and AR App Design.

The critical factors related to user experience are going to be lighting, distance, occlusion, and perspective. As you've noticed, the tracking will tolerate a broad range of lighting conditions, but will work best w/ illumination appropriate for reading (e.g. you'll see quicker target detection in this range). Glare and reflection tend to blow-out a/o confuse the regions of the image that they affect, which will impact detectability and tracking. But this typically isn't a significant issue unless you're using a glossy print media and bright direct lighting on the target.

Some basic troubleshooting tips for users are ..

1. Make sure that you can see all of the details of the image clearly on screen, and that the entire image is in view.

2. Try viewing the image at a slight angle.

These will ensure that the target is detected. If the details of the image are clear to the human eye, they will be apparent to the Tracker, and if the entire image is in view on screen, then all of the image's features will be available to the Tracker. One problem that I've often seen new users encounter, if they are unfamiliar with AR, is that they'll place the camera too close to the target. This reduces the area of the image captured by the camera.

Number 2 can be helpful with marginal targets because tracking actually benefits from some perspective distortion.  Also novices will sometimes assume that the camera has to be parallel to the plane of the target, or directly over the target's center. This impacts their user experience because they're not moving the camera freely. So telling them to view the target at an angle helps to dispel this assumption.

Feel free to PM me your doc if you'd like some feedback on it.

 

 

 

Troubleshooting advice for app end users

July 23, 2012 - 6:49am #2

That's really helpful advice - many thanks.

Log in or register to post comments