<?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 Kevin D. Kim on Medium]]></title>
        <description><![CDATA[Stories by Kevin D. Kim on Medium]]></description>
        <link>https://medium.com/@kevindkim?source=rss-88447dabb08d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GALo6indeVbvyLJFGVPEtg@2x.jpeg</url>
            <title>Stories by Kevin D. Kim on Medium</title>
            <link>https://medium.com/@kevindkim?source=rss-88447dabb08d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 04:10:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kevindkim/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 Next Wave of DeFi Users: A UX Research Study]]></title>
            <link>https://medium.com/usegossamer/the-next-wave-of-defi-users-a-ux-research-study-f20f180c23a1?source=rss-88447dabb08d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f20f180c23a1</guid>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Kevin D. Kim]]></dc:creator>
            <pubDate>Sat, 26 Oct 2019 03:04:10 GMT</pubDate>
            <atom:updated>2019-10-28T02:29:11.136Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xiAgvVPGyduYQavOWGGwjQ.jpeg" /></figure><h3>Introduction</h3><p>For the last few months, we’ve been hard at work building and iterating on the alpha version of <a href="http://usegossamer.com/">Gossamer</a>, an Ethereum-based alternative investment platform for the financially savvy consumer. We want to make earning through <a href="https://cointelegraph.com/explained/decentralized-finance-explained">decentralized finance</a> (also known as DeFi) simple enough for the wider investor audience. We’ve started off by integrating Compound to help users easily earn 7–10% APY, but have some exciting new features in the works and plan to launch our public beta soon. In the near future we’ll be sharing more about ourselves, our founding hypotheses, and how we’ve incorporated the takeaways below into Gossamer.</p><p>Back when Gossamer was just an idea, we did a set of 21 qualitative interviews with a diverse set of casual crypto users to understand their financial habits and perception towards DeFi. We’re no strangers to the user experience problem in Ethereum — I’ve previously <a href="https://medium.com/hackernoon/6-principles-for-designing-dapps-for-regular-people-from-a-consensus-18-hackathon-winner-134cdb881cc1">written</a> and <a href="https://slideslive.com/38911919/guerrilla-user-research-for-dapps-step-1-to-mainstream-adoption">spoken at Devcon</a> about it. In that spirit, we’ve compiled our main insights to share with the community.</p><h3>Methodology</h3><p>In July 2019, we conducted 21 user interviews of about 45 minutes each. We asked a variety of closed and open-ended questions about their traditional investing habits, their awareness of the Ethereum ecosystem, and their thoughts on various aspects of new decentralized finance offerings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KW4SuhCpOZ9bHvlN.jpeg" /></figure><h3>I: General investing habits</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*D4sNK3LU5FSiCcj_.jpeg" /></figure><h4>FinTech products (robo-advisors, Robinhood) were the most popular investment tools.</h4><p>We weren’t surprised by the popularity of robo-advisors, who have indicated that tech-savvy millennials with disposable income are their target audience.</p><h4>For younger participants (25 and under), crypto was their first real investment.</h4><p>This cohort grew up during the financial crisis and were still in college when the cryptocurrency market started to take off. These participants felt they didn’t have enough savings to make traditional investing worthwhile pre-crypto boom, but were drawn into crypto investing for the potential of sky-high returns. A few younger participants admitted that after losing money in crypto, they took a serious look at more “responsible” investments, like robo-advisors or individual stocks.</p><blockquote>“I only had a couple of hundred dollars in my bank account. Earning 2% [a year] wasn’t worth the hassle of opening a new account but crypto returns were crazy, so I jumped in head first.” (23, M, Marketing)</blockquote><blockquote>“After I lost money in crypto, I realized I should try less risky forms of investing. It was a wake-up call for me to become more responsible.” (24, M, Engineer)</blockquote><h3>II: Awareness of the Ethereum ecosystem</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4UBbdwi449LxeQIA.jpeg" /></figure><h4>Research from speculating on crypto drove the little knowledge of the Ethereum ecosystem that people did have.</h4><ul><li>Because most people were introduced to crypto as a form of speculation, Tether had significantly more name recognition than USDC and Dai. People had seen it on exchanges like Binance or mentioned in news articles.</li><li>When discussing borrowing and lending on the blockchain, DeFi protocols like MakerDAO and Compound had little to no recognition, but Nexo and ETHLend were mentioned once each, but only for their tokens purchased as speculation — the products were never used.</li><li>Out of the 4 people who had heard about MetaMask, only 2 had ever used it. They specifically used it to play CryptoKitties during the market boom, and had uninstalled it since.</li></ul><p><em>In each interview, we walked users through an explanation of earning on the Compound protocol. We touched on key aspects like the high earning rates (7–10% on DAI), the use of stablecoins, the over-collateralization of loans and the protocol’s risk mitigation measures.</em></p><p><em>Earning on Compound is a good way to encapsulate the DeFi phenomenon, representing a lot of the strengths (cost savings, removing the middleman) and weaknesses (smart contract security, technical complexity). We’ve curated their thoughts into insights that we believe apply to the DeFi ecosystem as a whole.</em></p><h3>III: What casual consumers liked about DeFi</h3><h4>Has no direct connection to the stock market</h4><p>Savvier investors recognized quickly that ecosystems like Compound were not directly connected to the stock market’s performance. This opened their eyes to DeFi as a way to diversify their portfolio, especially since this group was heavy in robo-advisors, index funds and stocks. A few also called out the value of earning 7–10% interest in an economic climate where interest rates were decreasing worldwide.</p><p>Less-savvy investors also saw this as a strong positive when mentioned to them, although they weren’t able to proactively recognize it.</p><blockquote>“Most of my investments are in the stock market, which I feel a little worried about with everyone talking about a recession coming. This could help diversify [my portfolio] without taking big risks.” (27, M, Finance)</blockquote><h4>Higher returns vs. traditional investments.</h4><p>When presented with some relevant comparison points (7% as the historical average for stock market returns, ~2% for high-yield savings accounts), people were sold.</p><p>All 21 users expressed a positive response upon seeing the comparison numbers, and many were pleasantly surprised. Even with people who were savvy traditional investors, contextualizing Compound’s rates was a helpful reminder that put things in perspective.</p><blockquote>“Wow, I can earn 3–4 times what I can with a high yield savings account!” (33, M, Entrepreneur)</blockquote><blockquote>“I can earn like the stock market but don’t have to worry about all the ups and downs. This is awesome.” (30, M, Marketing)</blockquote><h4>Removes the bank as the middleman</h4><p>Many of our participants liked the idea of DeFi removing the banks as middlemen. However, the bigger insight was that this helped users <strong>better understand the source </strong>of their higher returns. The lightbulb moment came for users when they realized cutting out the bank’s share led to greater earnings for themselves. This simple yet powerful explanation helped some get over the “too good to be true” hurdle for Compound’s rates.</p><blockquote>“#%@$ the banks. I read that banks made record profits in 2018. 7–10% APY is high, and cutting banks out is a bonus.” (28, F, Business Development)</blockquote><blockquote>“I like that the Ethereum code is removing the banks from the equation. This makes sense now — I thought it sounded sketchy at first.” (28, M, Lawyer)</blockquote><h4>Feeds into existing belief in blockchain technology as the “future”</h4><p>Almost all participants who liked DeFi also cited a larger belief in the long-term potential of blockchain technology, regardless of their background. Several who had little expertise of their own were still willing to believe in DeFi and Compound as a manifestation of the technology’s promise, due to the bullishness of experts they trusted.</p><blockquote>“I believe in this technology long-term, regardless of crypto prices and Bitcoin. It’s the future of money.” (24, M, Engineer)</blockquote><blockquote>“I think that blockchain is going to revolutionize a lot of different industries and a lot of smart people I follow think that as well.” (32, F, Designer)</blockquote><h3>IV: Casual consumers’ problems with DeFi</h3><p>Many of the problems our participants had with using Compound were centered around security and volatility. While that’s nothing new within the broader context of cryptocurrency, there are some special nuances for DeFi that we wanted to tease out.</p><h4>The lack of a centralized, accountable organization</h4><p>For most participants, the thing they most valued was the security of their money. They cared less about the path to get there, whether it was centralized or decentralized technology. A few saw the trustless nature of the smart contracts to be positive to security, but for most, smart contracts created more questions than answers.</p><p>On the other hand, our participants generally trusted Coinbase, almost exclusively more so more than smart contracts or DeFi products they were learning about. They saw Coinbase as a known entity with public accountability — their friends and family all used Coinbase.</p><blockquote><strong>“</strong>When I think about decentralization, I worry that no one’s responsible if something happens. I like that Coinbase has a CEO and an About Us section, that if something happens there are people that would be accountable.” (30, M, Marketing)</blockquote><blockquote>“Do I have to send my stablecoins to an address outside of Coinbase? That’s a little scary — I trust Coinbase, they’re a known Silicon Valley company. I have no idea who’s building these more experimental products.” (32, F, Designer)</blockquote><h4>The fear of hacks</h4><p>Many of our participants had a story: someone they knew that lost their funds through some exchange or wallet hack . The less technical participants tended towards conflating all of the money-loss events in the ecosystem (exchange hacks, ICO scams, smart contract hacks). The most cited example was the May 2019 Binance hack. These people struggled to assess the risk of an ecosystem like Compound getting hacked, and wanted trusted third parties’ opinions of its security.</p><p>The more technical participants were able to hone in more specifically on smart contract security — knowing that bugs happen frequently in normal development, they expressed distrust towards holding large amounts of value in smart contracts.</p><blockquote>“I don’t think crypto technology is 100% secure. Many people in Korea believe so. I wouldn’t feel safe having a lot of money in my own exchange, let alone a service I don’t know much about.” (26, M, Grad Student)</blockquote><blockquote>“I don’t know a ton about smart contracts, but if the code can’t be changed easily and they’re holding a lot of money, that seems dangerous. If Binance can get hacked, anyone can get hacked.” (32, M, Engineer)</blockquote><h4>The lack of “insurance”</h4><p>The number 1 question we got about security of Compound was some version of “is my money insured?” Several users proactively compared earning on Compound to a savings account, which invited this natural follow-up. There was a tone of suspicion when this question was asked, as if they were trying to figure out what the catch was.</p><p>A few who asked about insurance for Compound proactively recalled that Coinbase and Gemini had insurance, but were unable to describe what the specific details of the policies were. We did not try explaining the new trend of decentralized smart contract insurance, but it’s likely that these participants wouldn’t be thrilled about the idea of smart contracts being insured by other smart contracts.</p><blockquote>“Is this company legally liable if you lose your money?” (28, F, Tech)</blockquote><blockquote>“I remember Binance got hacked recently. If my funds were lost, do I have FDIC insurance or something similar?” (29, M, Tech)</blockquote><h4>The volatility of stablecoins (particularly Dai)</h4><p>After the walkthrough, a few financially savvier participants asked follow-up questions about the price stability of stablecoins. They were satisfied with the idea that USDC was guaranteed at a $1 rate, but had concerns about Dai. In particular, they were concerned about Dai’s price fluctuations and its use of a volatile cryptocurrency like Ethereum as collateral, even if the fluctuations themselves were minor.</p><blockquote>“I’m from South America so I think about the risks of currencies changing in price. It’s worrying that Dai changes in price so often, when it’s supposed to be stable.” (33, M, Entrepreneur)</blockquote><blockquote>“I’ve heard of MakerDAO but I don’t know what they do, relying on Dai seems unnecessary when I can just take safer stablecoins that are guaranteed. I care more about the coin being stable than about whether it’s decentralized.” (30, M, Marketing)</blockquote><h3>To be continued…</h3><p>There’s a lot here to unpack, and we can’t do it within a single conclusion. We’ve explored various reactions of a casual cryptocurrency user to DeFi, yet there’s still a lot of nuance remaining, particularly around different audience segments.</p><p>We’ll be exploring these themes deeper in our next few posts, as we take you with us on our journey building Gossamer. Stay tuned.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fievoyi%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fievoyi&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fievoyi%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/71d2ba03f9834452354ae9af1aacd325/href">https://medium.com/media/71d2ba03f9834452354ae9af1aacd325/href</a></iframe><h4>If you found this useful, please share, follow us on <a href="https://twitter.com/UseGossamer">Twitter</a> and Medium, and of course try our live alpha product at <a href="https://www.usegossamer.com/">usegossamer.com</a>. Stay tuned for the next iteration of the series, in which we break down target audience segments most ripe to be onboarded onto DeFi.</h4><p><em>Many thanks to my co-founder </em><a href="https://twitter.com/tarikbellamine"><em>Tarik Bellamine</em></a><em>, </em><a href="https://www.linkedin.com/in/sarasodine/"><em>Sara Sodine</em></a><em> and </em><a href="https://twitter.com/starsoup7"><em>Sarah Baker Mills</em></a><em> for feedback on this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f20f180c23a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/usegossamer/the-next-wave-of-defi-users-a-ux-research-study-f20f180c23a1">The Next Wave of DeFi Users: A UX Research Study</a> was originally published in <a href="https://medium.com/usegossamer">Gossamer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 principles for designing blockchain apps for non-technical users]]></title>
            <link>https://medium.com/hackernoon/6-principles-for-designing-dapps-for-regular-people-from-a-consensus-18-hackathon-winner-134cdb881cc1?source=rss-88447dabb08d------2</link>
            <guid isPermaLink="false">https://medium.com/p/134cdb881cc1</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Kevin D. Kim]]></dc:creator>
            <pubDate>Thu, 31 May 2018 15:38:28 GMT</pubDate>
            <atom:updated>2019-05-23T09:03:57.744Z</atom:updated>
            <content:encoded><![CDATA[<h4>A case study using one of the Consensus ’18 hackathon-winning dApps</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OGJNqnQEpKB01rd5UxpokA.png" /></figure><p>Earlier this month at the 2018 CoinDesk Consensus Hackathon in New York, my team signed up to build a supply chain <a href="https://hackernoon.com/tagged/blockchain">blockchain</a> app to track NYC produce from farm to restaurant. When I asked the on-site local sustainability worker who the users were, she told me that some farmers who needed to use the app were <em>“70 years old, don’t check their email and can’t use the current Excel spreadsheet system”</em>.</p><p>I was stunned. How were we supposed to build a blockchain app for a 70-year old farmer who can’t even figure out Microsoft Office?</p><p>Challenges like this will only grow more common, as at least <a href="http://www.hsbc.com/news-and-insight/media-resources/media-releases/2017/rise-of-the-technophobe-education-key-to-tech-adoption-says-hsbc">80% of people in the world do not know what blockchain is</a>. Unfortunately, <a href="https://www.coindesk.com/information/what-is-a-decentralized-application-dapp/">dApps</a> (apps with some data or logic on a blockchain) for regular people today have bad user experiences. Aside from a few that have <a href="https://media.consensys.net/get-to-know-the-47-projects-that-make-up-the-consensys-mesh-478b7d3028c1">tens of millions of dollars of institutional support and dozens of support staff</a>, these dApps consist of poorly-designed <a href="https://medium.com/@mccannatron/state-of-the-dapps-5-observations-from-usage-data-april-2018-a3e9da01bc22">pyramid schemes, casino games, CryptoKitties knock-offs</a> and of course, Ether Shrimp Farm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7VOrn6YEK9IHrRoL5k-dBQ.png" /><figcaption>I didn’t handpick this dApp just to prove my point — according to dappradar.com, this is legitimately one of the most popular dApps today. Yikes.</figcaption></figure><p>Our dApp took a crack at this for the Consensus hackathon, and won first place in our division for our solution.<strong> In this article, I’ll be sharing 6 key principles for designing dApps for non-technical users, using the process behind our hackathon dApp as a case study. If you’re interested in dApps, blockchain, UX or design, this article is for you.</strong></p><h3>Hackathon Context</h3><p>Before diving into the <a href="https://hackernoon.com/tagged/design">design</a> principles, I’ll skim over the basics of our project here.</p><ul><li><strong>Challenge </strong>— The CoinDesk challenge we addressed:</li></ul><blockquote>Using blockchain technologies, create a prototype to give trackability and transparency to GrowNYC food supply chain, from farm, to warehouse, to retail outlet, to consumers.</blockquote><ul><li><strong>Team</strong> — Our team consisted of 1 front-end developer (Rachel), 2 back-end developers (Saif, Piers) and a developer straddling both and handling the QR code recognition (Paco). I was the UX designer and also collected user and data model requirements.</li><li><strong>Constraints </strong>— We started hacking around noon on Saturday, and submissions were due by 1pm on Sunday. So we had only 24 hours to conceive, design and build the solution.</li><li><strong>Technology</strong> — We built a mobile application with React Native that each member of the supply chain (farmers, warehouse workers, etc.) would use to enter in and verify package data. We built on the Hyperledger runtime engine and used JavaScript and Hyperledger Composer native languages for the logic and data model.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K4Di41I1XPUH1kSynZ9uWA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kw2QoY1GMDQ7Fbm37hke2A.jpeg" /><figcaption>Hard at work deploying our local blockchain (left). Printing out and testing multiple QR codes (right).</figcaption></figure><h3>1. Use user personas to frame the problem around people, not blockchain</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HvAAj-j0cxibRTyfNEQV3g.jpeg" /><figcaption>Excuse the handwriting…</figcaption></figure><p>Based on information I gathered about our less tech-literate users, I developed quick user personas of the people that would need to use this solution. <a href="https://www.usability.gov/how-to-and-tools/methods/personas.html">User personas</a> are not meant to be actual people, but humanized approximations of who real users might be to make their problems more concrete:</p><ul><li><em>Winston</em>, 70-year old farmer<strong>, </strong>white<strong>, </strong>a U.S. Navy veteran, uses an old Android phone, needs his grandson to manage his emails</li><li><em>Truong</em>, a 29-year old warehouse worker and father of three, Vietnamese immigrant, just started taking night courses for his limited English</li><li><em>Katrina</em>, a 20-year old CUNY student and Greenmarket intern, white, manages a part of the farmer’s market<strong>, </strong>majoring in Cinema Studies</li><li><em>Cristobal</em>, a 37-year old associate chef at a local restaurant, Mexican-American, responsible for buying produce in the mornings from the local markets for the day</li><li><em>Denise</em>, a 42-year old part-time florist and mother of two who brought her family to dine at the restaurant, African-American, just moved to NYC from Mississippi</li></ul><p>It may seem a bit fluffy, but humanizing these imaginary users in detail helps you gut-check yourself at various points in the development process.</p><p><em>Gas price and GWEI? Will a 70-year old farmer care about that?</em></p><p><em>Explaining hashes and showing full timestamps? Maybe that’s unnecessary for a 42-year old tired mother who just wants to know where her apple pie came from.</em></p><p><strong>Use personas to make sure you’re building the product for your end users, not for yourself.</strong></p><h3><strong>2. Make complex data entry as easy as possible</strong></h3><p>After building our personas, we pieced together the user journey for our app. The below graphic explains how users chronologically would use Localtrail. A package of food is tracked from the farm where it was grown, to the retail location where it’s consumed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I510LXRANtK3n2nZTOyJCg.png" /><figcaption>A walkthrough of how various stakeholders in the process use the Localtrail app for a given package</figcaption></figure><p><a href="https://en.wikipedia.org/wiki/Hick%27s_law">Hick’s Law</a> is a simple concept: the more choices you put in front of your users, the more time it will take them to make a decision. When our users include 70-year old farmers or stressed-out mothers, reducing complexity in data entry and management is critical to the app’s survival. This applies to all apps, but those stakes are<strong> </strong>even higher when dealing with blockchain,<strong> </strong>where it’s easy to go overboard with data<strong>. </strong>Here are three helpful tactics:</p><h4><strong>Collect only the minimum viable data</strong></h4><p>We favored simplicity over detail in our data model — for each package, we prioritized the fewest number of data points possible for trustless verification, like the type of food, the quantity of the food and the quantity metric. Adding extra mandatory fields usually <a href="https://unbounce.com/conversion-rate-optimization/how-to-optimize-contact-forms/">increases the abandonment rate</a> of a form, so extraneous data like purchase information didn’t need to be on a blockchain. If you’re using a public blockchain and are subject to gas, being rigorous about what data is pushed to the blockchain becomes even more important.</p><h4>Design the flow based on the context</h4><p>A few things that need to be considered for a complex user flow:</p><ol><li><strong>Device:</strong> <a href="http://www.scielo.org.co/scielo.php?script=sci_arttext&amp;pid=S0012-73532015000500026">People prefer bigger screens</a> for complex tasks and data entry, but we were locked into mobile given the need for on-the-go code scanning and data entry. <a href="https://www.appticles.com/blog/2016/03/mobile-vs-desktop-13-essential-user-behaviors/">Mobile websites have twice the bounce rate and a third of the engagement of desktop</a>, so you need to fight to keep their attention.</li><li><strong>Type of data: </strong>If you’re asking a series of yes or no questions or users just have to select an answer, visualizing it all at once is palatable. But when you’re mixing freeform text boxes, drop-down menus and calendar popups — break up the flow to make it manageable for users.</li><li><strong>Number of data fields per package X packages per day: </strong>The farmer had to enter in 7 different data points for each package, sure. But we also had to multiply that by dozens of times per day because of the amount of produce some farms were shipping.</li></ol><h4>Show explicit progress to keep users engaged</h4><p>Your brain generates dopamine after completing a task — gamifying experiences with points or levels is a classic tactic to keep <a href="https://blog.trello.com/the-psychology-of-checklists-why-setting-small-goals-motivates-us-to-accomplish-bigger-things">users coming back for more</a>, especially when dealing with boring tasks like data entry. Particularly for blockchain-related data, a single moment of frustration in the flow can cause a user to leave and move on to one of the hundreds of other things they have to do that day. Because of this, it’s critical to give users visual answers to questions like <em>“how far through the process am I?”</em> and <em>“am I done, or is there more?”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NsnYdAgSQEVBX1LpsfB1bA.png" /><figcaption>The farmer flow is broken up into smaller chunks, making a complex process very simple</figcaption></figure><p><strong>Taking the above into account, we landed on the above flow that had more steps and less complexity per step.</strong> One long scrolling screen might be more time efficient, but I pictured Winston squinting at his screen in direct sunlight on his farm, his thumb hitting the wrong form fields scrolling through his low-end Android. So we opted for a direction that had many simple screens, one after another, asking for only the minimum viable data that would be posted on the blockchain.</p><p>We also opted for a visual timeline that conveys to the user that there are discrete steps in this process and while in the middle of this process, they can go back or keep moving forward. One inspiration here was Intuit’s <a href="https://www.invisionapp.com/blog/ux-review-turbo-tax-makes-filing-almost-fun/">TurboTax</a> app, which does a great job of splitting up the impossibly complicated task of filing taxes into many bite-sized chunks.</p><h3>3. Abstract away the blockchain as much as possible</h3><p>Here’s a list of things that 1. don’t help Winston the farmer do his job, and 2. might confuse him to the point of giving up on the app:</p><ul><li><em>The hash of his blockchain transaction, full string or truncated</em></li><li><em>His participant address</em></li><li><em>The block ID containing his transaction (if this was on mainnet)</em></li><li><em>The etherscan.io link to the block in which his transaction is being mined (if this was on mainnet)</em></li><li><em>The knowledge that his transaction data was stored on the blockchain</em></li><li><em>The knowledge that his blockchain provider is Hyperledger</em></li></ul><p>Frankly, it’s not important for a farmer or a warehouse worker to know that their transactions are being posted to a blockchain at all. <em>For a supply chain app built on a centralized server, would we explain the nuances of server redundancy or AWS Lambda in the farmer flow?</em></p><p>The earlier principle of collecting “minimum viable data” applies to <em>showing data</em> as well — we should only show the minimum blockchain data necessary for the specific problem space and users. Blockchain data scares most people. That’s why we removed that data from the Farmer Flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dbByQf5_Nt1RNWRpWkPVBQ.png" /></figure><p>We can apply this concept to the End Consumer experience as well, where people at places like restaurants are scanning a QR code to see where their food came from. Here’s how I prioritized the data:</p><ul><li><strong>Above the fold </strong>— show the farm, its location, and how fresh the food is (given harvest date). This is maybe 85% of people — these diners are busy and seeing that the food is fresh and it’s from a real local farm is good enough.</li><li><strong>Normal View of the receipt </strong>— additional details like the address of the farm and the exact harvest date. A very small number of people, perhaps 10% of consumers, might fall into this group. Partly for boredom or curiosity, they will look at the additional data and then move on with their life.</li><li><strong>Expanded View of the receipt </strong>— the previous information plus the actual field of harvest (sometimes different than the farm itself), the timestamp of the various steps of QA, and a tool tip that taps out to an explanation of how blockchain was integrated into the product. A <em>tiny, tiny </em>number of enthusiasts (maybe 5%) will care enough to examine the detailed journey the package of food has gone through.</li></ul><p>By adding more friction to the consumer experience as the information became less relevant to the users, we’re valuing their time, but providing an option to see more if they want to do so. <strong>We’re not taking away control from users by making it harder to see data — we’re being respectful of their busy lives.</strong></p><h3>4. Be transparent when dealing with irreversible actions</h3><p>When users are about to make permanent decisions with lasting consequences, clarity and transparency need to be baked into the design. For Localtrail, it’s not important for these users to know that their transactions are being posted to a blockchain — but what is important is for them to know that <strong>submitting or verifying package data is irreversible</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d2uiMiQn04uhtQKxjOm9Vg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0wWtqxxfZ3Gir-9y80ZyVw.png" /><figcaption>Convey security without conveying blockchain</figcaption></figure><p>To get this across, we added careful copy that emphasizes that submitting that data is final and cannot be edited once posted. We abstract the technical cause of that to the fact that we’re storing their data in “a transparent, secure way”, and incorporate the familiar iconography of a the lock and the cloud, two concepts that users in 2018 are familiar with, to convey the immutability of their data storage.</p><h3>5. Don’t hold your users up while their data posts to the blockchain</h3><p>It is not important here to the farmer whether package data is in the process of being appended to the blockchain vs. has finished being appended. Each step in the flow requires the right type of data to advance and our app was built on a permissioned blockchain (no gas), so there’s no way for a transaction that was submitted to fail. Even on public blockchains, after a transaction is submitted you can provide muted updates through notifications and small modals while the user does something else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cYusACbGgA7Qkn3cIypzeg.png" /><figcaption>Instead of a loading screen while the data is appended to the blockchain, we provide Winston immediate actions to take, designed with priority in mind</figcaption></figure><p>What’s truly important is <em>clarity around what their next action should be</em>. Most dApps lack a post-transaction assurance that the user can move on, which can be frightening for less tech-literate users. We provided a prioritized set of buttons: a higher-priority “New Package” button (likely what the farmer’s next action will be), and a lower-priority transparent “View All Transactions” button.</p><p>We designed the app to help Winston focus on his most important tasks, not add unnecessary cognitive load.</p><h3><strong>6. Remove blockchain from your name and branding</strong></h3><p>Our choice of the name Localtrail and the tagline <em>Community-first transparency in the supply chain </em>was intentional<em>. </em>Most blockchain-enabled companies have the words <em>block</em>,<em> chain</em>,<em> bit or eth </em>in their name. That might be OK if your users are developers or enterprises, but for regular consumers, it’s better to focus on the actual problem you’re solving.</p><p>We wanted to reinforce our focus on the user and their problems in their <em>local community. </em>Even in the logo, you don’t see any chains or cubes — ours is a farm, the origin of the community supply chain<strong>. </strong><a href="https://twitter.com/OhJia">Jia Wu</a> showed me an existing supply chain solution, <a href="https://www.provenance.org/">Provenance</a> — that takes a similar approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1IYfL9560XW2WdbWV2-u5A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*luZdDsLMvNQ6SDJ5YUfE2Q.png" /><figcaption>Provenance.org’s landing page — nary a mention of blockchain in sight!</figcaption></figure><p>Nowhere in the site until you click on “Technology” do you see a mention of blockchain. Their <em>“Every product has a story” </em>tagline focuses on conveying their mission and the value they provide to customers. That’s how it should be done.</p><h3>Final Thoughts</h3><h3>Hyperledger on Twitter</h3><p>Congrats to Localtrail - winners of the Hyperledger prize package at the Building Blocks Hackathon! They built a transparent blockchain solution that tracks produce from farm to supply center to the end user, powered by Hyperledger Fabric &amp;amp; Hyperledger Composer #Consensus2018</p><h4>dApps are still apps, and apps need to be usable</h4><p>There’s a perceived tension in the blockchain community between the traditional UX mantra of simplifying the user’s experience for them, and the decentralization ethos of giving full control and transparency to users. <em>In my mind, this tension shouldn’t exist.</em></p><p>Hashes and Merkle tree proofs might instill confidence for dApps in banking or enterprise-grade data storage. But if we’re talking about consumer-facing dApps where most to all of the users have no idea what blockchain is —<strong> </strong><em>we have to be able to let go of the desire to aggressively prove trustlessness as much as we can</em>.<strong> </strong>All that data isn’t helping anyone if only 1% of users understand what it means.</p><p>The most successful startups focus relentlessly on <a href="http://startupclass.samaltman.com/courses/lec07/">connecting with their users</a> and <a href="https://www.youtube.com/watch?v=IhNnkPsdohY">making something that people want</a>. That doesn’t change just because some of the code or data lives on a blockchain. <strong>We will only achieve mainstream adoption of blockchain if we deliver great user experiences.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y2L3QQx5_Giz8lMz42AsYg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZdHqRUW6vVoCmW0qhUVWtg.jpeg" /><figcaption>All of the Consensus 2018 hackathon participants (left). Our awesome team (right).</figcaption></figure><h4>If you enjoyed my thoughts, please clap, leave a comment, reach out via email (<em>kevin0kim@gmail.com</em>) or <a href="https://twitter.com/kevin0kim">Twitter</a> — I’m trying to become more active. My next post will build off of this one, breaking down existing popular dApps from a user experience standpoint.</h4><p><em>Thanks to </em><a href="https://medium.com/@sayaiwasaki"><em>Saya Iwasaki</em></a><em>, Sara Sodine, </em><a href="https://elankiderman.com/"><em>Elan Kiderman</em></a><em>, </em><a href="https://twitter.com/Bosefina"><em>Bo Ren</em></a><em>, Vijay Menon, </em><a href="https://twitter.com/Levanche"><em>Charu Jangid</em></a><em>, </em><a href="http://danshipper.com/"><em>Dan Shipper</em></a><em>, </em><a href="https://www.linkedin.com/in/tarik-bellamine-0aa35352/"><em>Tarik Bellamine</em></a><em>, </em><a href="https://medium.com/@brianubiquik"><em>Brian Flynn</em></a><em> and </em><a href="https://medium.com/@mitchkosowski"><em>Mitch Kosowski</em></a><em> for their feedback on this article. Thanks to my awesome teammates Rachel, Paco, Saif and Piers. And thanks to </em><a href="https://medium.com/u/3d9d3a22b291"><em>beltran</em></a><em> and </em><a href="https://medium.com/u/411ecbe2a483"><em>Sarah Baker Mills</em></a><em> for influencing me with great pieces.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=134cdb881cc1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/6-principles-for-designing-dapps-for-regular-people-from-a-consensus-18-hackathon-winner-134cdb881cc1">6 principles for designing blockchain apps for non-technical users</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>