<?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 Trung Nguyen on Medium]]></title>
        <description><![CDATA[Stories by Trung Nguyen on Medium]]></description>
        <link>https://medium.com/@nttrung91?source=rss-f268bff86090------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*aaE2JvYk5KP-KQwaJkjfiA.jpeg</url>
            <title>Stories by Trung Nguyen on Medium</title>
            <link>https://medium.com/@nttrung91?source=rss-f268bff86090------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:43:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nttrung91/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[The current state of prototyping]]></title>
            <link>https://medium.com/design-bootcamp/the-current-state-of-prototyping-e9a291ebc6ce?source=rss-f268bff86090------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9a291ebc6ce</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[prototype]]></category>
            <dc:creator><![CDATA[Trung Nguyen]]></dc:creator>
            <pubDate>Sat, 16 Oct 2021 03:58:05 GMT</pubDate>
            <atom:updated>2021-10-17T21:44:11.587Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>“If a picture is worth a thousand words, then a prototype is worth a thousand meetings.”– Saying at IDEO</em></blockquote><p>Prototyping is an important stage of the design thinking process because it empowers us to rapidly test our ideas and institute improvements until the design is truly delightful.</p><p>There are two common prototyping techniques: low fidelity and high fidelity prototyping. Depending on the goal of the study, both techniques possess their own pros and cons. In this article, we will focus primarily on high fidelity (hi-fi) prototyping. First, we will talk about the current state of hi-fi prototyping tools and the challenges associated with each tool; and then we will discuss how prototyping with code can facilitate and support the prototyping process.</p><h3>What is fidelity?</h3><p>According to the Nielson Norman Group, the term fidelity refers to “how closely [a prototype] matches the look-and-feel of the final system.” The closer the prototype resembles the final system, the higher fidelity it has. In other words, the more interactions and realistic graphics a prototype contain, the higher the fidelity it has.</p><p>In prototyping, the terms low fidelity (lo-fi) and high fidelity (hi-fi) are often used to distinguish between static and interactive prototypes.</p><h4>Low fidelity</h4><p>Lo-fi prototypes are often used earlier in the design process to quickly capture users’ initial feedback and iterate on them. In lo-fi, speed, rather than completeness, is the key driver.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*stvUEKqdCFtP__GBrWX75A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@amayli">Amélie Mourichon</a> on <a href="https://unsplash.com/photos/zVdUQ0-opSY">Unsplash</a></figcaption></figure><h4>High fidelity</h4><p>Hi-fi is used later in the design phase after receiving user feedback on the lo-fi prototype/design. At this stage, we begin thinking of adding interactions into the design. Depending on the goal and the complexity of the design, the more interactions we add, the higher the fidelity, and the longer time it will take to develop the prototype. But in return, we will receive more faithful and impactful feedback from users because their experience using it more closely resembles the real app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hyO-lxRlkV0AW3sx_CMduA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@bugsster">Taras Shypka</a> on <a href="https://unsplash.com/photos/iFSvn82XfGo">Unsplash</a></figcaption></figure><h3>Prototype tools</h3><p>In recent years, there’s been a proliferation of high-fidelity prototyping tools emerging in the market. These include Principle, Invision, Figma, and Framer just to name a few. These tools have helped simplify the process of creating interactive prototypes.</p><h4>The current challenges and limitations</h4><p>All the hi-fi prototyping tools provide a powerful way for building prototypes. However, they come with challenges and limitations. Let’s explore them:</p><ul><li><strong>Limited interactivity:</strong> all the prototyping tools share one thing in common, which is to add interactivity only to the things we care about. As a result, elements that are not part of the highlight feature are not interactive. The lack of interaction between the key feature and its surroundings prevents us from seeing the entire experience as a whole.</li><li><strong>High learning curve:</strong> implementing more complex interactions can be a challenge to get the hang of.</li><li><strong>The cost of change:</strong> as projects grow in complexity, changes become increasingly costly to make. Additionally, the majority of the tools do not have version control; therefore, an unintended change would cost even more time to revert back.</li><li><strong>Time constraint:</strong> the more complex the design and interactions, the more time required to plan, estimate, and prototype the design.</li><li><strong>Connecting the experience:</strong> as projects grow in scale, connecting the many pages and locating specific frames can become difficult. It’s even possible to accidentally change aspects of the prototype without knowing.</li><li><strong>Doesn’t encompass all interactions:</strong> while code isn’t required for basic interactions in prototypes, more complex interactions will need code.</li><li><strong>Inability to handle logic:</strong> since the prototypes typically lack code, they’re unable to handle logic such as input field validation.</li><li><strong>Lack of support for TV experience:</strong> all prototyping tools support click and touch-based devices. However, none support TV experience. We will explore more on this limitation in the next section…</li></ul><h3>The challenges of prototyping for the TV experience</h3><p>Prototyping for the TV experience inherits all the challenges mentioned above along with other unique challenges and limitations.</p><h4><strong>Focus-based movement</strong></h4><p>Navigating in the TV experience requires keeping track of the focus movement. When the users navigate with the remote control, the focus element moves accordingly. The focus element has the following characteristics:</p><ul><li><strong>Focus state:</strong> Display the indicator as an affordance of which element is being focused</li><li><strong>Awareness of the surroundings:</strong> The focused element is aware of its surroundings and knows beforehand whether it can move the focus left-right-up-down.</li><li><strong>Animation:</strong> Animation is crucial to make the sense of place obvious. The reason is moving the focus using the remote, while sitting far away, requires constant attention. If the focus does not animate correctly, then the users won’t know where the focus lands on, and that will frustrate them.</li></ul><p>In Figma and Framer, we can map keystrokes to fire actions on the prototype, and then use an IR receiver (e.g., Flirc) to map the remote buttons to the keystrokes.</p><p>This approach works for simple designs and interactions. For more complex ones, on the other hand, it will be time-consuming to manually add the focus. Additionally, adding animation to the focus movement, in some cases, may require coding.</p><h3>Prototype tools vs. prototyping with code</h3><p>Both prototype tools and prototyping with code have pros and cons depending on the complexity of the design and interactivity.</p><h4>Simple design and interaction</h4><p>For basic design and interaction, prototype tools appear to be a better candidate because it is much faster to prototype and make changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/1*0moNC8qeBjXx1hKrDvc9OA@2x.png" /></figure><h4>Complex design and interaction</h4><p>For more complex design and interaction, on the other hand, teams may consider prototyping with code because of the better overall score.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/1*PZRUicmzJFNv5w6cjCF97w@2x.png" /></figure><p><em>Special thanks to </em><a href="https://medium.com/u/3f7358e3b75"><em>James Vinh</em></a><em>, Eunsun Mota, and Steve Okamoto for reviewing the article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9a291ebc6ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-current-state-of-prototyping-e9a291ebc6ce">The current state of prototyping</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>