<?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 Ewout van Lambalgen on Medium]]></title>
        <description><![CDATA[Stories by Ewout van Lambalgen on Medium]]></description>
        <link>https://medium.com/@ewoudt?source=rss-a5999c631d62------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*vpiB3PNThQ7cR0_Xc7o8bw.jpeg</url>
            <title>Stories by Ewout van Lambalgen on Medium</title>
            <link>https://medium.com/@ewoudt?source=rss-a5999c631d62------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:27:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ewoudt/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[I made an infinite amount of fonts*]]></title>
            <link>https://medium.com/@ewoudt/i-made-an-infinite-amount-of-fonts-6b2dfbc562d7?source=rss-a5999c631d62------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b2dfbc562d7</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[variable-fonts]]></category>
            <category><![CDATA[typography]]></category>
            <category><![CDATA[freelancing]]></category>
            <dc:creator><![CDATA[Ewout van Lambalgen]]></dc:creator>
            <pubDate>Mon, 19 Dec 2022 13:03:32 GMT</pubDate>
            <atom:updated>2022-12-21T05:07:26.267Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Animated gif of infinity symbols changing in shape and size" src="https://cdn-images-1.medium.com/max/799/1*6HeD09YQojWJcQfXlmALFQ.gif" /><figcaption>Animated gif showing the Ultra-Compressed and Ultra-Expanded changing in width</figcaption></figure><h4>*More like ±45.600 variations, but ‘infinite’ just sounds more impressive.</h4><p>As a UX/UI Designer, I’ve worked for a lot of different clients and agencies in the past years. Besides that, together with two friends, I also have my own creative agency. It’s called Arbitrair (‘Arbitrary’ in Dutch). We create brand identities, illustrations, graphics and everything design related for our clients.</p><p>Just like not all architects design and build their own homes, and not all chefs cook meals for their families at home, designers sometimes overlook their own brand identities. Even though Arbitrair has worked on tons of brands, less attention was given to our own brand. It was always just a logo. There wasn’t even a specific typeface that was consistently used. So after almost 15 years it was time for a refresh.</p><p>From the moment we decided to do this, it was also clear to us it didn’t need to be a ‘super visual’ upgrade. We wanted a minimal, clean identity. Something that would fade into the background so the focus would still be on the work for the clients. What was needed was just a nice font.</p><p>This could have been as simple as downloading some existing font and calling it a day, but I always want to learn something new while working on a project. My designer’s ego and dignity wouldn’t allow for such an easy solution. It seemed this would be the perfect fun little side-project to do amongst all the client work.</p><p>And of course, a fun little side-project never really stays little..</p><p>Typography is my every-day friend in everything I work on. I believe good typography is one of the pillars of good design. But since I have almost zero experience in creating a font, I thought it was a good idea to start by finding an open source font to see how it’s done, to learn from it, and to reference it as a jumping off point. During my search for such a font I came across Work Sans by Wei Huang. Work Sans is easy to read on both small and large sizes, it has multiple weights, and has character of its own, but without an extreme personality. So I trusted it to be the perfect start for what I wanted in Arbitrair Grotesque.</p><figure><img alt="Type example of Work Sans" src="https://cdn-images-1.medium.com/max/1024/1*qEHQo4LEiMpllOnsZ3hemA.png" /></figure><p>Before working on the actual font file, I typed out all the characters in Work Sans and started sketching my adjustments on top of it. Lower crossbar here, shorter terminals there, changing some angles, switching to a different ‘a’, ‘k’, ‘G’, and ‘Q’. And finally, ink traps everywhere!</p><blockquote>* Ink traps — You know, those small negative spaces in sharp corners of characters. They’re generally used for newspaper print fonts to prevent tiny printed characters from completely filling up with ink and becoming illegible. Really not necessary in digital typography, but it is that small detail that’ll make Arbitrair Grotesque unique enough.</blockquote><figure><img alt="Work Sans with edits and changes sketched on top" src="https://cdn-images-1.medium.com/max/1024/1*o9ypwmt289zWCF49sDT8-Q.png" /></figure><p>I then moved to Glyphs.app to officially start creating the font after the sketches. One by one, I adjusted all the characters to make them look like what I had sketched out. Expectedly and unexpectedly, it took me several weeks to do all the adjustments. But when I finally finished adjusting, I exported the font file and I was.. Underwhelmed. It was technically fine, but it was just one variant, one weight. And it was boring. The result was not at all what I wanted. It was not arbitrary. I desired MORE.</p><figure><img alt="Type example of Arbitrair Grotesque Regular" src="https://cdn-images-1.medium.com/max/1024/1*d72J6QEYzYGIu2T13W17MA.png" /></figure><p>And yes, this was the moment that the project switched from a fun little side-project into a giant beast of a project.</p><p>Next to the Regular version I had just created, I wanted a Bold version. This could have been done in exactly the same way as the Regular, but I knew I would want a lot more than just two versions. I decided to go the route of variable fonts. I knew for this to work you need to create the most extreme fonts, the blackest Black and the thinnest Thin. The app can then interpolate all possible variations in-between. I started by working on an UltraBlack. When this one was done after a couple weeks, I continued on the ExtraThin. With more practice on making every character, I also got faster, and started mastering the tools and design principles pretty quickly and comfortably.</p><p>After finally being done with these two extremes, I was ready to see the magic of interpolation! I clicked export, checked on the ‘variable font’, aaaaaand… Errors. Errors everywhere.</p><figure><img alt="Screenshot of an error notification in Glyphs.app" src="https://cdn-images-1.medium.com/max/1024/1*meIh4ZNuukVwRbvE_Ciiow.png" /></figure><p>So, very valuable lesson learnt from this stage was that, apparently, it is very important to keep the outlines compatible for proper interpolation. It is crucial to not only have the same amount of nodes between different variations of a character, but also have the same path directions. If you don’t, your interpolated characters might end up very different from what you’re expecting.</p><figure><img alt="Variations of the letter a that have glitches in them" src="https://cdn-images-1.medium.com/max/1024/1*iEsIrxsc1fdpuaUBtRcN9g.png" /><figcaption>When the path direction is different between your masters, the interpolated versions of a character will all have unexpected results. Very arbitrary, but not what I want.</figcaption></figure><p>If a character consists of multiple shapes (eg. The tittle on the ‘i’ is a separate shape, which means that the ‘i’ consists of two shapes), they also need to be in the same order. Luckily Glyphs.app can fix a lot of these problems in a couple of clicks.</p><figure><img alt="Screenshot of the layers panel in Glyphs.app" src="https://cdn-images-1.medium.com/max/1024/1*uOBQrx82C0bjRR74_Gy26g.png" /><figcaption>The tittle and the stem of the ‘i’ are in the wrong order on the left. On the right, how it should be.</figcaption></figure><p>Okay, magic time, take two! This time it worked! I had a complete variable font set from the super skinny to the extremely chunky, and everything in-between. Yeah!</p><p>The super skinny to extreme chunky set of fonts indeed gave me a moment of happiness. But I still wanted more. This project needed to become a beast. A monster. I needed Condensed and Extended versions as well. I desired more. More. MORE!</p><figure><img alt="Type example of the extremes; ExtraThin, Regular and UltraBlack" src="https://cdn-images-1.medium.com/max/1024/1*yxxrh7rgAfhuJRMjWpvc8w.png" /></figure><p>I went back to Glyphs again. Creating new variants became even easier after all the exercise prior. I’ve learnt how to do it. I’ve learnt how to keep every character compatible to prevent error during exports. I’ve learnt going for the most extreme extremes to set up a good base. So this time I created the Ultra-Compressed and Ultra-Expanded versions of my ExtraThin and UltraBlack. It now only took a couple more days to create all those variants. And this time there were no errors during export!</p><figure><img alt="Type example of the extremes in both weight and width" src="https://cdn-images-1.medium.com/max/1024/1*94YaursV8IEqmvn3qO2DSQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nqdVmHuuLa7gYm2enDfcoQ.gif" /></figure><p>I’ve done it! I had one by one created a ginormous beast consisting of 4545 unique hand-drawn characters which together form a font family with every weight and width imaginable. The final collection was way too big to check every single combination for mistakes. But, I did it anyway, because I always triple-check my work. And, of course, there were still some minor bugs.</p><figure><img alt="Two versions of the letter Q in Arbitrair Grotesque" src="https://cdn-images-1.medium.com/max/1024/1*r1Ay_xGq3Efujr7gCHUD-A.png" /></figure><figure><img alt="Animated gif of the letter Q changing between versions" src="https://cdn-images-1.medium.com/max/1024/1*tP31BTOJ0TRxoxj9zQ4knw.gif" /></figure><p>In certain generated characters, some strokes and shapes started to blend together. For example the tail and the bowl of the ‘Q’ are so heavy in the UltraBlack that they become a thick mess of a character. This can be fixed by adding alternate layers. Basically a different design of the same character to switch to when you reach a certain weight or width. This keeps everything legible.</p><p>At that point, I could finally tie a ribbon on the font and call it a finished fun little side-project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Hl-7p04A3aarC1LmGe6_iA.gif" /></figure><figure><img alt="Type example of Arbitrair Grotesque" src="https://cdn-images-1.medium.com/max/1024/1*9dCcj3hAO_08EW1Rgn7V0w.png" /></figure><figure><img alt="Type example of Arbitrair Grotesque" src="https://cdn-images-1.medium.com/max/1024/1*X8_6SVn4BCFV5ViG7IFIxw.png" /></figure><figure><img alt="Type example of Arbitrair Grotesque" src="https://cdn-images-1.medium.com/max/1024/1*NCNiqBW7Tmi76Y0872AKFg.png" /></figure><figure><img alt="Type example of Arbitrair Grotesque" src="https://cdn-images-1.medium.com/max/1024/1*dv6h5QjF8rmqw1jsQUBtCQ.png" /></figure><p>There are definitely still some small kinks here and there, and it is not as a Helvetica or other classic fonts. But at least I learnt a lot during the process.</p><ul><li>Learning the basics of typography is a good first step.</li><li>Opening up open-source font files to see the details, how they’re set up, and what characters there are that you didn’t even know existed.</li><li>Tiny mistakes can lead to huge problems. So get the basics right first. Keep your nodes consistent, don’t use too many, and make sure your paths are in the right direction.</li><li>Be persistent and flexible. It is not a one-time success exercise, so just be ready to change and adjust everything again and again.</li><li>Have a plan for what you want. (Try not to suddenly decide you want a million variants halfway through the project, like me)</li><li>The first set will take a lot of time, while the rest of the variants will get easier and faster.</li><li>If you want a variable font, start with the most extreme variants and use interpolation to generate the in-between versions.</li><li>Not all (design) apps understand what to do with variable fonts. So do export all styles as separate files as well.</li><li>Just start by doing! Try things and see what happens and you might end up with a great font!</li></ul><p>And now it’s time for me to make a Serif version. And add some Italics. And a Display version.. Maybe a Monospace..</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b2dfbc562d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How bad typography (almost) ruined my holiday]]></title>
            <link>https://medium.com/@ewoudt/how-bad-typography-almost-ruined-my-holiday-763359569673?source=rss-a5999c631d62------2</link>
            <guid isPermaLink="false">https://medium.com/p/763359569673</guid>
            <category><![CDATA[lining-figures]]></category>
            <category><![CDATA[typography]]></category>
            <category><![CDATA[numerals]]></category>
            <category><![CDATA[old-style-figures]]></category>
            <category><![CDATA[passport]]></category>
            <dc:creator><![CDATA[Ewout van Lambalgen]]></dc:creator>
            <pubDate>Fri, 11 Aug 2017 08:20:09 GMT</pubDate>
            <atom:updated>2018-04-12T15:34:25.514Z</atom:updated>
            <content:encoded><![CDATA[<h4>Bad typography can <a href="https://www.typotalks.com/videos/designing-for-split-second-clarity">kill</a>, but the wrong type of numerals can prevent you from going on vacation. Which is obviously worse.</h4><p>A little while ago, I went on vacation to New York with a friend of mine. We booked our flight, applied for our ESTAs and all was good in the world. Until the day of departure when we tried to check in for our flight. The app kept on giving errors without being specific about what went wrong. After cursing the developers of said app, thinking the app was just buggy or something, I moved on to the website. But that too wouldn’t let me check in for the flight. Here at least I got an actual message on what went wrong. Still not a very useful error message: just that there was something wrong with the passenger details. But still, this was better than no information at all.</p><p>So, we both started checking our passenger details and before long this friend started calling me a moron, because I apparently entered her passports document number incorrectly. Obviously I didn’t, I can actually read. She just entered it incorrectly when she was applying for the ESTA, but that’s besides the point. The point is that this mistake was made because of bad typography. To be precise: a horrible misuse of Old Style Figures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*WrlCjzv5mszOuKdYpYkCOw.gif" /><figcaption>Shocking. I know.</figcaption></figure><p>In 2014, the Dutch passport got a complete makeover, with a pretty rainbow gradient in the background and not much else. The whole thing is actually pretty legible. It uses Lining Figures, except, for some weird reason, the document number, which uses Old Style Figures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q-YiRQm0jwaU5GwcJSJ7fg.jpeg" /><figcaption>Here’s an example of a Dutch passport.</figcaption></figure><h3>A little history</h3><p>I’m not saying Old Style Figures are evil, not at all actually, I like ‘m. But there is a time and a place to use them. And it’s not in the document number of a passport.</p><p>A long time ago, people using the Latin alphabet where using Roman Numerals. You know, those I, II, III, IV, V, VI, etc. numbers. But somewhere during the 12th century, Arabic Numerals reached Europe and we started using those more and more instead. Those Arabic Numerals are the basis of what we now call Old Style Figures. (One could argue that Roman Numerals are the OG Old Style Figures.)</p><p>Over time, shopkeepers started writing them more and more in line with each other. The first font based on this style of writing was introduced in 1788, and Lining Figures were born. After this, Lining Figures became increasingly popular and in the 19th century they had mostly started to replace Old Style Figures.</p><p>In the 20th century, Old Style became more and more in disuse with the advent of phototypesetting and later because of the lack of support for it in the first digital font files (Type1 and TrueType). Only by the time OpenType became the standard for digital font files, Old Style Figures could really make a comeback.</p><p>But since Old Style isn’t seen as separate characters by the Unicode standard, you need to use OpenType features to get to them. (In some typefaces it’s the other way around: You’ll need to use those features to get to the Lining Figures.) Many people don’t know how to use OpenType features and some apps don’t offer them altogether. (<a href="http://www.macworld.com/article/3052388/software/how-to-access-advanced-opentype-features-in-a-variety-of-mac-apps.html">Here’s how to use it</a>) Even some design apps don’t offer support. (Looking at you, Sketch – Okay, with a <a href="https://twitter.com/getflourish/status/509299605176328192">workaround</a> you can, but it should just be build into the app.)</p><h3>Old Style, Lining, Tabular, Small Caps???</h3><p>After this brief history lesson on numbers, you might be wondering what the difference between all these figures is, and when you should use them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*J9w0k-SA9GWncus60ELhTQ.png" /></figure><h4>Old Style</h4><p>Also known as non-lining, lowercase or hanging figures. They have varying heights and alignments. They are similar to lowercase characters. They share the same x-height and have ascenders (6, 8) and descenders (3, 4, 5, 7 and 9).<br>In running texts, like your body copy these figures fit in way better than Lining Figures. Good if you don’t want them to take too much attention. (Medium uses them as well, so you’re already reading a piece of text with these ‘lowercase’ numerals in them. Reads pretty good, right?)</p><p><strong>When to use:</strong> Inline in your body copy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*Sp2_0Yr0np9mhBvI2bq3ig.png" /></figure><h4>Lining Figures</h4><p>Also known as uppercase figures. These all have a uniform height and alignment. Usually the same height as capital letters and they all live on the baseline. <br>These usually feel a bit bigger then the Old Style Figures and stand out a bit more. In some cases, this makes them more legible. Which is good, if the numbers are the main focal point of your content.</p><p><strong>When to use:</strong> When showing data. Phone numbers, passport document numbers, that sort of stuff. Oh, and next to capital letters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*E_IwyoMcOwHm7sepTugQLg.png" /></figure><h4>Tabular</h4><p>Both Old Style and Lining Figures can also be Tabular. (I used lining in the example image.)<br>Tabular is like a mono-spaced version of your numerals. Good for use in tables (hence the name) when you want all numbers to align vertically to make your data more legible.</p><p><strong>When to use:</strong> In tables, when using large amounts of numbers that need to be aligned beneath each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*h678INMea5dt97cwvURgMA.png" /></figure><h4>Small Caps</h4><p>Okay, these are really not that important for this story, but still worth mentioning. Small Caps Figures aren’t really a specific type of numerals, they just fit better next to other Small Caps texts. Say, for instance, you’ve got some acronyms in your text, maybe even a flight number, like KL6020, you’ll want to use Small Caps for a better fit in your body copy.</p><p><strong>When to use:</strong> When it’s part of some text that’s also in small caps.</p><h3>So, about that document number on the Dutch passport…</h3><p>I sort of understand why the designer of the Dutch passport decided to use Old Style Figures for the document number. There’s a bigger difference between characters than with Lining Figures, such as the capital I and the number 1 (not necessarily between the capital I and the lowercase l though), and the capital O and the number 0. However, the rest of the passport uses Lining Figures. So suddenly using Old Style can be confusing if you’re a regular mortal who’s not into Typography.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/892/1*J3pRq81QH6G3U2vbXNUWNg.png" /><figcaption>The number 1, Capital I and lowercase l, using Lining Figures. Left in Brando Sans, right in Gill Sans.</figcaption></figure><p>There are a number of ways to fix the problem with the 1/I and o/O using Lining Figures. For instance, you could just not use the number 0 in the document number (which is actually true for the Dutch passport), Moreover, you could use the 0 with a slash in it, or you could even just choose a better typeface where the difference between those characters is bigger. But then you would still have the problem of context. If you only see one of the two characters, you don’t have anything to compare it to and it can still be unclear which character you’re looking at.</p><p>The context problem also goes for Old Style Figures and is probably what went wrong for my friend. Since the rest of the passport only uses Lining Figures you wouldn’t expect the document number to suddenly use a different type of numerals. The numerals in her document number are mostly the ones with descenders, so she probably thought all numbers were put on a different baseline from the letters to make it easier to read. Then, because she wasn’t paying enough attention and doesn’t have a lot of knowledge of typography, she didn’t notice that the B in her document number was actually an 8.</p><p>In her case the document number had mostly descenders, except for the 8. But if you only have sixes and eights in your document number, you could easily think they’re all Lining Figures and thus mistake a capital I for a one. Again, because of the lack of context.</p><h3>Old Style is evil?</h3><p>No! Old Style Figures are great. You just need to use them in the right place. And, although the idea of using Old Style next to capital letters for better differentiation between characters is a good one in principle, it just doesn’t work here. But then again, just using Lining Figures, without doing anything extra to the design, isn’t the answer either.</p><p>My friends thinking of the placement of letters and numbers could be an answer for this problem. Using Lining Figures, like the rest of the passport, and putting them on a different baseline from the letters, would actually make it a lot more legible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lu7sN9fK0jQ9H4sIGYpfhw.jpeg" /><figcaption>Left Old Style – Right Lining Figures, like the rest of the passport, but on a lower baseline.</figcaption></figure><p><em>(We did manage to go to New York on time, by the way. Getting a new ESTA only took 1 minute)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=763359569673" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Icon design done right.]]></title>
            <link>https://medium.com/@ewoudt/icon-design-done-right-79a051197c59?source=rss-a5999c631d62------2</link>
            <guid isPermaLink="false">https://medium.com/p/79a051197c59</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[icons]]></category>
            <dc:creator><![CDATA[Ewout van Lambalgen]]></dc:creator>
            <pubDate>Thu, 03 Nov 2016 10:23:31 GMT</pubDate>
            <atom:updated>2016-11-07T19:29:17.354Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tc-3JlVrIcg1v3i6XSb4UQ.jpeg" /></figure><p>Designing icons isn’t hard to do. But it is, apparently, hard to do right. There are a lot of things to keep in mind when creating a large set of icons.</p><p>But before we get into the details of what and how, we should first talk about what icons are. Icons are small abstract shapes that represent an idea. In UI design they can be used to make the interface easier to read. An icon is something to interact with. An intuitive visual that’s understandable through all cultures and languages. If used correctly, with a consistent icon set you can give a feeling of quality in your interface, to signal to your user that you’re a professional who knows what they’re doing.</p><p>Icons are a part of the UI. They should blend in, be actionable and easily understood at small sizes. Often clients will request an ‘icon’ that’s used more to just have a fun visual next to, say, a USP. These usually shouldn’t be icons, they’re ‘spot illustrations’ and can be richer in visual style than regular icons.</p><blockquote>“Before you know it you have a horrible mishmash of differently styled icons in your interface”</blockquote><p>Of course you could just download an icon pack from the internet and be done with it. Those packs are often missing some icons you might need for your specific use and you’ll end up downloading more icon packs to fill up the missing icons. Those icons have a different style from the first pack though. And before you know it you have a horrible mishmash of differently styled icons in your interface. Those packs are also not very unique and don’t always fit with the brand identity of your client. An icon set designed with airport wayfinding in mind would feel completely out of place at a Chinese supermarket for example.</p><p>Icon design is very much a precise job. Unlike web/interface design, there’s no front-end developer who’ll fix your smaller mistakes and inconsistencies later on. You have to make sure everything is perfect. From the stroke weights and corner radiuses to a consistent perspective and overall weight of the icons themselves.</p><p>Some things to keep in mind to design a consistent icon set:</p><h4>1. Should this even be an icon</h4><p>Before you start designing any icon you should always ask yourself if it should even be an icon. What is it going to be used for? In what context, Who’s the target audience?</p><p>If the icon is going to be used to just add an image to some text, it should probably not be an icon. A spot illustration would be more appropriate. <br>When designing a set of icons that start to look more and more the same, for example different types of media (CD, DVD, Blu-ray), you should probably not try to create different icons for everything. It’s okay to use the same icon for different cases.</p><h4>2. Define the style</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/1*rzks1yfkGsEEcdhc8Qgsvg.png" /><figcaption>Different styles for the same icon (Departing flight)</figcaption></figure><p>When designing icons for a client, you’ll want the icons to fit in with the brand. For this you can look at a couple different things. The typography or the logo for example. Does it have sharp corners or is it more rounded, how thick are the strokes. The brand colours. Is it just one colour, monochrome, multiple colours or does it use transparency? Or if that’s not enough, have a look at the brand promise or the core values. What’s the tone of voice? Is it loud, soft, friendly, pure business, etc? This will all have impact on the style of the icon.</p><h4>3. What size is it going to be used</h4><p>Figure out what size the icons are going to be used. This does a lot for the amount of detail you can use. If an icon is going to be used inline in texts and buttons it’s probably going to be small and a lot of smaller details will go missing.</p><p>Always design the icon with the pixel grid in view. Even though you’re going to export the icon as a SVG vector file, you’ll still want to have the icon looking sharp and crisp at the intended size.</p><h4>4. Put it on a grid</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*hKewJllX76cA7OiJP3hPBg.png" /><figcaption>Examples of icons using the grid (rectangles, circle, square) while keeping the same overall weight.</figcaption></figure><p>To make sure all your icons have the same weight and feel like they’re from the same family of icons you should use an icon grid. These consist of a couple of rectangles and circles. You can see these as bounding boxes. The amount of pixels within each shape is somewhat the same. Stay within these shapes and your icons will feel like they all have the same weight. Google has a great icon grid for their <a href="https://material.google.com/style/icons.html">Android/Material Design icons</a>.</p><h4>5. Stroke weights</h4><p>Try to be consistent with stroke weights. Don’t use a 1px stroke on one icon and a 3.5px stroke on the next. They will feel unbalanced and foreign from each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*MraEroTQpRm6QJQjJCNtew.png" /><figcaption>In use negative space feels heavier than positive space. That’s why a 2px negative stroke feels the same as a 2.5px positive stroke.</figcaption></figure><p>Keep in mind that negative space has a different weight than positive space. So using a 2px stroke would feel heavier as a negative stroke than as a positive stroke. Add a little weight to the positive stroke (ie. 2.5px) and it will feel like the same weight.</p><p>But don’t just use the same stroke weights for all icons in a set. Some icons can feel too heavy or light when using the same strokes as in different icons. Arrows, magnifying glasses, hamburger menu’s, check marks, etc. can feel really thin compared to more complex/solid icons. So these can get a bit more weight. Just don’t go crazy with all sorts of exceptions in weights.</p><h4>6. Outlines or solid</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*dBbP9WmAOBnNhW-yRVyh1w.png" /><figcaption>Even though these icons are part of a solid icon set, they could just as easily be part of an outline icon set.</figcaption></figure><p>When deciding between outline or solid icons always look at the bigger picture first. Will it feel at home within the design. Are outline icons heavy enough? Are solid icons too heavy?</p><p>Also consider that not all shapes work as one or the other. Outline icons tend to get really complex really fast and loose their recognisability and meaning in an interface. The same goes for solid icons. Not all icons feel solid. A smartphone or laptop icon might look like outline icons because of their screens.</p><h4>7. Corners</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/948/1*ePUA4xw71m92RuehKQWW6A.png" /><figcaption>Don’t go crazy on the amount of border radiuses in your set. Stick to one or two different radiuses for all icons. (some details may need a different radius of course, but for the bigger shapes, keep it simple and consistent)</figcaption></figure><p>Are all icons going to have hard corners, or are they all going to have a corner radius? It’s easy to lose this consistency in larger icon sets. Hard corners don’t always work on all icons and the same goes for rounded corners. Try to have a good rational behind the usage. For instance, only use rounded corners on icons that represent physical objects that are mostly rounded or organic shapes that wouldn’t be recognisable with hard corners. <br>Just be consistent. Don’t use different radiuses for every icon.</p><h4>8. 2D or 3D</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/1*doRHUx5z9coYzjaM9ep7eA.png" /><figcaption>2D icons: Is it a stack of coins or a double cheeseburger menu icon? The one on the right is clearly money.</figcaption></figure><p>Not all icons work in flat 2D shapes. A stack of coins for example isn’t recognisable from the side. It could just as easily be a hamburger menu icon.<br>Not all icons work in 3D either. A leaf or piece of paper can look very flat/2D within a 3D icon set.</p><p>That’s why you should always think about the shapes and metaphors of your icons before starting the actual design proces. Will those metaphors work in 2D, will they work in 3D? Maybe you need to change the shape a bit. The stack of coins could change into a banknote with some coins next to it, seen from the top. The leaf could become a plant in a pot so it feels more 3D.</p><h4>9. Colour</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*k4qW1qKGkQf7E9srWSEqew.png" /><figcaption>A single colour, monochrome with transparency and coloured icon on different coloured backgrounds. The coloured icon doesn’t work as well on all backgrounds and would need multiple versions with different colours to work. (Obviously the dinosaur has these colours to blend in with his surroundings. It’s just camouflage)</figcaption></figure><p>In most cases single colour icons are fine. Easy to design. And you can just use them in black or white or in your brand colours.</p><p>When going for multi-coloured icons always consider where the icon is going to be used. On a photographic background, the colours of the icon might not be as visible and you’ll need to design different versions of that icon for different use cases.</p><h4>Some tips</h4><p>Most icons need a label. Even when your icon seems completely clear and recognisable, it can still not be clear for everyone. The same icon can also have different meanings to different people.</p><p>Don’t use texts in icons. Especially not in small icons. It won’t be readable. It will only become a fuzzy mess. Just don’t do it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*rAD8VCaOLg2GrvkSjVABuA.png" /><figcaption>Don’t mix side and front views of the same type of icons. Keep them consistent by only using the front or only the side view.</figcaption></figure><p>Be consistent in the way you show shapes. For example, if you have a set of different forms of transportation, don’t show a car and a train from the side and a taxi and a bus from the front. Show all of them from the front, or all of them from the side. But don’t force it. A bicycle isn’t all that recognisable from the front.</p><p>Don’t just use some social media icon pack you found online. There are way too many of those packs with antique Twitter icons. Always download the official icon/logo from the source. You don’t want your brand to be represented with the wrong logo, so why would you represent another brand with the wrong one?</p><h4>TL;DR</h4><p>Start on paper, think about the icon, should it even be an icon. What size is the icon going to be used at. Put it on a grid. Be consistent in your strokes, corners, the use of outlines, solids and 2D or 3D. And please don’t ever use free social media icon packs.</p><p>Keeping all this in mind, designing a consistent icon set shouldn’t be all that hard.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79a051197c59" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>