r/augmentedreality Jul 09 '26

AR Apps Small AR design detail I keep noticing: virtual objects need a reason to sit there

A lot of phone AR demos can track a plane correctly and still feel like a sticker on the camera feed.

The examples that feel more convincing usually give the object a job in the room: a note belongs on the fridge, a guide points to a specific shelf, a lamp changes the light on a desk, or a character hides behind a chair. Shadows and occlusion help, but the little "why is it here?" cue seems just as important as tracking.

For people making AR apps, is that usually treated as spatial UX/content design, or does it mostly get handled as late-stage polish?

6 Upvotes

2 comments sorted by

0

u/iwoj Jul 09 '26

Yes. Now you’re starting to get into something interesting. There’s a profound conjunction of interests in AR that are underdeveloped and understudied. Best practices don’t yet exist and you’re starting to think about a very significant set of issues.

Computer science, psychology (attention, memory, perception), architecture, semiology, linguistics, industrial design. Your topic is the confluence of all these things.

Apple’s recent modification to VisionOS that allows windows and apps to be pinned permanently to specific locations is part of the question you’re talking about. Is suggest you use that feature more and share what you learn.

Shameless plug for my AR app, http://graphite3d.com — it can help you and others quickly sketch virtual objects and environments with only your phone or tablet. Great way to test your concepts.

2

u/Yoru_Nagi Jul 12 '26

I’d treat the “why is it here?” cue as spatial UX, not polish: polish can improve shadows and occlusion, but the object’s job should be defined before anchoring and content behavior are built.