<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dave Can Code on Medium]]></title>
        <description><![CDATA[Stories by Dave Can Code on Medium]]></description>
        <link>https://medium.com/@davecancode?source=rss-66c92d327814------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TDAIboWUsROUFI8KphmBnQ.jpeg</url>
            <title>Stories by Dave Can Code on Medium</title>
            <link>https://medium.com/@davecancode?source=rss-66c92d327814------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 12:47:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@davecancode/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Magic Leap Human Interface Guide, Part Two]]></title>
            <link>https://medium.com/@davecancode/magic-leap-human-interface-guide-part-two-d3cbe6d0a853?source=rss-66c92d327814------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3cbe6d0a853</guid>
            <category><![CDATA[virtual-reality]]></category>
            <dc:creator><![CDATA[Dave Can Code]]></dc:creator>
            <pubDate>Mon, 24 Sep 2018 03:35:25 GMT</pubDate>
            <atom:updated>2018-09-24T03:35:25.155Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the second article in a two-part series outlining the Magic Leap Human Interface Guidelines. For the most up-to-date information, more examples, and in-depth explanations, be sure to check out the <a href="https://creator.magicleap.com/learn/guides/design-principles">Magic Leap documentation</a>.</p><p>In this second part, we’ll go over the Lumin OS conceptual framework and common interaction patterns for the platform. In <a href="https://medium.com/@davecancode/magic-leap-human-interface-guide-part-one-9b04875c065a">part one</a>, we covered general style best practices and discussed the native Lumin components.</p><h3>Framework</h3><p>The Magic Leap framework outlines general design principles covering core concepts when developing for the platform. This section covers a handful of these concepts to provide a consistent experience for apps from the wide variety of developers. It should be expected that these guidelines will evolve over time so check the documentation and forums regularly for the latest recommendations.</p><h3>Landscape</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*cvgCyG4QnBc9eN5q" /></figure><p>Landscape apps are persistent and analogous to running multiple applications on a laptop. These apps can be manipulated in 3D spaces and provide a multitasking paradigm as illustrated in the gallery, media player, friends list in the image above. An interesting feature is that these experiences can be casted to other Magic Leap users so two users with two headsets can interact with an app in the same space. At the time this article was written, this seems to be available only to native Lumin apps so you can’t cast Unity apps. However, I’d expect these APIs to be exposed in the future.</p><h3>Immersive Apps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*kJ06ejwf9WehFimQ" /></figure><p>Immersive apps are rendered one-at-a-time meaning any landscape apps will be temporarily hidden and run a minimal set of services in the background. Currently, all Unity apps are rendered as immersive apps. Thought should be given to how users will enter and exit the app as well as provide consistent interactions with landscape apps. Dr. Grordbort’s is one example of an immersive app.</p><h3>Prisms</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*Cx2rOuIJmth9IYgf" /></figure><p>Prisms outline the bounds of an experience and can be used in landscape apps to aid with placement in the environment and can be mimicked in immersive apps as a common interaction model. They should minimize empty space and fit snugly around an experience. Additionally, they should behave predictably when spawning in either app format.</p><h3>Placement</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*vod05ZSSlXLbw669" /></figure><p>A key concept in mixed reality is weaving the physical and the digital world into one seamless experience. The world mesh can be leveraged to create realistic collisions, occlusion, and visual effects that increase immersion for users. Indicators and highlights should be used to provide feedback. Snapping and billboarding are also recommended. At the time of the writing of this articles, the world mesh still seems to be at a very beta level in immersive apps however native system landscape apps are quite good. I’d expect this to improve over time.</p><h3>Persistence</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*g44-9lI9mmtaGIWf" /></figure><p>Once the Magic Leap One has mapped your space, landscape apps placement should persist across sessions. This allows users to personalize their experience space and find their apps in familiar places. Content can be renewed and refreshed periodically keeping the experience fresh and informative. Persistence will fail at some point so think through ways to guide users in those cases with sound and visuals.</p><h3>Privacy + Security</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*Z0vXTxQtkW1CG4-f" /></figure><p>Lumin provides privileges similar to smartphone platforms, allowing users to pick and choose which options to grant to any app. The best practice is to only request privileges necessary for your app to function. Use clear and understandable language when requesting and have a plan for degraded functionality when a user denies or disables a privilege as well as how to guide users through the process of reenabling it through the system menus. Currently, there are about 20 privileges available ranging from Local Area Network to World Meshing.</p><h3>Interaction Model</h3><p>Reliable experiences will provide consistent interaction models that mimic the system. Keep the interaction responsive and always leverage multisensory feedback to reinforce clarity and avoid confusion.</p><h3>Targeted</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*Dl4cGWzaQDrQrF7K" /></figure><p>A common targeting example is to indicate to the user that what is being looked at can be interacted with. The simplest way to achieve this is by raycasting from the headpose. Again, think through the variety of angles users will be looking at content and devise a way to avoid requiring sharpshooting headpose rays. Another common error is the ray passing through prisms and can be alleviated by adding a slightly larger collider or a background collider “layer” for the ray to hit and capture the raycast.</p><h3>Activated</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*fuvzeE2euvgIGS_DKEfJxA.gif" /></figure><p>Activation communicates to the user that they are now about to interact with content in a given experience. Indicate active objects with visual, audio, or haptic cues and then keep the deactivated state quiet, in contrast.</p><h3>Focused</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*7Qi3MUODHYF_MZ5zorvOGw.gif" /></figure><p>Focused objects will receive user inputs. Be clear and predictable to avoid user frustration. Subtle changes, such as modifying z-depth, are best and guide focus in the interaction.</p><h3>Interactions</h3><h4>Content Navigation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*8M4XapRDBp_Zu3QhYJuCwg.gif" /></figure><p>Care should be taken to provide the appropriate input mechanisms for navigating content. Follow common patterns such as pagination and scroll views to minimize clutter, keep things focused, and display additional options. As the focused object changes, one option is to pop objects forward as well as highlight the current item.</p><h4>Selection</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*r_zRuLOxEAlNWz0WrF3lkA.gif" /></figure><p>Inform the user what is selectable by providing consistent, visual cues as to which items are selectable and the current state, such as targeted and focused. Additionally, provide multiple selection inputs, such as trigger or tap on the touchpad, where appropriate.</p><h4>Back and Home</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*s7ss2qZZqWu9D-22lxy-YA.gif" /></figure><p>The Home button is reserved for the system and it should be used minimally, if at all, inside the app. This is less critical in immersive apps as the user will need to long hold the button to go back to the system, consisting of landscape apps. A confirmation dialog might be useful in immersive apps as well. To clarify, pressing the Home button once is considered a back command while double pressing indicates a home command. Experiment and test your control scheme to formulate the best interaction.</p><h4>Manipulation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*TUU5LLND7BY3EZZM" /></figure><p>Users should be able to manipulate content with common actions such as rotate, scale, and distance. Avoid awkward combinations and consider users with smaller hands when designing interactions.</p><h4>Grab and Place</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AhLHtW9zES11Snjm" /></figure><p>Where sensible, allow users to position content in a personalized manner in their environment. Indicate this is possible with visual cues and be mindful of the variety of spaces that will be used.</p><h4>Context Menu</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*GRAsyNDfLe8aB7HF" /></figure><p>Keep things tidy by minimizing options unless until a context menu is requested via user input. This can give users a safe place to explore and learn interactions rather than forcing the discovery of easter eggs. As an example, the bumper is commonly used to invoke context menus on this platform.</p><h4>Text Entry</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VTVupzbAzuV3Wa31" /></figure><p>Minimize the amount of text entry for the best experience. Forcing users to enter large amounts of text is extremely uncomfortable in AR and MR. See the above image for some general guidelines. In most cases, it’s best to utilize voice dictation however manual entry might be unavoidable for entering login credentials. Another option is to QR codes or equivalent image recognition input to avoid manual entry.</p><h4>Casting</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ILfDFPlK6yq9hG7W" /></figure><p>Casting allows users to share and experience content together, when they are all using individual headsets and in the same physical space. Only one cast at time is possible and currently only available to Lumin Runtime Apps, but this could change in the future. If this is something you require, communicate your use case to the Magic Leap team so they can explore and prioritize this functionality for other runtimes, such as Unity.</p><h3>Input Methods</h3><h4>Overview</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Bkz7mEAPeQkbZm6k" /></figure><p>A combination of familiar and novel inputs can create foundation for developing new interaction models and more natural interfaces. As seen above, a wide palate of options are currently available on the platform including headpose, eye gaze, gestures, voice, the Magic Leap One (Totem) controller, the mobile app, and bluetooth keyboards.</p><h4>Magic Leap One Control</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*OnCruSm7PtllgzqV" /></figure><p>The Totem controller features haptics, LED halo lighting, 6DoF tracking, analog and digital buttons, and touch trackpad. Explore each of these options and utilize multimodal feedback to achieve optimal results in an experience.</p><h4>Headpose</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8372x0wv-H3HcGPMPRJgnA.gif" /></figure><p>Headpose can be very effective as humans naturally look and orient our head and view towards things we intend to interact with and signal our attention. Best results are achieved with content at eye-level and close to the user. Since a raycast is used, it can be extremely difficult to sharpshoot distant objects. Be creative in devising alternatives or modifying the raycast, possibly with multiple rays to form a view cone or frustrum.</p><h4>Eye Gaze</h4><p>As implied, eye gaze allows users to interact with content by moving just their eyes. Strongly consider minimizing eye gaze as a core or sole mechanic as it quickly leads to fatigue and cognitive overload. Be very judicious with this technique.</p><h4>Gesture</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*b5wgRacYAfelBd_7" /></figure><p>Gestures can provide an extremely natural way to interact with content. The platform currently supports the commands above and they can be combined to create chords as well. All inputs are raw, so be thoughtful with cool downs between detecting gestures. Be sure to provide alternative inputs as well as relying too heavily on gesture inputs can be fatiguing and error prone. Test, test, test these interactions.</p><h4>Voice</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*aHaecbW8zIl9679cld-28A.gif" /></figure><p>Voice is an excellent choice for text entry and simple commands. Build out simple command trees that mimic the current digital assistants, like Siri on iOS, and leverage cloud APIs to enhance input with natural language, where appropriate.</p><h4>Magic Leap Mobile App</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*ovyddlK3FWoSIxnu" /></figure><p>The Magic Leap Mobile App is downloadable for smartphones and provides an alternative input mechanism, mapping controller functionality as well as enabling more natural text entry. Very useful for testing and prototyping but less useful for end users it can not be expected it will be installed on their phone.</p><h4>Bluetooth Keyboards</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*6oUrO55HP5QQNxW-" /></figure><p>Bluetooth keyboards are another alternative input mechanism which maps controller functionality as well as text entry. Again useful for prototyping, less so for final experiences. Could be useful for enterprise and power users using the device in corporate environments and in the field.</p><h3>Feedback</h3><h4>Interaction Feedback</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*2IDQGrnxseQgEllQ" /></figure><p>Providing interaction feedback is absolutely a best practice. Make feedback multifaceted and utilize the entire palette of tools available such as haptic, visual, and audio. Be careful not to overwhelm users and aim to mimic real world feedback. Use reality as a guide.</p><h4>Loading</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*aHaecbW8zIl9679cld-28A.gif" /></figure><p>As always, minimize loading times and continually strive to improve download and start up times. Provide immediate feedback and consider when to use determinate or indeterminate loading indicators. Think through loading scenarios for app startup, in app content, and at the system level.</p><h4>Dialogs</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-D4pf9_nmw043M3i" /></figure><p>Dialogs typically come in a modal format as a temporary overlay such as system permissions and error states. Be aware of options such as altering z-depth and using legibility masks and blurs to maintain focus, clarity, and readability.</p><h4>Notifications</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gD35xs9YDiJlMxlD" /></figure><p>Notifications are similar to dialogs but do not block the core experience. Some examples might be incoming friend request or temporary network disconnections. Thought should be put into communicating with minimal text and clear iconography. Don’t distract the user or overwhelm them with messaging. Check out the documentation for more guidelines regarding specific components that should be included in notifications. Also, they advise against any advertising. At this time, it’s not clear if that will get you booted from the app store.</p><h4>Null and Empty State</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*uCVdE9ofu0cDbHmE" /></figure><p>Be mindful when designing your experience to include null and empty states. A search result that returns no results or an empty contact list are good examples. Think through components in your app which might have these states and plan early how to handle them.</p><h4>Errors</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YqyNqPqU391c4w2j" /></figure><p>Be aware of each part of your experience that can go badly if an error state is encountered and develop a hierarchy of critical errors that will completely halt the experience and less critical ones that will merely degrade things. Some of these interruptions will completely break the immersion of your experience while others might simply downgrade the interaction temporarily. Create a priority system for errors and communicate error states clearly to users.</p><h3>Conclusion</h3><p>In this article we covered the development framework and interaction models from the Magic Leap Human Interface Guide. In <a href="https://medium.com/@davecancode/magic-leap-human-interface-guide-part-one-9b04875c065a">Part 1</a>, we outlined style recommendations an overview of commonly used components. Be sure to check out the <a href="https://creator.magicleap.com/learn/guides/design-principles">online documentation</a> as it is updated frequently, evolving rapidly, and covers many more of these concepts in even greater detail.</p><h3>About the Author</h3><p>Dave is a software engineer and creative technologist based out of Los Angeles specializing in interactive Unity3d, C#, and iOS mobile development. He’s also available for work in virtual reality, gaming, visualization, and interactive installations. He experiments in computer vision, computational photography, visual effects, and drone videography.</p><p>His educational background includes work in computer science and traditional architecture.</p><p><a href="http://davecancode.com/">http://davecancode.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3cbe6d0a853" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Magic Leap Human Interface Guide, Part One]]></title>
            <link>https://medium.com/@davecancode/magic-leap-human-interface-guide-part-one-9b04875c065a?source=rss-66c92d327814------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b04875c065a</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Dave Can Code]]></dc:creator>
            <pubDate>Tue, 18 Sep 2018 04:13:35 GMT</pubDate>
            <atom:updated>2018-09-24T03:18:00.348Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the first article in a two-part series outlining the Magic Leap Human Interface Guidelines. For the most up-to-date information, more examples, and in-depth explanations, be sure to check out the <a href="https://creator.magicleap.com/learn/guides/design-principles">Magic Leap documentation</a>.</p><p>In this first part, we’ll cover general style best practices and discuss the native Lumin components. In part two, we’ll go over the Lumin OS conceptual framework and some common interaction patterns.</p><h3>Style</h3><h3>Color</h3><p>Color is used to bring focus to elements within your design and tie into your branding. The Magic Leap One uses an additive light model meaning black is not rendered, in other words transparent, and white is brightest color in the system.</p><p>To simulate black areas, it’s suggested to surround the area with light, emphasizing the darker, black areas. In contrast, brighter or whiter areas will create more noticeable visual distortion around content.</p><p>Avoid using gradients as they tend display with significant banding.</p><h3>Audio</h3><p>Sound is an excellent way to draw users into your experience and lead them around a space. For instance, if an item spawns outside field of view, spatial sound can be used to draw a user’s attention towards that area. Sounds can be used to complement movement or animations as well as provide feedback in menus and interactions. Experiment with spatial sounds in the environment to draw focus and headlocked sound for core interactions, such as music or audio for video.</p><h3>Typography</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*3VDjajWeSoi4UnPq" /></figure><p>The system font for Lumin OS is LominoUI and it’s been designed specifically for the Magic Leap One device with a focus on readability. As with all typography, care should be given to selecting an appropriate font size and weight. For longer pieces of text, aim for about 60 characters per line and minimize, if not eliminate, 3D text.</p><h3>Iconography</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*l14s-ak3Ifpqg_UI" /></figure><p>Lumin OS also contains a default icon set of approximately 90 different glyphs. The general design focuses on circles and 45-degree angles. Appropriate sizes, line weights, and negative space should be considered when designing for the device.</p><h3>Animation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*RlszmiYjjpUmdYa5" /></figure><p>Tasteful animations have been included in the operating system and judicious use in your designs can help guide users. Emphasis should be placed on keeping animations simple, smooth, and subtle.</p><h3>Depth</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*KowjHMBg1eoD0XEB" /></figure><p>Personally, my favorite style technique is depth. By layering content and moving the most important content closest to the viewer, experiences can very effectively guide users through complex choices and interactions. Care should be taken to not invoke too many layers, typically no more than four, as well tasteful use of blurring of content behind the current level to increase readability and minimize distraction.</p><h3>Components</h3><h3>Buttons</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*SXqjtoidlfOU-i4k" /></figure><p>A few important things to remember regarding buttons are to avoid crowding the interface and use text sparingly. Use buttons for common actions and relegate less essential functions to other parts of the interface. Text can be difficult to read in AR, so focus on presenting clear icons and fall back to text in more complicated scenarios.</p><h3>Dialogs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k_V5bPqZNQJXjnxi" /></figure><p>Only use dialogs when absolutely necessary and when they make sense contextually. As mentioned in the button section, avoid large amounts of text and focus on clear intentions in the button labels rather than “yes,” “no,” or “cancel.”</p><h3>Dropdowns</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Uvq451OgzKYG0uX5" /></figure><p>Use dropdowns to filter large numbers of options down to a manageable subset and minimize the amount of space required to display them.</p><h3>Images</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*fg_WyoWkfOqwZZVu" /></figure><p>Images work well on grid-based layouts. Additionally, consider responsive layouts which allow the images to flow and resize as required by the layout, similar to responsive web pages. Images themselves can be used like buttons for executing actions however take care in communicating they are interactable. Use of blur, focus, and depth can provide this clarity for users.</p><h3>Input Fields</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*LPCZ6rJA6xPtUNVk" /></figure><p>Minimize text input fields unless absolutely necessary, such as logins and passwords. Raycasting or scrolling keyboards can be a real hassle for users. Try to provide shortcuts, such as numeric or email keyboards or “@gmail.com” keys, where applicable to improve user experience.</p><h3>Labels</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*l4PQqCpF0OhJhojs" /></figure><p>Use standard system styles and an appropriate size and weight for readability. Additionally, use a color background or legibility mask.</p><h3>Legibility Mask</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*zMx5rb3psmRAKRjM" /></figure><p>Legibility masks are semi-transparent colored backgrounds that give text something to be set against in your interface. Masks can be used to improve legibility of text and other elements as well as create a layer between various z-depths of an interface or workflow.</p><h3>List</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*F5O8Yr1vd5-5HeXo" /></figure><p>Lists can be used to reduce the number of options and present a filtered view of data, such as a contact list. Avoid long lines of text and keep the entries short.</p><h3>Loading Indicator</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*YEf2tydBqAdhkfa1" /></figure><p>Use loading indicators to communicate progress on lengthy or asynchronous tasks such as loading data from a web service or downloading files.</p><h3>Panels</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*W4vL83dv01QKCU_t" /></figure><p>Use panels and tabs to group related items and provide a streamlined view of items.</p><h3>Pickers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*QutMiEoMXfsj3Yvi" /></figure><p>Pickers can be used to minimize text input and ensure correct formatting for data entry. Use an appropriate picker for the task, such as dates, numbers, or color selections.</p><h3>Portal Icons</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1pQQIZ6MSz6MnyQ8" /></figure><p>Portal icons are used to identify and launch apps. Creativity can be leveraged here to animate the content, provide depth into the portal itself, as well as communicate a simple preview of the application.</p><h3>Scroll UI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*chOWSY2wMvvwuYzj" /></figure><p>Scrollbars can be used to display extra content in a given content well. Thought should be given as to where to clip content as displaying part of the next row or page can help the user identify there is more content to scroll. The view port is also wider and can allow for more content horizontally so be sure to consider that space in layouts.</p><h3>Selectors</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NfOj3PKcJdG7N43g" /></figure><p>Selectors allow for the selection of one or multiple options. Radio buttons enforce one choice out of many while checkboxes can be used to select multiple items.</p><h3>Sliders</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*HJcXVet-Bh9kTQm6" /></figure><p>Sliders can provide a variety of interesting interface interactions. A few common examples are horizontal, vertical, radial, range, and toggles.</p><h3>System Keyboard</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dDfoSKKGF9IkFzfT" /></figure><p>Lumin OS provides a software keyboard to enter text in native applications. Check out the <a href="https://magicleaphelio.com/">Helio</a> browser and wifi settings to see examples on your system.</p><h3>Toggles</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*Xp1sdqAcFtNXMREC" /></figure><p>Toggles can be used in a variety of compelling ways, namely switches and icon buttons.</p><h3>Conclusion</h3><p>In this installment we covered the style recommendations and an overview of the most commonly used components from the Magic Leap Human Interface Guide. In Part 2, we’ll dive deeper into the Lumin OS conceptual framework and common interface interactions.</p><h3>About the Author</h3><p>Dave is a software engineer and creative technologist based out of Los Angeles specializing in interactive Unity3d, C#, and iOS mobile development. He’s also available for work in virtual reality, gaming, visualization, and interactive installations. He experiments in computer vision, computational photography, visual effects, and drone videography.</p><p>His educational background includes work in computer science and traditional architecture.</p><p><a href="http://davecancode.com/">http://davecancode.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b04875c065a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Started Developing with Magic Leap One and Unity]]></title>
            <link>https://medium.com/@davecancode/getting-started-developing-with-magic-leap-one-and-unity-70abe9e5ab01?source=rss-66c92d327814------2</link>
            <guid isPermaLink="false">https://medium.com/p/70abe9e5ab01</guid>
            <category><![CDATA[virtual-reality]]></category>
            <dc:creator><![CDATA[Dave Can Code]]></dc:creator>
            <pubDate>Wed, 05 Sep 2018 01:52:11 GMT</pubDate>
            <atom:updated>2018-09-05T01:52:11.391Z</atom:updated>
            <content:encoded><![CDATA[<p>This tutorial will quickly point you in the right direction to get everything you’ll need downloaded and installed. After you have access to the creator portal, download and install the package manager, install the SDKs and packages, install the IDE. Once everything is installed, you can explore the examples, tutorials, and samples as well as start configuring your own builds.</p><p><strong>Register for Creator Portal Access</strong></p><p>This step is simple: register for an account at the <a href="https://creator.magicleap.com/">Magic Leap Creator Portal</a> so you can access other materials in this guide.</p><p><strong>Install the Package Manager</strong></p><p>Once you’re registered in the portal, you can start downloading the various software you’ll need to start developing. First off, you’ll need the <a href="https://creator.magicleap.com/downloads/lumin-sdk/overview">package manager</a>. Pick your operating system and run the installer. The package manager will help you download SDKs, profilers, and debuggers. For this tutorial, we’ll be using the Unity packages but there are also Unreal and native Lumin packages as well. After installation, open the package manager which will greet you with default install locations on your file system so you can track down these files later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BGnI2elL6jiiZe2L" /></figure><p><strong>Install Common Packages</strong></p><p>For the common packages, you’ll need to install the Lumin SDK at a minimum. You also will have the option to install thermal profilers, graphics debuggers, and IDE extensions from this section of the package manager.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gOAwZhUAmYONDRmC" /></figure><p><strong>Install Unity Packages</strong></p><p>Next, scroll down in the package manager and install the Magic Leap Unity Package. You can optionally install the Unity API documentation as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*06cPjINE2jG2pAM9" /></figure><p><strong>Install the Magic Leap version of the Unity Editor</strong></p><p>Special builds of the Unity IDE are available on the <a href="https://unity3d.com/partners/magicleap">Unity site</a>. Download and install this next to any existing version you have installed on your system.</p><p><strong>Download API Examples, Lessons, and Tutorial Projects</strong></p><p>In the SDK you downloaded earlier are included a variety of starter scenes to get you up to speed on developing for the Magic Leap One. In the creator portal, these are referred to as <a href="https://creator.magicleap.com/learn/guides/sdk-examples-landing-page">API Examples</a> and provide a crash course to developing on the platform. These examples include the controller, hand tracking, image tracking, meshing, planes, raycasting, the media player, the mobile app, image capture, video capture, and persistence.</p><p>Additionally, Magic Leap has made available the following for download from the creator portal:</p><p><a href="https://creator.magicleap.com/learn/guides/abductor-sample">Samples</a> — These projects focus on a specific topic such as meshing, gestures, or vignettes.</p><p><a href="https://creator.magicleap.com/learn/guides/magickit-overview">Magic Kit</a> — The goal for these samples are to provide complete, tiny concepts for developing in mixed reality and combine a number of concepts into one more complete app.</p><p><a href="https://creator.magicleap.com/learn/guides/goat_labs-welcome">Studio Spotlights</a> — These are yet larger projects highlighting work from specific studios, the first of which is an internal team at Magic Leap: Goat Labs.</p><p><strong>Creating a Unity Project</strong></p><p>Get used to the following set of steps since you’ll be doing this over and over again for any of your Unity projects.</p><p>Open the Magic Leap version of the Unity IDE.</p><p>Open an existing project or create a new one — we’ll assume you’re just getting started with API examples so create a new project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BLCzo50H81cD2fMb" /></figure><p>Open the Build Settings window and select Lumin OS as the target platform.</p><p>Click “Switch Platform” (this will take a few seconds to a few minutes)</p><p>Check the “Sign Package” checkbox</p><p>Click the “…” button to set your Lumin SDK location from the install earlier.</p><p>Click the “Player Settings” button</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jJg0XHFuneqH2X8t" /></figure><p>In the Player Settings window, you’ll need to select your development certificate under the Publisher Settings section to sign your builds for the Magic Leap One hardware. If you don’t have one, follow the <a href="https://creator.magicleap.com/learn/guides/developer-certificates">instructions</a> on the creator portal.</p><p>Additionally, you can check the boxes for privileges your application will require at runtime.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/0*rZFEh2wmQ2drmB0U" /></figure><p>Finally, import the Magic Leap Unity Package downloaded earlier via the package manager. This will install a bunch of starter code and the API example scenes (this could take a few seconds or minutes).</p><p>At this point, pick a scene and fire it up in the editor or try it out in the <a href="https://creator.magicleap.com/learn/guides/tools-magic-leap-remote">Magic Leap Remote</a>. If you’re fortunate enough to have the hardware, go to File &gt; Build &amp; Run to send the current build to your headset (be sure to include the scene in your Build Settings window and you’ll need to set an output location the first run for you built .mpk file).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/0*jGpa1mwobQW1Dvus" /></figure><p><strong>Troubleshooting</strong></p><p>The most important thing is to make sure the Lumin SDK, Unity Asset Package, and Unity IDE are all on the corresponding build, especially during early beta access as APIs are changing frequently. Carefully read any output in the console window as it can provide helpful clues when things go wrong. Also, keep an eye out for changes announced in the creator portal and the forums.</p><p>Getting started can take an hour or so to get everything downloaded the first time. After the initial download, use the package manager to update the SDKs and Unity packages. Occasionally, you’ll need to download a new IDE version. Pay attention to messages and forums for updates to certificates that may invalidate the one you’ve already downloaded, although this is rare.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70abe9e5ab01" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Common Augmented Reality Mistakes]]></title>
            <link>https://medium.datadriveninvestor.com/3-common-augmented-reality-mistakes-6ff5c08fa3cf?source=rss-66c92d327814------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ff5c08fa3cf</guid>
            <category><![CDATA[virtual-reality]]></category>
            <category><![CDATA[augmented-reality]]></category>
            <category><![CDATA[magic-leap]]></category>
            <dc:creator><![CDATA[Dave Can Code]]></dc:creator>
            <pubDate>Wed, 29 Aug 2018 02:30:00 GMT</pubDate>
            <atom:updated>2018-08-29T02:30:00.907Z</atom:updated>
            <content:encoded><![CDATA[<p>Here are three common mistakes I see people make when the first get started in augmented reality. As you’ll see, they’re easy to avoid once you know what to look for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9YdwBxDpfeD8o446EaFijA.jpeg" /></figure><h3>Trying to do 2D apps but in 3D</h3><p>The most common mistake I see being made in this first round of content is trying to force a 2D app idea into the 3D paradigm. Typically this involves envisioning some standard, flat smartphone app as something you stick on a wall or a table in AR — essentially just a lift and shift from PC or phones. Common examples include an animated calendar app on the fridge or a wall of tweets. The challenge is to venture outside these standard designs and explore the concept a bit. Rather than simply recreate physical items in the digital realm, try to develop an experience that creates an entirely new way to accomplish a task. You have space now, so use it! Turn that boring agenda view of someone’s schedule or a todo list into a virtual Candyland with different boss types to represent various meeting types. The same technique applies to everything you’d find on a smartphone fresh out of the box. Phone call? Create a futuristic video chat wall. Text message? Throw emoticons at an avatar representing the other person. New interactions should be created for every common task you would normally use your phone for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*POoBjAtlVfU4T5Q7HN998Q.jpeg" /></figure><h3>Mixing control/engagement models</h3><p>Another common pitfall is getting lost in the various engagement models in AR. This is the biggest advance in consumer technology since the original smartphones started rolling out. People are already getting lost in the interaction models now available. Do you use raycasts from the controller? What about gaze? How about the touchpad on the controller? Should hand gestures be used? There are a lot of new options to consider. Amateurs will attempt to use all of these modes simultaneously in an experience rather than picking one or two that make the most sense for an experience or objective. Gaze is great when you have someone focused on facing and looking at large virtual objects which make for easy targets. Gestures can be leveraged effectively when you want to quickly send an input, such as switching a song or a video on a playlist. Old fashioned raycasting is a tried and true method for many interactions but avoid forcing people to sharpshoot targets like keyboards, checkboxes, or tiny buttons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g2Y0yR_lg9nPgYpEDIXT8w.jpeg" /></figure><h3>Not embracing the medium</h3><p>My personal summary of AR is “a feast for the senses.” Modern platforms such as HoloLens and Magic Leap One offer a wide selection of inputs and feedback mechanisms making the augmented world more of a reality, drawing people into the frame of the virtual universe you’re attempting to communicate and tying them emotionally into the content as well as the environment. Input mechanisms can range from controllers, to gaze, to eye tracking as well as gestures, voice commands, and even image recognition. Feedback mechanisms such as sound effects, visual effects, or haptics in addition to environmental cues like lighting and music help cement the user into your experience. Particle effects and shaders can be used to provide some visual flair for successful actions or reduce cognitive load in busy locales. A great place to look for inspiration is video game level design and in-game tutorials. Observe how each of these experiences are used to provide focus and guidance to people who are new to the world being explored.</p><p>If you’ve gotten this far you no longer have an excuse to make these mistakes. Now go forward, build amazing things, avoid these pitfalls, and make some magic!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*hjkpw9GdK9V11Hx4Ug3AKQ.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ff5c08fa3cf" width="1" height="1" alt=""><hr><p><a href="https://medium.datadriveninvestor.com/3-common-augmented-reality-mistakes-6ff5c08fa3cf">3 Common Augmented Reality Mistakes</a> was originally published in <a href="https://medium.datadriveninvestor.com/">DataDrivenInvestor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>