<?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 Wiemer Viet on Medium]]></title>
        <description><![CDATA[Stories by Wiemer Viet on Medium]]></description>
        <link>https://medium.com/@wiemerviet?source=rss-5e014c172a55------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*j3D0x-6PBToWeQDzi2vBMQ.jpeg</url>
            <title>Stories by Wiemer Viet on Medium</title>
            <link>https://medium.com/@wiemerviet?source=rss-5e014c172a55------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:30:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wiemerviet/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[8 tips for a smooth and delightful sign-up flow]]></title>
            <link>https://medium.com/lifes-a-picnic/8-tips-for-a-smooth-and-delightful-sign-up-flow-8bbac3589317?source=rss-5e014c172a55------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bbac3589317</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui-animation]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Wiemer Viet]]></dc:creator>
            <pubDate>Tue, 06 Jul 2021 10:23:42 GMT</pubDate>
            <atom:updated>2021-07-06T10:23:42.492Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-t90h5mXPnYVrZ1a7HohUg.png" /><figcaption>Illustration by <a href="https://medium.com/u/7f4c60a31635">Irene Falgueras</a></figcaption></figure><p>Garages, we would love them to be tidy and well-organised, but over time they always turn into chaos. How often aren’t we planning on restoring order and cleaning up? But motivation already evaporates when we stand in front of the big mess. We just don’t know where to start! Sign-up forms are not any different. If we see a list of input fields stretching beyond the borders of our screen we’d rather run to the nearest exit. Let’s do this later.</p><p>But what if we got a little help? Someone who would guide us to break down the big job into smaller ones. Let’s first order our garden equipment or ask for one piece of information instead of all. Let’s turn that form into a flow.</p><blockquote>“Too many choices or irrelevant options can cause hesitation, confusion, or worse abandonment.”</blockquote><blockquote>― <strong>Nir Eyal</strong></blockquote><p>Not that long ago, our sign-up was one of those horror forms. Customers had to provide us with all the information we needed and in the worst case, we wouldn’t even be able to provide them our services. Most of the customers did get the job done, but it wasn’t a delightful experience. This blog will touch upon 8 key learnings which helped us in creating a stepped sign-up flow and a delightful first experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*znVgzAduoZYhxC8NaNckPQ.png" /></figure><h4>1: Ask only what’s necessary</h4><p>Which information do you really need from someone for them to start using your service? Information like the customer’s birthday is most likely not mandatory for them to sign-up. Each step you add creates an extra hurdle to jump over. The more hurdles, the more likely your new customer will drop out. During our sign-up process, we only ask what’s essential. First and foremost, we need to know if we can deliver at the customer’s address. Additionally, the E-mail address and password we use to get in contact and give the customer the ability to log in. And lastly, we ask for the customer’s phone number so they can use SMS verification to securely log in to the app. If you don’t have such security features, you can leave out the phone number. It is one of the higher hurdles since customers might get the feeling that they will receive unwanted marketing calls. If you don’t need it to get started, skip it.</p><h4>2: Timing is everything</h4><p>Consider when it makes the most sense to ask for which information, maybe the sign-up isn’t the place for it. For example, at Picnic we only ask for the customer’s first and last name when they place their first order. Simply because the Runners needs to know which doorbell to ring. Asking for this information during check-out makes more sense. At check-out, we can explain that we need this information to make the delivery successful. The customer is more likely to provide this information at this point. During sign-up asking for this information doesn’t make much sense, since the customer doesn’t see the value of it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fIdmD1cirA1pPUgjImdUBA.png" /></figure><h4>3: Take the customer by the hand</h4><p>So now we know what the questions will be in our sign-up form. Luckily we are not tied to a physical piece of paper, which means we can split these questions over multiple screens. By creating these splits, we create more focus for the customer. Also, similar to planning framework SCRUM, we split the big task of filling the complete form into smaller individual tasks. Completing a small task is easier and gives a feeling of completion. Robert Cialdini’s principle of commitment and consistency states that if a customer makes a small step or completes the first action towards a goal they are more likely to complete the task. It’s recommended to start with questions that can be answered from the top of mind and aren’t privacy sensitive. Once the customer has taken a first small step, they are more likely to complete the entire flow. Humans don’t like to quit, so when a couple of harder questions come later, they are less likely to drop out. Completing things gives us a nice feeling.</p><h4>4: Tell me why</h4><p>Even though we carefully weigh what we need to ask during the sign-up, it is still important to tell what we will do with this data and why we need it right now. For example, if we do need the phone number, which is quite a sensitive topic as mentioned earlier, it’s really important that we emphasise that we will use this for security reasons such as 2FA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lGpMUO5mr8wfnS-Gg2uHnQ.png" /></figure><h4>5: Make it conversational</h4><p>One big downfall of our previous sign-up form was that we asked to fill in the complete form, even if later on it turned out we didn’t deliver at their address. Quite a bad experience, putting in all the effort to complete the form and not getting the reward. By creating a stepped flow, we can take side paths. As in conversation, we can give tailored questions based on the answers we got. For example, when we do not deliver at the customer’s address, we can ask if they want to be updated when we do.</p><h4>6: Get the details right</h4><p>The small interactions will turn this flow into a smooth ride. For example, always start with the keyboard open and the field in focus. The customer can start typing right away, saving an extra click or two in each step. When there are multiple fields, make sure the keyboard has the next key enabled, so that the customer does not have to scroll or search for the next field. Even better, if your field has a fixed input, like for example a postal code. Make this transition to the next field go automatically when the requirements for the field have been met.</p><h4>7: Clear copy</h4><p>When a customer is on the quest to complete a task as quickly as possible, you want to coach them with clear instructions to their goal. Our new sign-up has a fixed format on every screen, so the customer learns quickly where to look for the instructions they need. We always state the question first, directly asking for the input we’re looking for. The customer can choose to enter the input straightaway. In case the customer has questions, we give a little explanation of what we will do with this data. But keep it short, there’s a big chance that a customer won’t read a long piece of copy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qgj4mYWmIw1AJeudhTYIEA.gif" /></figure><h4>8: Small delights</h4><p>You never get a second chance to make a first impression. This is probably the first time the customer interacts with your product, let’s make it a memorable experience. In our sign-up, each step is enriched with a <a href="https://airbnb.design/lottie/">Lottie animation</a>. For example, celebrating that we deliver at the address with some balloons popping up. Or, my personal favorite, Peter Picnic closing his eyes when the customer is typing their password. By adding these small delights the customer is not only satisfyingly completing tasks but also has a smile on their face doing so.</p><h4>Final word</h4><p>During testing the sign-up with customers we already noticed how easily they flow through it. The interaction was very natural to complete. Since we have rolled-out this new flow we have seen an increase in the rate of successful completion: more new customers successfully sign-up. 🎉</p><p>For many of us, filling out long-winded forms sometimes feels as the bane of our existence. However, with a few smart tweaks you don’t have to put your customers through the same thing. We’ve learned that sign-up flows don’t just have to work, but can actually be that delightful first experience your customer remember.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bbac3589317" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lifes-a-picnic/8-tips-for-a-smooth-and-delightful-sign-up-flow-8bbac3589317">8 tips for a smooth and delightful sign-up flow</a> was originally published in <a href="https://medium.com/lifes-a-picnic">Life&#39;s a Picnic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What a collaborative design tool like Figma brought our team]]></title>
            <link>https://medium.com/lifes-a-picnic/what-a-collaborative-design-tool-like-figma-brought-our-team-9fba8543de01?source=rss-5e014c172a55------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fba8543de01</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[design-tools]]></category>
            <category><![CDATA[figma]]></category>
            <dc:creator><![CDATA[Wiemer Viet]]></dc:creator>
            <pubDate>Tue, 17 Sep 2019 12:59:16 GMT</pubDate>
            <atom:updated>2021-02-18T10:17:51.609Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cMAclE8xIRlYarjoChLwZg.png" /></figure><p>Within our product teams at Picnic, researchers, designers, copywriters, and developers work closely together. For example, at the daily stand-up, where we all share what we’re working on, and where we as designers hear how we might be able to assist our colleagues in their work. Or at the weekly UX-kickstart, where we share progress and make decisions with our fellow designers. Or when we do demos at the end of a sprint, and team members show what they have been working on and we celebrate what we’ve achieved together. The developers let the latest feature see daylight for the first time and designers show the freshest prototypes. Whatever it is that we do, we do it together.</p><p>But, not that long ago, the design tool we used didn’t reflect our collaborative work environment. We used Sketch and the files were all saved on our company Dropbox. Each project had its own structured folder including Sketch files, Principle prototypes , and all other related files. For a business owner, this is like entering a maze. And if the copywriter wants to work on a project, he has to make sure the designer has saved and closed the file he wants to open. Otherwise, conflicted copies end up all over the place. You can compare it to a locked archive cabinet, that only the designer can open. Everyone who wants to take a look at the progress or start the next iteration has to ask the designer for the keys.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*R1a8IK21g7kx7tFC" /><figcaption>Sketch files locked up in a vault</figcaption></figure><p>Luckily, we are still a small team of designers. This makes it relatively easy to experiment with new tools and implement them into our workflow. So we looked into the world of design tools and we gave some a spin. We tried Framer X, Figma and the beta of InVision Studio. All great tools with their own advantages, but after weighing the options, we decided to go with Figma. Why? Let’s take a look.</p><h4><strong>Multiplayer designing</strong></h4><p>Figma is like a multiplayer game, we’re all online working together in the same space. We no longer have conflicted files on our Dropbox anymore (yay 🎉) and we can all work on a project at the same time. Today still, it feels like magic when there are multiple cursors moving over your screen, building up a new app feature. But besides multiplayer designing, it’s also easier to check in on your colleagues work-in-progress. I can open a project and leave direct feedback, try out something and leave it behind as a present, or copy and paste some screens for my own work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*rwyrxVIPzh4WHamcxG_t3Q.gif" /><figcaption>Multiple cursors performing magic</figcaption></figure><h4><strong>Sharing progress with business owners</strong></h4><p>In Sketch, you can export the latest flowchart as a PNG and share it with the team. But don’t be surprised if the Project Lead who was on vacation shows-up at your desk two weeks later with a list of remarks. You’ve already entered the next phase of design and might have tackled many of these comments.</p><p>With Figma, business owners, developers, and project leads can have viewing access and can always see the latest version of the project. They can also peek into earlier iterations to see what has been tried before. They could even pick-up the pencil and create sketches themselves to communicate their ideas.</p><blockquote>“But when everything is set up, it works like a charm”</blockquote><h4><strong>Co-op mode with copywriters</strong></h4><p>Another great thing about multiplayer designing is that it’s seamless to work together with our copy team. But beware, inviting others to work on your projects takes some preparation such as structuring your files and clearing up the design process. But when everything is set up, it works like a charm. For copywriters, it’s more natural to work in actual designs. It’s easy to see if the copy fits in the UI because you get a better understanding of the complete feel of the screen or feature. This is better for workflow, copy-pasting is minimized, and errors are reduced.</p><h4><strong>Component overrides</strong></h4><p>Besides live collaboration, there’s a lot more gold in this treasure chest. For example, I really like the component overrides (psst: check out my blog on <a href="https://blog.picnic.nl/building-the-picnic-component-library-b89583df8e16">the creation of our own component library</a>). Figma allows you to change colors, text and things like border-radius while leaving constraints fixed. This allows for minor changes while keeping the component connected. And all changes to the master are still visible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*omkuIMqU2Ue9pK7I" /><figcaption>Overriding a component in Figma</figcaption></figure><h4><strong>Other stuff we really liked!</strong></h4><p><em>Searching for components</em>: Figma provides a search option for searching components, which is much easier compared to the structured menu of Sketch.</p><p><em>Versioning</em><strong>: </strong>One of the downsides of working with many people in the same file is that, sometimes, stuff magically disappears 🤷‍♂️. With versioning, you can go back in time and find what was lost.</p><p><em>Less hardware dependency</em><strong>: </strong>New tools require bigger hard drives, faster processors and more RAM to keep up with all the innovations. Everyone loves a fancy new laptop, but wouldn’t it be great if our machines last a little longer? Compared to for example Sketch, Figma uses less CPU and also runs on Windows. This didn’t make us pick Figma, but it’s certainly a nice benefit.</p><h4><strong>Point of improvement</strong></h4><p><em>Intuitiveness: </em>One of the things we miss from Sketch is the intuitiveness of the tool. Especially the layers panel. I used this a lot and found it easy to understand and navigate. But in Figma, you can get easily lost and it’s more difficult to discern the difference between groups, layers, and components.</p><h4><strong>Final word</strong></h4><p>At Picnic, we are really happy with the tool transition. It fits our workflow better. By collaborating inside the tool, we’ve also improved our productivity; giving feedback to each other just makes us go faster. And last but not least, everybody, company-wide, can join the party and see what’s going on in design land.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fba8543de01" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lifes-a-picnic/what-a-collaborative-design-tool-like-figma-brought-our-team-9fba8543de01">What a collaborative design tool like Figma brought our team</a> was originally published in <a href="https://medium.com/lifes-a-picnic">Life&#39;s a Picnic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 user-testing insights that shaped the Picnic Runner App]]></title>
            <link>https://medium.com/lifes-a-picnic/5-user-testing-insights-that-shaped-the-picnic-runner-app-fdff593ab6bb?source=rss-5e014c172a55------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdff593ab6bb</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Wiemer Viet]]></dc:creator>
            <pubDate>Thu, 17 Jan 2019 08:24:12 GMT</pubDate>
            <atom:updated>2021-02-18T10:17:29.786Z</atom:updated>
            <content:encoded><![CDATA[<p>Remember that time you tried to push open a door but instead smacked your face against the glass? You were meant to pull. But don’t worry…it wasn’t your fault, it was the door’s. Or more specifically the <em>design </em>of the door.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/382/1*dVgByF7kqbW4nYcKNVkYTA.gif" /><figcaption>A Norman door in the wild</figcaption></figure><p>At first sight, the door’s form was not obvious to understand. This is called the Norman door, after Don Norman, writer of the book <em>The Design of Everyday Things.</em></p><p>“A door poses only two essential questions,” he writes. “In which direction does it move? On which side should one work it? The answers should be given by design, without any need for words or symbols, certainly without any need for trial and error.”</p><p>The purpose of everyday tools and products should be intuitive to understand. Without a second thought. This lies in the design and the responsibility is with designers.</p><h3>The Picnic Runner App</h3><p><a href="https://medium.com/lifes-a-picnic/picnic-the-modern-milkman-transforming-urban-distribution-bae975749a12">Picnic’s Runners deliver groceries in a busy, urban environment.</a> They need to know where to go and to quickly and simply recognise which orders to unload. The system they use should be the perfect companion that helps them fulfil their daily tasks.</p><p>We looked at the third-party software our Runner’s were using and realised that there were features and functions that were not fully intuitive. It wasn’t clear how to operate the software at first glance and training from experienced users, as well as trial and error, was needed just to understand the basics.</p><p>Such software was not offering the helping hand that our Runners require. Especially a new Runner, who’s already nervous about starting the job.</p><p>To help out Runners and improve efficiency, thus cutting back on training time and making workflow more fluid, we decided to create, design and build our very own <strong>Picnic Runner App</strong>.</p><h3>Learning from Runners</h3><p>The design and building of prototypes only began once we had developed an awareness of the problems we wanted to solve. By joining Runners on their trips, we observed how they worked as well as doing deliveries ourselves. We gained an intimate understanding of the everyday workflow, the obstacles presented by the third-party software and how a new design could offer better solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZVptzLd20LFCHWNA" /><figcaption>User-testing in an electric Picnic Vehicle (ePV)</figcaption></figure><p>There were over <strong>60 user-tests </strong>with Runners across the Netherlands and we went through <strong>11 iterations</strong> of the design. We made mistakes, got confused and some of the team woke up in the middle of the night with bright ideas and a cry of ‘Eureka!’.</p><p>Overall we learnt a lot.</p><p>Here are five insights that we discovered during user-testing and which ultimately shaped the Picnic Runner App to what it is today.</p><h4>1. Focus on the task at hand</h4><p>The tasks of a Runner are repetitive and linear. Most deliveries go smoothly and Runners follow their schedule. Each delivery consists of the following steps:</p><ol><li>Navigate to the (next) address</li><li>Unload groceries from the vehicle</li><li>Carry them to the customer’s doorstep</li><li>Collect and load any returned goods (e.g bottles or packages)</li><li>Repeat</li></ol><p>When the third-party software was opened Runners were given many options. Sometimes this even led them to screens which were never used. Every time the device was activated, there were unnecessary decisions to make. Taking time and wasting cognitive load.</p><p>We reduced the number of options to make sure that Runners only see information that helps them with the task at hand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Pnr7a6J3HUwmB3j9" /><figcaption>Discussing the flow with Runner Amir during a test trip</figcaption></figure><h4>2. No more talking like a computer</h4><p>When I was in school, there were two types of vending machines. Vending Machine One had horizontal rows lettered A-Z and vertical columns numbered 1–20. To buy a soda, you first had to find out the corresponding code (e.g. Doctor Pepper: B6). You typed this into the keypad before paying and receiving your favourite carbonated soft drink with a unique and subtle flavour.</p><p>Vending Machine Two had buttons with each soda represented by an image. You didn’t have to learn the language of the machine. You just tapped the drink you wanted, paid and it would drop down. Much easier!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-t1DYA3THrDcKewGMdEl4w.png" /></figure><p>Similarly, we noticed that the system to locate totes, the crates in which deliveries are stored, was confusing and took time to learn. Each tote location had a double number (the first representing the left or right side of the <a href="https://medium.com/lifes-a-picnic/the-epv-cute-clean-and-electric-b840e0c00b1">ePV</a>, the second showing the position within that side). I.e. Vending Machine One.</p><p>We created a visual representation of the side of the ePV with highlighted tote positions, just like Vending Machine Two. This way, Runners can immediately recognise where the totes for each delivery are located.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tj-FN6qURLW5OB6vH45FtQ.png" /></figure><h4>3. Learn from the cheaters</h4><p>People find ways to get around systems they don’t like. Cheaters are intuitive and show how improvements can be made. We ran group sessions with the Runners to learn about their experiences on the job. Helping us discover some interesting hacks.</p><p>We learnt that the current trip scheduling was actually slowing Runners down. They would perform their deliveries faster than planned and arrive early to customers. Thanks to the insight, we developed how the trips are scheduled. Now, the system is better catered to the speed of the Runners while ensuring deliveries arrive in our 20-minute window.</p><p>With an understanding of drop locations (e.g. whether the address is a house or an apartment on the 6th floor with no elevator), each drop-time can be improved, making trips more efficient. We added a feature to collect this information. In the future, it will be possible to tailor trips to the experience level of each Runner. Helping new Runners build up their skills.</p><h4>4. Celebrate achievements big and small</h4><p>We found that it wasn’t always clear when a delivery was completed. On top of that, going through a successive process from address to address with repetitive tasks can get tedious. By developing a screen that gives Runners feedback on their last delivery and a little encouragement for the ones to come, we create a small brain break.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*U1XPw6VX6Z_zNa1W" /><figcaption>Not only is the feedback valuable, but it celebrates a micro achievement</figcaption></figure><h4>5. Don’t be blinded in the dark</h4><p>During a test trip in Utrecht, the sun began to set and it quickly became dark. Because the screen of the device was really bright, it was difficult for the Runner to adjust their eyes between checking the direction and staying focused on the road. This could lead to a dangerous situation. The solution came quickly: don’t be blinded in the dark, turn on nightmode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jFa96ENpfkHALVD3" /></figure><h3>The advantages of user-testing</h3><p>There are many advantages to embedding user-testing into the design process. It saves a lot of time, money and effort. We don’t have to build a finished product before discovering if it works. Instead, we create low-fidelity prototypes to proof our concepts with real users. Maybe an idea looks and sounds great in the office, but is it really intuitive to use?</p><p>Often designers become very convinced of their products. After putting a lot of effort into a new design, you get stuck in a tunnel and it can be crushing to discover what you built doesn’t work. With user-testing, your vision remains broad. You’re ready for whatever each session brings and eager to try many different things to learn what works and what doesn’t.</p><p>For the enterprise design team at Picnic, it’s handy that our users are just around the corner. Whenever there’s a new idea or concept to test, we can find out directly if our prototypes work. We don’t have to travel far and our colleagues, the Runners, are always willing to take us along for a ride.</p><p>In my experience, I’ve found that people in Picnic’s operation are always motivated to help out and be involved in the development process.</p><p>After all, they are the ones that use our designs every day.</p><blockquote>“The error is not the user’s. It’s the designer’s.”</blockquote><blockquote>Don Norman.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdff593ab6bb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lifes-a-picnic/5-user-testing-insights-that-shaped-the-picnic-runner-app-fdff593ab6bb">5 user-testing insights that shaped the Picnic Runner App</a> was originally published in <a href="https://medium.com/lifes-a-picnic">Life&#39;s a Picnic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building the Picnic Component Library]]></title>
            <link>https://medium.com/lifes-a-picnic/building-the-picnic-component-library-b89583df8e16?source=rss-5e014c172a55------2</link>
            <guid isPermaLink="false">https://medium.com/p/b89583df8e16</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[components]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[libraries]]></category>
            <dc:creator><![CDATA[Wiemer Viet]]></dc:creator>
            <pubDate>Thu, 21 Jun 2018 07:55:37 GMT</pubDate>
            <atom:updated>2021-02-18T10:17:39.172Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In a growing company like Picnic, it can be hard to keep everything streamlined and structured. Especially in UI design where each designer has to be on the same page in order to create a pixel-perfect product. You might like the buttons to have a margin of 12 pixels, while someone else prefers 8. You might like your hairlines in #e5e5e5 but your colleague wants #f2f2f2.</em></p><p><em>To prevent these pixel-debates and hexadecimal-discussions, we decided to build a structured component library. By doing this, we not only make sure that everyone uses the same margins, colours and corner roundness, but we also speed up the process of converting wireframes and sketches into actual screens. Allowing us to quickly update designs for our user testing sessions.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/384/1*uHJlJBm7fHNljnUcsaKl4A.png" /><figcaption>A component library is like a box of Lego</figcaption></figure><p>A year ago, when I started at Picnic, the designs were still evolving and there was no UI library. During the start-up phase, there were many freelance designers working for short periods in the company. This meant there was no ownership over the categorised masterfiles. There was a complex process for selecting features, and new designers struggled to tell the difference between ideas and an actual design. This lead to many different interpretations of the Picnic design, and no-one was sure what the rules were behind building a cohesive UI. My first project at Picnic was to fix this problem and create a structured way of distributing and maintain the UI.</p><h4><strong>Let’s get started</strong></h4><p>To kick of this project, I had to formulate a set of rules to form the style guide. These rules are a visual representation of the Picnic brand. A great way to determine what should be in this guide is by using <em>css </em>properties, like:</p><p>1. <strong>Colour: </strong>First, the brand colours. At Picnic we have two colours, both with a darker variation. Purpose colours can also be added to the palette, e.g. red when something goes wrong. We finish the palette by adding a set of greys to be our building colours.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WKRT07HV0ygVsX1KbJASnA.png" /></figure><p>2. <strong>Shadows: </strong>To help us determine which shadow level to use, we have a set of two shadows that depend on the background colour. Alternatively, there is the option for a flat design and no shadow at all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RatelM7w2wQ6yia8S7MocA.png" /></figure><p>3. <strong>Font: </strong>Either pick a font that matches the brand identity, or build a custom one. At Picnic, we have a separate font for Android and iOS. We also determine what the font weight and size will be. In addition, you’ll need body text, headers, subheaders and button text.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LfexkEAwrFA8VDyON4iWCA.png" /></figure><p>4. <strong>Border radius:<em> </em></strong><em>No border radius makes a product more corporate, whereas rounder borders are friendlier.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vs6WpaSQYstVNWnE4rLBuA.png" /></figure><p>5. <strong>Grid: </strong>Pick a grid, but keep in mind that it has to be scalable. A 5 point grid will get you in trouble when scaling up to 1.5x. So, if in doubt, use an 8 point grid.</p><p>6. <strong>Easing curves: </strong>When elements move they communicate a lot to the user. If your product is robotic and mechanical you should use little easing. If you want to appear tough and daring, your elements should move quickly and be aggressive. Or maybe your target audience is kids, then you want to be more playful, and go for the bounce-curve.</p><blockquote>“Our websites are fluid, so our processes and workflows need to match.”</blockquote><blockquote>— Brad Frost</blockquote><h4><strong>Chemistry is the answer</strong></h4><p>Typefaces, colours, grids, etc., are important bases, but they remain subjective and leave room for interpretation. To prevent different outcomes of this style guide, they need to be translated into fixed components. These become the building blocks of the product, just like a big box of Lego. Web developer Brad Frost came up with a great way to build such a library. By comparing the structure of an app or website to principles found in chemistry and biology, he created <strong>Atomic Design</strong>. In this method, small components come together to create a big part. These new parts together create an even bigger part and so on. Brad uses the following steps:</p><p>1. <strong>Atoms:</strong> the smallest element, cannot be broken down into smaller pieces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cNfvkACqcgwUQgZjuCWGZA.png" /></figure><p>2. <strong>Molecules</strong>: a small set of atoms that already have a function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JK-e8lR0U_cKwF4cFgKxUw.png" /></figure><p>3. <strong>Organisms</strong>: a bigger set of atoms and molecules that have a function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T_rctPcLqSuaX8nOgo8mig.png" /></figure><p>4. <strong>Template</strong>: a complete screen without content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bgdayp_2fXZGrnCZa5jahA.png" /></figure><p>5. <strong>Page</strong>: A template containing content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Djfg2NIDV8QHkeuar--eqA.png" /></figure><p>By using atomic design reusable items are created. Atoms can be used in different molecules and may end up in a different page, but they will look exactly the same.</p><blockquote>For example, the search icon from the search page also appears in the navigation header in the Picnic storefront. By editing the search icon atom, its appearance will change in both pages, making sure there are never two different search icons. This saves time and creates a consistent product.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qOHgz98pyb-GJRxKRxAL6A.png" /></figure><h4><strong>Ease of use</strong></h4><p>UI chemistry is fine and dandy, but designers do not want to waste time digging through a pile of atoms, molecules and organisms to find the right component. Therefore, it is crucial to group and name the elements correctly. A common way of doing this is by naming them after design patterns. A pattern is a general, reusable solutions to commonly occurring problem, which can be used in different interfaces. For example, the tab bar in the Picnic app is a common way to structure pages, and is also used in other apps to fix the same problem. By naming the element <em>tabbar </em>in the library, a designer knows immediately what the component contains.</p><p>A single pattern can have many forms, depending on the implementations. E.g., a button is a common way to confirm an action, but it has several different forms. The visual appearance of that button communicates to the user if the action is primary or secondary. Furthermore, the rest of the molecule where the atom appears influences it’s appearance. For instance, on a full page you’ll see a raised button, but on a card a flat button is used.</p><p>For example, the slotselector, used to select delivery time, is a unique and very important item to the Picnic world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j2PTIFyggMT2iTUKoDLJnA.png" /><figcaption>The slotselector is used to pick the time of delivery</figcaption></figure><h4><strong>Final step, put it in the cloud</strong></h4><p>To ensure that the library is working at its full potential, each designer must use the same version. I experimented with tools such as Craft from Invision, or by putting a Sketch template into dropbox. These worked, but they weren’t great. Thankfully, Sketch released ‘libraries’. This puts the different components straight into the cloud and onto the machine of the designer. This means that when a component is edited, all designers immediately have the latest update at their disposal. The library is alive, and components can easily be added or removed. To make sure that only the good stuff is in our box of UI-Lego, we only add components from features that have been developed and have survived the A/B test in our live product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3CjBuiMCYu7U8G-1t4M7cg.gif" /><figcaption>Building a screen using ‘libraries’ in Sketch</figcaption></figure><h4><strong>We love the library</strong></h4><p>Since building the Picnic component library our workflow has improved greatly. This is especially noticeable when the team starts working on a new project. It has become easy to add the existing screens from the symbols menu in Sketch, so the designer can check out the current design. When we decide what to build, we can start experimenting with building different blocks, or moving pre-existing ones around. Maybe the perfect brick is already there, or we can detach an element from the library and start changing it to our liking.</p><p>With the pre-set components, we are able to create prototypes much faster. We only have to think about the new stuff we create, because the elements that we reuse come from our library. This speeds up the process, and new designs are quickly converted into prototypes. This not only improves the speed of the workflow, but our designs have become more consistent. Picnic’s developers see more cohesive designs, and this translates into consistent and ultimately enjoyable products.</p><p>In conclusion: we love our component library ❤️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b89583df8e16" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lifes-a-picnic/building-the-picnic-component-library-b89583df8e16">Building the Picnic Component Library</a> was originally published in <a href="https://medium.com/lifes-a-picnic">Life&#39;s a Picnic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>