<?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 Hubert F on Medium]]></title>
        <description><![CDATA[Stories by Hubert F on Medium]]></description>
        <link>https://medium.com/@MySweetHubert?source=rss-d10930d767c9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mqlkj5ambLbZOqAYzwt41g.jpeg</url>
            <title>Stories by Hubert F on Medium</title>
            <link>https://medium.com/@MySweetHubert?source=rss-d10930d767c9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:42:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@MySweetHubert/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[Accessibility, a powerful design tool]]></title>
            <link>https://medium.com/slack-design/accessibility-a-powerful-design-tool-22f5e6d46278?source=rss-d10930d767c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/22f5e6d46278</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[a11y]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Hubert F]]></dc:creator>
            <pubDate>Mon, 25 Feb 2019 18:16:49 GMT</pubDate>
            <atom:updated>2019-02-25T18:16:49.361Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*ARw2tN489LwdBYGf" /><figcaption>Photo of gold glitter by <a href="https://unsplash.com/@rawpixel">rawpixel</a> on <a href="https://unsplash.com/photos/7unLAauqSeg">Unsplash</a></figcaption></figure><p>When given the choice between an accessible bathroom or a non-accessible one, many people would pick the accessible one: there’s more space, it’s more comfortable, it’s a no-brainer. Digital products are the same. When given the choice, people naturally prefer what’s easier for them to use, to read, or to understand.</p><p>But designers tend to be reluctant to follow accessibility standards — the design practices that help people with visual, motor, auditory, cognitive, or other disabilities make the most of a digital product. Accessibility is a complicated subject, and sticking to those standards is often perceived as a creativity inhibitor, which might turn a sensible design into something that looks more like a road sign:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*ykxU50FGJNN8-XSn1FG00A.png" /><figcaption>Crossing the Slack interface with caution tape colors: what designers think when they hear “accessible” :(</figcaption></figure><p>But accessible design helps everyone. It improves experiences not just for people with disabilities, but for people in temporary situations where their usual way of interacting with your product won’t work — say, if they’re outside and can’t see their screen well or if their mouse runs out of battery and they can only use their keyboard.</p><p>Accessibility is not a constraint: It is a design philosophy that encourages you to make better choices for your users, and helps you focus on what really matters. Simplicity will always be the most difficult target to reach in a design, and accessibility can be one of the best tools to get you there. Slack has been investing more resources to focus on accessibility in the last few years, and what was originally perceived as an extra burden turned out to be one of the best things that ever happen to our design team. There are a million different ways you could implement accessibility in your process, but here are a few that are working really well for us.</p><h3>Narrow down your choices</h3><p>The typical design process can feel like a succession of micro decisions, most of which tend to be hard to explain individually. Why would this colour work better than another? Why would this font size be more appropriate? This famous quote from <a href="https://stopdesign.com/archive/2009/03/20/goodbye-google.html">Douglas Bowman</a> resonates a lot with designers:</p><blockquote>A team at Google couldn’t decide between two blues, so they tested 41 shades between each blue to see which one performs better. […] I’ve grown tired of debating such miniscule design decisions. There are more exciting design problems in this world to tackle.</blockquote><p>Having a good, thought-out reason to make those micro decisions is essential to keep your product moving forward, and this is exactly what accessibility standards can give you. For example, only using accessible colours will help you narrow down your choices, so it’s easier to make a decision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*rCiCWdjKwMDCvtR8OYba3Q.png" /><figcaption>A smaller subset of colours meets accessibility standards, which simplifies design choices</figcaption></figure><p>If you’re making your decisions in service of a goal, accessibility, they’re much easier to defend. People can disagree with many of the choices you make, but it is infinitely harder to argue against a decision that makes your product accessible to more people. Between the blue that the CEO prefers and the one that you prefer, you will always lose, but if your blue is accessible, then it stands a much better chance.</p><p>This process is true for many aspects of design. Here at Slack, for example, we used to display the list of keyboard shortcuts inside a modal (a pop-up window, if you prefer). Eventually, we had enough shortcuts to start looking into making this modal scrollable. That’s a trivial technical change, but as we were looking into the potential accessibility issues, we realized that people with short term memory impairment could really struggle using this modal, as they had to close it in order to try the shortcut, effectively hiding the shortcut that they are trying to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*VxEIlcE0UtEgmtIXsLxkvQ.png" /><figcaption>Our previous keyboard shortcut modal required scrolling</figcaption></figure><p>Our solution was to move the panel into the right sidebar, so it could be left open while trying the various shortcuts (you can open it using Cmd/Ctrl + /). By designing for a small portion of users, we ended up creating a much better experience for everyone, as you don’t have to constantly open and close the modal to learn new shortcuts. Furthermore, this solution was much more flexible for adding new shortcuts to the list, and allowed us to even make some of the items clickable to preview the feature without needing to use the shortcut. What’s more, this was also simpler for our engineering team to build.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*INKJ0hyAbc_9_pPA2PCntg.png" /><figcaption>Our new keyboard shortcut panel opens in the right sidebar</figcaption></figure><p>We’ve also drawn on accessibility principles to improve the design of our custom status modal. A custom status in Slack is a way to quickly communicate to your teammates what you’re up to right now: commuting, in a meeting, on holiday, etc. When we first released custom statuses, the interface was entirely contained inside of a menu item.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/0*p66doG6zucBkvsnh" /><figcaption>Our first version of the custom status form used a submenu</figcaption></figure><p>But a form inside a menu item is a big problem for screen readers, who are expecting a menu item and have problem reading a form in this context. So instead we decided to use a modal to contain the form. Not only did it work better for screen readers, but it was also a more flexible solution that allowed us to introduce new features like status expiration, or having a keyboard shortcut (Cmd+Shift+Y) to open the modal, which is not something that would have made sense for a submenu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/0*UK6EmvcJAx4zt0Gt" /><figcaption>Our new custom status form, in its own modal</figcaption></figure><p>With this solution, it was easier for everyone to summon the form without using their mouse, which on top of being a great accessibility improvement, resulted in a significant usage increase for this feature since launch.</p><h3><strong>Train your team</strong></h3><p>Designing for accessibility doesn’t happen overnight; it can take some time to make your team or your company understand its value. But by backing up your design decisions with accessibility principles, you can start to build robust design patterns that will make your team’s life much simpler.</p><p>Back in 2016, Slack was using more than 130 different colours, 32 of which were different shades of blue. It wasn’t immediately seen as a problem until we raised the accessibility flag. If we ever wanted to adopt some form of accessibility standards, <strong>we needed to regain control of our colours</strong>. In a surprisingly fast process, we managed to reduce those colours to 18. This smaller palette was much easier to manage both for designers and engineers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*j8tWf9obX5SytgoPBLfumQ.png" /><figcaption>Slack’s original colour palette on desktop: more than 130 colours</figcaption></figure><p>Fast forward to today, engineers are often the first ones to point out if a colour is outside of our existing palette, as it is more work for them to create a new colour than to use an existing one. This also comes with the guarantee that if we are not creating new colours, we are much more likely to meet accessibility standards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*W4p3QsYdDILNvsrhlr7A1g.png" /><figcaption>Slack’s new colour palette on all platforms: 18 colours!</figcaption></figure><p>This new system also simplified the process for the design team. We often don’t need to specify what colour to use in our design specs, as they are quite self explanatory. This is less work for designers, less work for engineers, and a more accessible outcome.</p><p>With this new set of colours, we could more effectively start to work on the most pressing accessibility issue we had, which was the low contrast elements in the interface. A more contrasted interface is easier to use for everyone, not just people with vision impairments. But the transition to a more contrasted interface can be difficult at times. Whenever we would make a portion of the interface darker to meet accessibility standards, the immediate feedback was that it was too dark, too polarizing. People are used to the existing interface and don’t even realize the effort they have to make to use it. But after a few days, when the dust settles and they get use to the new colours, if you show them how it was before, they tend to have the exact opposite reaction. Suddenly they realize that they always had to make an effort to see the interface, even though their vision was completely fine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*ClFc2aw1tWsSV5qOIiYrdg.png" /><figcaption>Our previous, faint input field, and our current input field with sufficient contrast</figcaption></figure><p>Making the interface more contrasted ended up making it more comfortable for everyone. Once people experience this, they will be much more accepting about using accessible standards all across the interface.</p><h3><strong>Own your craft</strong></h3><p>One of the values we hold dear here at Slack is that if you’re not doing it right, then it’s not worth doing at all. Same goes for accessibility: It’s not something you can only do <em>a little bit</em>. When you start seeing accessibility as this magical ingredient that forces you to make things the right way, it becomes crystal clear that you need to apply it to every aspect of a product: from design to engineering, from marketing to customer support. For this to be possible, as a designer, you should feel empowered to completely own accessibility. Don’t assume that engineers are fully aware of accessibility standards, don’t assume that project managers have it on their list, don’t assume that your QA team is testing for it. Own it, teach it, help build the process, make it easier for everyone to understand the game. It is always more fun to play a game when everyone understand the rules.</p><p><em>Thanks to Valerie Ross, Sarah Park, and the writing team at Slack for making this blog post a million times better than my original submission.</em></p><p><em>👋 Interested in joining the team at Slack? </em><a href="https://slack.com/careers#openings"><em>We’re hiring!</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22f5e6d46278" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slack-design/accessibility-a-powerful-design-tool-22f5e6d46278">Accessibility, a powerful design tool</a> was originally published in <a href="https://medium.com/slack-design">Slack Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Threads in Slack, a long design journey]]></title>
            <link>https://medium.com/slack-design/threads-in-slack-a-long-design-journey-1c9b1af652c9?source=rss-d10930d767c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c9b1af652c9</guid>
            <category><![CDATA[messaging]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Hubert F]]></dc:creator>
            <pubDate>Wed, 04 Apr 2018 22:45:33 GMT</pubDate>
            <atom:updated>2018-04-05T03:46:53.064Z</atom:updated>
            <content:encoded><![CDATA[<h4>(Part 2 of 2)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F-jO_QPkpjU8aINP." /><figcaption>Photo by <a href="https://unsplash.com/photos/An4DuozJUnY">Kristóf Vizy</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p><a href="https://slack.design/threads-in-slack-a-long-design-journey-a7c3f410ecb4">In Part 1</a>, we covered the Slack design team’s initial approach to Threads: a feature that would allow people to reply to messages in Slack. After our first several designs proved to be failures, we had to go back to the drawing board.</p><p>The design team had spent nine months trying to build Threads, but it was time to face a harsh reality: our model was just not working, no matter how visually polished the design was. We decided to start from scratch — but beforehand, we took some time to work on a couple of small features that were necessary to support threads and emoji reactions. We also decided to conduct some user testing to better understand why our model was failing.</p><h3>Message Actions</h3><p>Before trying our next approach, we added the <a href="https://twitter.com/SlackHQ/status/664973373210886144">ability to take action on a message</a>, which fixed the problem of opening threads by mistake, and added an obvious place for threads to begin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*ZKsMp3_9WkxN0qZ0." /></figure><p>This benefited a few other projects that were happening at the same time, like the aforementioned <a href="https://twitter.com/SlackHQ/status/619175252375924737">Emoji Reactions</a> project, as well as the <a href="https://twitter.com/SlackHQ/status/732991930288775171">Share Messages</a> project, and <a href="https://twitter.com/SlackHQ/status/720674741384646658">Reminders</a>. With inline actions in place, we were able to move on to user testing.</p><h3>User Testing</h3><p>To better understand why our model was failing, we decided to conduct a small round of user testing. During those tests, people experienced the same confusion with Threads as the Slack team, but we were able to better identify the breaking points. The main problem was that the design was <strong>very complicated</strong>, and people didn’t understand it at all. For example, here is what a thread could look like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*hjO8KCUOYGdVPEOI." /></figure><p>Because you could reply to any message, including replies, Threads quickly became extremely complex. Once we realized this, we decided to restrict each thread to only one level of replies, hoping that this would be simple enough to start making sense.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*Kkz8Ec5i2HxfL1kfjQjdqw.png" /></figure><h3>Exploration 4 — One-Level Threads</h3><p>Reducing each thread to only one level of replies was an instant success on all fronts. The design was simpler, it was easier to build, and of course, easier to understand and to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*kcVPgKcYxNyUfNM3." /></figure><p>Although people were less confused with this approach, an unexpected problem started to appear: people were using Threads <strong>too much </strong>and it was making channels very difficult to understand, as multiple conversations wove into each other constantly.</p><p>Before Threads, if a user wanted to reply to an older message, they would have had to start a new message with some context, like, “about this topic, I think that…,” which was easy to read. But now that Threads were doing the heavy lifting of providing context, people didn’t bother doing this, making the channel incredibly hard to read without opening every thread in the channel.</p><p>We tried a few designs to fix this problem, like preambles before replies to provide better context, or notifications (e.g. “Hubert has replied”) that would be posted instead of replies in the channel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*lmgE53fBb52oxj-t." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*kPkXDXyjgUKdtZyD." /></figure><p>Unfortunately, none of our solutions had any real positive impact. No matter how it was presented, Threads would make you read messages multiple times, as you would read a thread and then read the replies of that thread again in the channel. The feature that was supposed to help reading channels was doing the exact opposite. Once again, our model was failing. Since posting replies in the channel was never going to work, we decided to explore removing them altogether.</p><h3>Exploration 5 — Sidebar Conversations</h3><p>In our next iteration, replies were only posted in the sidebar, not in the channel. This was a major simplification of the feature, both in terms of visual design and engineering. But we were facing a new problem. On all our previous explorations, a new reply would mark the channel as unread, so the user would be alerted when their conversation was continuing. Now that replies were not in the channel anymore, we couldn’t rely on this system, but we still needed a way to let users know when new replies arrived. We decided to move thread notifications to the Activity panel on the top right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*QRBfcpqXjSz34jD_." /></figure><p><strong>Hiding replies from the channel content turned out to be the single most meaningful change we made while designing Threads.</strong> Channels were once again easy to read and focused. People weren’t confused about how to use Threads. Before this change, we would see people using Threads on the last message in the channel even though it would have been exactly the same to just send a new message to the channel. Now, there was a real difference between replying in the channel or in a thread.</p><p>Of course, things were still not perfect. We quickly realised that the Activity panel was not the right way to notify people about new replies. It was easy to miss, but distracting at the same time. The notification system was going to be our next challenge.</p><h3>Exploration 6 — All Threads</h3><p>For the first time, we didn’t have to turn our previous experiment off while building a central reply notification system (known as All Threads). Even though things were not perfect, they were good enough for our team to use in their normal workday. We took this as a very strong sign that we were on the right path.</p><p>All Threads was based on an existing feature in Slack, All Unreads, which displays all a user’s unread messages in a central view. The success of that feature proved we could build views detached from the context of a channel, and it seemed like a logical template to use for this feature, as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*-naxj1Z4k8TiAT_a." /></figure><p>All Threads made it easier to notify users about new replies, and easier for users to browse recent replies. None of our other designs allowed you to go back to older Threads once you closed them, and ultimately, this is what convinced us that it was the best option to start with. After a few days and a few tweaks, the feedback we were receiving was mostly about adding more features to this view — a positive sign! To avoid the risk of making All Threads too complicated for its initial launch, we decided to keep those ideas for future explorations.</p><h3>Exploration 7 — Broadcasts</h3><p>The last thing that we needed to address is the fear of missing out that people felt, with replies no longer appearing in channels. For this, we made broadcasts — a way of letting users choose to post their reply back to the channel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*PCBH8qtqsDd1rcWg." /></figure><p>As subtle as it seems, this was the final touch that gave stability to the whole model we were trying to build. The most valuable aspect of Threads was the reduction of extra noise in channels, but in some cases, that was problematic. For a few people, the previous design (where all replies were posted in the channel) was exactly what they needed. By adding the ability to also send your reply back to the channel, we allowed people the flexibility to use Threads in whichever way made sense to them.</p><h4><strong>Mobile</strong></h4><p>As Threads were also built on mobile platforms at the same time, each new exploration meant that the mobile version had to be adjusted as well. This was very new for our mobile team, as they were used to receiving projects in a mostly finished state. The Threads project was a catalyst for many of the changes that were made in the way we structure the product team at Slack today, like merging mobile and core product teams. To fully explore the impact of Threads on our mobile process will require a separate (future) blog post.</p><h4><strong>Launch &amp; Post Mortem</strong></h4><p>Having an exceptional Customer Experience team was crucial to launching Threads successfully, as they establish a direct line of communication between people using Slack and our product team. They helped us launch <a href="https://twitter.com/SlackHQ/status/821778487849586688">the feature</a> in <a href="https://slack.engineering/weaving-threads-bee48dc69d6">the best way</a> <a href="https://slackhq.com/threaded-messaging-comes-to-slack-417ffba054bd">possible</a>, and even replied to hundreds of users who had requested Threads over the years. We went as far back as early 2015.</p><blockquote>Looking back at all the work we’ve done, it almost sounds crazy that we thought that any of our early ideas could ever work.</blockquote><p>Even though it was a long road to get there, launching Threads was only the first step of the real journey. Launching is always the easy part. Since then we’ve made many adjustments, and have kept a very close eye on the feedback we’ve received.</p><p>Looking back at all the work we’ve done, it almost sounds crazy that we thought that any of our early ideas could ever work. But with every iteration of our design, we were convinced that this time we had the right solution, which made each failure even more difficult to admit. This journey was long, exciting, and sometimes painful, but it helped us remember that failing is an essential part of the design process, and you just have to be okay with it.</p><p>Every one of our failing explorations was successful to a small portion of people. It’s impossible to make everyone happy when releasing such an important feature, but after all our efforts, and all our failed attempts, we were able to face critics with a much stronger confidence about our solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/0*dJVBpVV8mIffMzXy." /></figure><p><em>Interested in joining the team at Slack? </em><a href="https://slack.com/careers#openings"><em>We’re hiring!</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c9b1af652c9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slack-design/threads-in-slack-a-long-design-journey-1c9b1af652c9">Threads in Slack, a long design journey</a> was originally published in <a href="https://medium.com/slack-design">Slack Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Threads in Slack, a long design journey]]></title>
            <link>https://medium.com/slack-design/threads-in-slack-a-long-design-journey-a7c3f410ecb4?source=rss-d10930d767c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7c3f410ecb4</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Hubert F]]></dc:creator>
            <pubDate>Fri, 23 Mar 2018 17:38:29 GMT</pubDate>
            <atom:updated>2020-08-25T16:41:06.796Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>(Part 1 of 2)</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ao94bmtjXx3DlWyg9_yJng.png" /><figcaption>Photo by <a href="https://unsplash.com/photos/HwxVLhLyg2s">Alexander Milo</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>On August 19, 2014 at 11:46 AM, Stewart Butterfield, CEO of Slack, created a new channel called #feat-rxns and invited a few members of the Slack team to join the conversation. The purpose of this channel was to build two new features in Slack: <a href="https://slackhq.com/722-ways-to-say-i-got-your-message-e69a4d7da8e4"><strong>Emoji Reactions</strong></a> and <strong>Threads</strong>. Looking back at this more than 3 years later, it might sound strange that both features were combined into one project, but at the time it did not sound like either of those would be big enough to justify more than one channel. They both revolved around the same idea: reacting to a message, with either words or emoji.</p><p>This is the story of designing Threads, and how much we underestimated its complexity. It’s also a deep dive into the design process at Slack.</p><h3>What are threads, though?</h3><p>Threads was one of our most requested features, but one thing that we realized quite early on is that “having threads in Slack” could mean a lot of different things. Most of the tools we use every day have threaded conversations at their core: Facebook, Twitter, Reddit, YouTube (and of course, emails). However, they each have a different way to handling this feature.</p><p>At the time, Facebook posts each had only one long thread of comments ordered by date. On Twitter, any tweet could have a multitude of direct replies, and those replies could also have replies, allowing an infinite amount of depth. Reddit, too, treated replies and their visibility slightly differently. So which was the right approach for us?</p><p>With all these different systems around, we wanted to first understand what people really mean when they ask for threads in <em>Slack</em>. At the time, Slack was not even one year old, and it would have made total sense to build something quickly and see how customers reacted to it. But Slack was working fairly well without threads, so we decided to take the time to figure out a model that would bring the most value to the way people use Slack.</p><h3>Quick notes about the Slack design process</h3><p>One thing that we are very proud of at Slack is that <strong>we drink our own wine </strong>— for every feature that we build, we try it out on ourselves before making it available to the public. Everyone is encouraged to provide feedback about a new feature, regardless of who you are in the company. Often, the most valuable feedback comes from people who have no idea what the feature is, as they will experience it in the most candid and genuine way possible. This system also provides the design team with a bit of leeway: if we’re not sure about something, we just give it our best shot and see how it goes.</p><p>This process was crucial for Threads, where it would have been impossible to validate any of our design decisions without seeing how real people used it. We shipped 6 major versions of Threads internally, and got valuable feedback every time. Each release was necessary in order to understand what wasn’t working and what was.</p><h3>Exploration 1 — The Twitter model, inline.</h3><p>We decided to start our first exploration of Threads based on the same model as Twitter, because it looked like the most flexible solution. The design adhered to the following rules:</p><ul><li>You can reply to any message, including other replies</li><li>There is no limit to how many direct replies a message can have</li><li>All replies are posted in the channel</li></ul><p>Here is an illustration of what we had in mind:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*MfWQmaw4v_haaCY-." /></figure><p>With this system, you could have multiple conversations happening simultaneously in the channel. We liked this first approach because conversations were kept in the channel, so replies lived by the same rules as normal messages: they would mark channels as unread, and mentions would trigger a badge on the channel. All we needed to do was to make sure that replies were clearly labeled so they wouldn’t degrade the normal reading experience.</p><p>The main problem with this first version was the “expanding” effect that you would experience when opening a thread. Because we were pushing messages up and down to display the thread inline, it was difficult not to lose your bearings when closing a thread, especially since you would always end up scrolling a little bit when reading the thread, and closing it would land you in a completely different position in the channel. This was so disruptive that it was impossible to judge the rest of the feature, so we turned the whole thing off, and explored other ways to open a thread.</p><h3>Exploration 2 — Twitter model, overlay.</h3><p>Instead of pushing content up and down, we next tried displaying threads in an overlay. We believed that by separating the thread into its own layer, it would be easier to navigate the channel’s content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*k6Ofs5cVcMs6kbU9." /></figure><p>Sadly, this solution fixed one problem, but created many more. Having to constantly open and close the overlays proved to be very tedious, and it was a lot of extra work just to read a channel. Also, making every message clickable was very problematic, because people click <strong>a lot</strong>, and often for no reason. Overlays were constantly triggered by mistake (whether the user was trying to click out of a menu, a selection, or just randomly clicking while reading a message), which was very frustrating. Eventually, we decided not to persist with overlays, and to move threads to the right sidebar.</p><h3>Exploration 3 — Twitter model, right sidebar.</h3><p>Moving threads to the right sidebar was very good news for the engineering team. With a minimum amount of effort we had a new place to view threads, without shifting content or adding extra layers to the interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*kjDqzrNz864Iijv2." /></figure><p>Because we were using a familiar element, the feedback we received started to shift from comments about the user interface to comments about the user experience. It wasn’t about how the feature looked, but how people <em>felt</em> when they experienced the feature. This was a good sign, because it meant that people were starting to use Threads, rather than just looking at them, but the amount of confusion people encountered was quite worrisome. Initially, we believed that if we spent enough time polishing the workflows, the design would eventually start to make sense. Unfortunately, after a few rounds, we realized that the feedback would not change, and we needed to continue to iterate.</p><p>As difficult as it was to admit, none of our initial solutions were successful. When a team hits a wall like this, the natural reaction is to question the very necessity of our work. Should we continue? Is this even a good idea? Are we adding complexity for no good reason? Should we just forget all about it and focus on the next big feature?</p><p><em>Read part 2: “</em><a href="https://medium.com/slack-design/threads-in-slack-a-long-design-journey-1c9b1af652c9"><em>Threads in Slack, a long design journey (Part 2 of 2)</em></a><em>”</em></p><p><em>Interested in joining the team at Slack? </em><a href="https://slack.com/careers#openings"><em>We’re hiring!</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7c3f410ecb4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slack-design/threads-in-slack-a-long-design-journey-a7c3f410ecb4">Threads in Slack, a long design journey</a> was originally published in <a href="https://medium.com/slack-design">Slack Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Icon fonts]]></title>
            <link>https://medium.com/@MySweetHubert/icon-fonts-3f8118ed687?source=rss-d10930d767c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f8118ed687</guid>
            <dc:creator><![CDATA[Hubert F]]></dc:creator>
            <pubDate>Thu, 31 Jul 2014 07:42:35 GMT</pubDate>
            <atom:updated>2019-07-19T05:44:17.575Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IoYNXEkfoePg-jg3QHv61Q.jpeg" /></figure><h4>An asset management heaven.</h4><p>Icon fonts are not a new thing. Ironically, IE4 was the first major browser to support @font-face in 1997, and Firefox 3, the last one in 2009. Since then we have witnessed an explosion of the font diversity on the web, usually for the better and sometimes for the worse. After decades of starvation, web designer were suddenly exposed to thousands of new fonts to choose from, and web design could finally be recognized as a respectable craft in the design community.</p><p>But for some reason, icon fonts were never really part of this revolution. It is quite surprising as even before the web, icon fonts were heavily used by designers. More than 200 years ago, it was already common to use a Dingbat to ornate a book. Modern versions of these original icon fonts are the famous <a href="http://www.linotype.com/en/852/itczapfdingbats-family.html?PHPSESSID=d49d8c4cec6b79b6af2f1fddc347ad48">Zapf Dingbats</a> or <a href="http://www.microsoft.com/typography/web/fonts/webdings/default.htm">Webdings</a>.</p><p>It is even more surprising to notice their absence when you realize how important icons are to the web. I cannot think of one website that doesn’t use icons. But to display them, web designers prefer to rely on images, wether it’s a sprite of icons or a collection of files, each one containing a separate icon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*AglrqisvGdpHexn1nNCYRw.png" /><figcaption>This type of folder should look very familiar to any web designer.</figcaption></figure><p>These methods work well, but it is hard to maintain. Each icon needs a different images for each size, colors, and each version needs their high-res sibling to look good on modern phones or high-resolution screens.</p><p>It is simpler to maintain a sprite of icons, but it can sometimes be limiting due to the extra css positioning it requires to be displayed. Once the icon is there, it can’t be moved, otherwise you will need to alter the CSS associated with it. Not fun.</p><h3>Multiple Platforms</h3><p>It wouldn’t be too bad if everyone had the same device. But nowadays, we have to support an <a href="http://screensiz.es/phone">very long list of screens</a>. Even worse, we are not restricted to websites anymore. Everyone wants an app, wether it’s on Android or iOS, or both.</p><p>When building a product, it is extremely hard to maintain a good level of consistency across all platform and devices because of the huge amount of assets that are needed for each version. The bigger the product, the harder it is to stay consistent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*ThEhoSz_Kw3GH3YthxaMaA.png" /><figcaption>Sorry for the french, I didn’t feel like changing the language of my phone only for this screenshot.</figcaption></figure><p>For example, if you look at the current icons on twitter.com and compare them to the Twitter app on iOS 7, you will notice that none of them look the same (as of July 2014). Even the bird house (Accueil/Fils) is slightly different. It probably was updated to a nicer version for the app, but then no one took the time to track all the other versions of these icons across all platforms to update them.</p><p>This is not due to negligence. This is because maintaining the design assets of a product is a<em> huge, complicated, and sometimes really not sexy job.</em></p><h3>One file to rule them all</h3><p>So why not using icon fonts? Instead of creating hundreds of different files, only create one. Here is a quick list of the benefits:</p><ul><li>A font file can contain thousands of characters and still remains very small.</li><li>A font file is supported by absolutely every platform as long as you provide the right format.</li><li>An icon in a font file can be used at any size, on any screen, at any resolution, and with any color you want.</li><li>The icon used on your website is <strong>the same as the one you use in your app</strong>. It comes from the same source file.</li><li>If you need to update a particular icon, <strong>you just need to update it once. </strong>All the iterations of that icon will be updated, regardless of their size, colors, etc… Just replace the font file and it will be reflected on all platforms.</li><li>Icons on high-resolution screens are the <strong>same as the normal screens</strong>, no more @2x.</li><li>If you’re an advanced “icon-fonter”, you can even use things like ligatures, layered font, OpenType features, or even <a href="https://dribbble.com/shots/328841-Interpolation?list=users&amp;offset=33">instances like a normal font</a>, to change the weight of your icons.</li></ul><h3>Creating an icon font</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*5ihq_qQjdGVC_KsuIccLRA.png" /><figcaption>Drawing an icon from Sketch to Glyphs</figcaption></figure><p>That’s probably one of the main reasons icon fonts are not heavily used: it sounds very hard to create your own. But if you know how to use vectors, you’re almost there.</p><p>Font design is probably one of the most misunderstood field of design by the general public. I remember getting a surprised reaction when admitting to a coworker that I enjoy font design in my spare time. He didn’t realize that fonts were designed by people. Fonts just “are”, like they magically appeared on computers without any human input. The reality is the exact opposite, it took a very long time and a truckload of skills to create the fonts that you are currently using on your computer.</p><p>Thankfully, you don’t need to be <a href="https://twitter.com/espiekermann">Erik Spiekermann</a> to be able to create an icon font. Some recent tools made the job a lot easier than it was 10 years ago. My personal favorite is called <a href="http://www.glyphsapp.com/">Glyphs</a> and it’s as easy as using <a href="http://bohemiancoding.com/sketch/">Sketch</a>. There is even a <a href="http://www.glyphsapp.com/tutorials/creating-an-icon-webfont">very good article in the Glyph Blog</a> that explain step by step how to create an icon font with Glyphs.</p><p>In short, using a font to manage all your icons has a ton of advantages when you’re building a multi-platform product. It is not the perfect solution, but it’s solving a lot more problems than it creates.</p><h4>How about SVG?</h4><p>SVG files are also vector-based assets and many will chose SVG files over icon fonts. However, only an icon font will allow you to regroup all your assets into one file that is not a sprite. Icon fonts are still more flexible and have a better support across all platforms so when it comes to asset management, SVG files are not bringing much improvement to a pixel-based workflow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f8118ed687" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>