<?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 Brett White on Medium]]></title>
        <description><![CDATA[Stories by Brett White on Medium]]></description>
        <link>https://medium.com/@brettandwhite?source=rss-971c75415e19------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fdoXAc-skfGqmh12U3QVMQ.jpeg</url>
            <title>Stories by Brett White on Medium</title>
            <link>https://medium.com/@brettandwhite?source=rss-971c75415e19------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 05:32:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brettandwhite/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[Keep it stupid-simple]]></title>
            <link>https://medium.com/@brettandwhite/keep-it-stupid-simple-254ae16dd86e?source=rss-971c75415e19------2</link>
            <guid isPermaLink="false">https://medium.com/p/254ae16dd86e</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Brett White]]></dc:creator>
            <pubDate>Mon, 30 Jan 2017 07:27:42 GMT</pubDate>
            <atom:updated>2017-01-30T07:29:18.205Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Keep it stupid-simple</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*3vWRWWjg-LVsjj36rSZqQw.png" /></figure><p>I’m not the biggest fan of acronyms, but the <strong>KISS</strong> principle of ‘<strong>Keep it simple, stupid</strong>’ (a design principle noted by the U.S. Navy in the 1960&#39;s) is one that I’ve appreciated since the day I first heard it, and an approach I’ve taken to creative problem solving ever since.</p><p>When designing digital user interfaces and experiences, regardless of platform (be it mobile, web, TV or wearable etc.) the less your user is required to think, the better. The fewer options you give them and the fewer actions you require, the fewer decisions they need to make and the easier it is to guide them to the intended result (be it making an inquiry, purchase or reservation etc.).</p><blockquote>“explain it to me like I’m a two year old”</blockquote><p>We are purposefully simplifying our experiences, which could also be described as ‘dumbing them down’. Like Denzel Washington’s character in the movie Philadelphia says repeatedly, “explain it to me like I’m a two year old”. Basically, a user interface needs to be ‘a no-brainer’.</p><p>I was recently suggesting the principle, and it occurred to me, that maybe it shouldn’t be ‘keep it simple, stupid’, but rather ‘<strong>keep it stupid-simple</strong>’.</p><p>So, keep it stupid-simple, stupid.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=254ae16dd86e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My top 3 UX design tools]]></title>
            <link>https://medium.com/framer-prototyping/https-medium-com-brett-white-my-3-top-ux-design-tools-754cb1f94ebb?source=rss-971c75415e19------2</link>
            <guid isPermaLink="false">https://medium.com/p/754cb1f94ebb</guid>
            <category><![CDATA[zeplin]]></category>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[framer]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Brett White]]></dc:creator>
            <pubDate>Mon, 19 Dec 2016 07:30:05 GMT</pubDate>
            <atom:updated>2018-01-04T13:51:33.006Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Mzc52NOfrWgDGG98L82aoA.jpeg" /></figure><p>Over the past year I have been on a quest for the ‘holy grail’ of the design to development process, and the tools that go with it, and finally with the year winding down and a little extra time, I find myself sitting on my couch with a cold beer (or two), trying to collect and structure my thoughts and opinions into something mildly coherent that might just add some value to anyone who designs and prototypes digital products for a living.</p><p>For the better part of the year I worked predominantly with <a href="http://www.adobe.com/africa/products/experience-design.html">Adobe XD</a>, it’s fast and loose and allows you to take a concept from design to low fidelity prototype in almost no time at all, and also allows for quick and easy exporting of assets for your developers. The tool is progressing fast, and getting better every month, but it has one fairly substantial flaw... it doesn’t play nicely with the other kids on the playground.</p><p>Low fidelity prototypes are great and definitely have their place when designing a proof of concept and getting a basic feel for the user flow, but what about custom transitions and micro interactions? For those, you need other tools, tools such as <a href="https://framerjs.com/">Framer</a> or <a href="http://origami.design/">Origami Studio</a>, but it’s at this point where you’ll realize you’ve designed yourself into a corner… “Surely I can just copy and paste or export my designs from XD into those tools?”, you’ll ask. Nope. No you can’t.</p><p>The only option you have is to recreate those designs in either Sketch, Photoshop or <a href="https://www.figma.com/">Figma</a> in order to import the layers and assets into Framer or Origami Studio. I worked for many years with Photoshop and decided a good while back (for a multitude of reasons that I won’t go into now), that it isn’t the right tool for UI design, so I’ve immediately scratched that from my list of options. I’ve heard great things about Figma and it’s leaning towards real time collaboration, but I’ve honestly never tried it, I definitely will at some stage I’m sure, but for now I haven’t heard anything that leads me to believe it’s the right tool for my needs. But then, there’s Sketch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*TnME0_NHK7UiMjAIAIiHSg.png" /></figure><h3>Sketch</h3><p><a href="https://www.sketchapp.com/">Sketch</a> is awesome. Sketch (in my opinion) is the coolest kid on the playground, and everyone wants to be friends with Sketch (sorry Windows users). Sketch is made for atomic design, it allows you to create user interfaces based on styles and symbols, and nested symbols (symbols within symbols), that are all configurable per instance, and not to mention intelligently scaleable. It’s fast - really fast - and can handle projects with dozens of artboards without any lag. Possibly the best part about Sketch is its plugins and integrations. One of the major losses I experienced when moving from Adobe XD to Sketch was losing the built in prototyping, but you have options. The wonderful people over at <a href="https://www.invisionapp.com/">InVision</a> have developed an amazing plugin for Sketch (and Photoshop) called <a href="https://www.invisionapp.com/craft">Craft</a>.</p><p><a href="https://www.invisionapp.com/craft">Craft</a> helps facilitate and automate several aspects of a typical design flow. It provides a one-click export feature of all (or selected) artboards to InVision for creating low fidelity prototypes, it also allows you to auto generate style guides, integrate real content into your designs, and create repeatable regions such as articles or cards. But that’s not the greatest part, InVision have very recently added a new feature to their already awesome product, that goes by the name of <a href="https://www.invisionapp.com/feature/inspect">Inspect</a>. <a href="https://www.invisionapp.com/feature/inspect">Inspect</a> allows users to open any of the artboards uploaded and inspect sizing, font styles, colors, spacing, icons and more, and export assets at various resolutions such as @2x and @3x for iOS. But, now that I’ve sung the praises of InVision and Craft, I have to tell you that it’s actually not my first choice for inspecting designs, generating style guides and exporting assets. My first choice is Zeplin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*6o5U7mRXFVBr9cuN7sERjA.png" /></figure><h3>Zeplin</h3><p><a href="https://zeplin.io/">Zeplin</a> is a tool built specifically to provide designers the ability to effortlessly export design specifications and assets for developers. Zeplin has plugins for both Sketch and Photoshop, and with a simple keyboard shortcut (Cmd + E) or click of a menu option, you can export all selected artboards directly into Zeplin. Zeplin will automatically create a style guide of all colors and font styles, and make and generate downloadable assets at all the necessary resolutions depending on platform and pixel density @1x or mdpi for example (iOS or Android respectively). Where Zeplin has an edge over Inspect is the granularity of the inspectable elements. InVision’s Inspect, in my opinion, offers far too much detail and granularity, it shows every last detail of how you structured your Sketch design, elements within elements, groups within groups etc etc, some of which are completely irrelevant to your developers. Zeplin allows you to control the complexity of the inspectable elements, making designs far less complex for developers to inspect. “But wait, what about basic low fidelity prototyping?”, you ask. Well, that’s where Framer comes in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*fh9V0IAuX0tw7HhEdoZ75w.png" /></figure><h3>Framer</h3><p><a href="https://framerjs.com/">Framer</a> is a tool originally built to provide designers the ability to create high fidelity interactive prototypes of specific interactions or animated transitions. The biggest challenge with Framer is that you need to write code in order to use the tool, CoffeeScript to be specific. Facebook have recently released a refreshed version of their own prototyping tool called Origami Studio which does not require you to know code, it works with drag and drop patches of logic, which allow you to create very intricate prototypes, but in my experience Origami’s prototypes performance is a bit laggier than that of Framer, and having worked as a developer I enjoy the coding aspect of Framer over the drag and drop process of Origami. Framer have also very recently released a new feature called Auto-Code for Animation Design, which makes designing complex animation very simple via a very familiar inspector. But it really is down to personal preference, both really are great tools, and both play beautifully with Sketch. Framer provides a very simple import facility of any open Sketch file, while Origami has an export plugin for Sketch.</p><p>Another major attribute that Framer has in its favor is its latest released feature, Framer Flows. An incredibly easy and simple way to create end-to-end screen flows for an entire prototype, it allows you to create platform specific screen transitions and popups/overlays as well as sticky nav bars and tab bars for scrollable pages, across pages within a multiple artboard Sketch file. This feature allows you to create incredibly native-feeling, high fidelity prototypes with minimal effort, almost as little effort as Adobe XD’s built in prototyping, but with far more impressive results. Framer also allows you to share prototypes with anyone, via a web link, something that Origami Studio is sorely lacking.</p><h3>Conclusion</h3><p>So, to wrap this up in a bow (for those of you who chose to skip to the end), if you’re in a position where you need to design UI, produce specs, assets and style guides and prototype the finished product, then the 3 tools I recommend you use, are <a href="https://www.sketchapp.com/"><strong>Sketch</strong></a>, <a href="https://zeplin.io/"><strong>Zeplin</strong></a>, and <a href="https://framerjs.com/"><strong>Framer</strong></a>.</p><p>Other great tools mentioned in this article include:</p><ul><li><a href="http://www.adobe.com/africa/products/experience-design.html">Adobe XD</a></li><li><a href="https://www.invisionapp.com/">InVision</a></li><li><a href="http://origami.design/">Origami Studio</a></li><li><a href="https://www.figma.com/">Figma</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=754cb1f94ebb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framer-prototyping/https-medium-com-brett-white-my-3-top-ux-design-tools-754cb1f94ebb">My top 3 UX design tools</a> was originally published in <a href="https://medium.com/framer-prototyping">Framer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>