<p>Published on <a href="https://blog.prototypr.io/design-principles-for-augmented-reality-32fb6ef8394e?source=rss----eb297ea1161a---4">| Prototyping: From UX to Front End &mdash; Medium</a> Skjoldbroder </p>
<h4>“How Might We use Augmented Reality — Part 2”.</h4>
<p>There are many great suggestions for how we might use Augmented Reality (AR). <a href="https://medium.com/u/1608f116ad21">Luke Wroblewski</a> initiated a super interesting conversation about this, and ideas are pouring in from designers worldwide.</p>
<p><a href="https://blog.prototypr.io/how-might-we-use-augmented-reality-part-1-45d7e9fed4e9">In an earlier article</a>, I categorised some of these ideas and came up with a bunch of new ones based on these categories.</p>
<p>Afterwards, I wondered whether AR would be <em>necessary</em> to implement these ideas. You could do it with AR — but would it actually be better than existing alternatives? Or would it be a gimmick?</p>
<h4>What can AR do better than anything else?</h4>
<p>If we want to make killer AR apps / services, I think we need to answer some fundamental questions, such as:</p>
<ul>
<li>what utility/value can <strong>only</strong> AR provide?</li>
<li>what user needs can AR fill <strong>better</strong> than any other technology?</li>
<li>which user segments can benefit the most from AR?</li>
</ul>
<p>To try and find possible answers to these questions, I did an ideation session with my friend <a href="https://medium.com/u/cf6865f6ce9f">Heine Gundersen</a>. The results are in this <a href="https://coggle.it/diagram/WYysLOaoXgAB95M2">mind map v2</a> (and below, in the image). I don’t claim that these results are “The Truth” — merely that they are a contribution to the conversation.</p>
<p><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aVjs959h4HU1jJ3UrnTQZg.png">via coggle.it (an online mindmapping service)</p>
<h4>Design Principles</h4>
<p>I think the following could be valid principles for designing for AR:</p>
<ul>
<li><strong>AR is good for showing information “for your eyes only” </strong>—<strong> </strong>could be for privacy reasons, or because others don’t need to see it)</li>
<li><strong>AR is good for showing information that can best be understood in context</strong> — e.g. overlaying assembly instructions on a motherboard so you can mount the CPU correctly, or inserting virtual furniture into your house so you can see how it would look, walk around it, etc. This is pretty classic AR.</li>
<li><strong>AR is good for situations where information changes frequently, and you need computational power to process data fast enough </strong>— e.g. you are watching a movie in Paris. The audio and subtitles are in French. AR could enable you to get realtime English translations overlaid on a dynamic situation</li>
</ul>
<p>I should note that I think the three principles apply to visual augmented reality only. Because we might also use audio or tactile information (force feedback) to augment reality. For example: a GPS app using audio to tell you which lane to take on the freeway, is a technology adding information to reality = augmenting reality.</p>
<p>Perhaps this should also be a part of the discussion about AR?</p>
<h3>Thanks for reading! Please do leave a comment, suggestion or ideas if you have thoughts about ways to make cool Augmented Reality stuff</h3>
<p><img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=32fb6ef8394e" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou"></p>
<hr>
<p><a href="https://blog.prototypr.io/design-principles-for-augmented-reality-32fb6ef8394e">Design Principles for Augmented Reality (Part 2)</a> was originally published in <a href="https://blog.prototypr.io">prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>


Design Principles for Augmented Reality (Part 2)

“How Might We use Augmented Reality — Part 2”.

Top Stories