<?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 Michael Todd on Medium]]></title>
        <description><![CDATA[Stories by Michael Todd on Medium]]></description>
        <link>https://medium.com/@michaeldtodd?source=rss-ac55381d8680------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*R-87Fot6Xw8c3oax9NfPiQ.png</url>
            <title>Stories by Michael Todd on Medium</title>
            <link>https://medium.com/@michaeldtodd?source=rss-ac55381d8680------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:17:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@michaeldtodd/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[Design Through Code: A Solo Creative Technologist’s AI-Driven Workflow]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Design through building. Iterate fast with AI. Live in the code. This roughly summarizes how I work these days. I started learning to code&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/ui-ux-code/design-through-code-a-solo-creative-technologists-ai-driven-workflow-7e268409b680?source=rss-ac55381d8680------2">Continue reading on UI/UX/Code »</a></p></div>]]></description>
            <link>https://medium.com/ui-ux-code/design-through-code-a-solo-creative-technologists-ai-driven-workflow-7e268409b680?source=rss-ac55381d8680------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e268409b680</guid>
            <category><![CDATA[creative-technologist]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[ai-tools]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Michael Todd]]></dc:creator>
            <pubDate>Fri, 07 Aug 2026 04:39:07 GMT</pubDate>
            <atom:updated>2026-08-07T04:41:27.129Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Pride Guide — an interactive guide to queer flags and their meaning]]></title>
            <link>https://medium.com/@michaeldtodd/pride-guide-an-interactive-guide-to-queer-flags-and-their-meaning-1c085435a83b?source=rss-ac55381d8680------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c085435a83b</guid>
            <category><![CDATA[advocacy]]></category>
            <category><![CDATA[lgbtq]]></category>
            <category><![CDATA[pride]]></category>
            <category><![CDATA[queer]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Michael Todd]]></dc:creator>
            <pubDate>Thu, 30 Apr 2026 16:55:39 GMT</pubDate>
            <atom:updated>2026-05-06T03:38:58.898Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_tfCxBYyaH81_DtjgIdXoQ.gif" /></figure><p>A digital guide to pride flags, representing the various orientations, genders, and more of the queer community.</p><p>Experience it at <a href="https://pride-guide.com/">pride-guide.com</a></p><h3>Overview</h3><p>Pride Guide is an educational app celebrating the diversity and beauty of the LGBTQIA+ community through its flags. It features an immersive flag explorer covering 18+ flags, their history and color meaning, an interactive 10-question quiz for those looking to test their queer flag history knowledge, ally guidance, and a print shop. As a solo passion project, my goal was to build on prior research of queer pride flags to create a digital online resource accessible to all.</p><h3>Motivations</h3><p>Before delving into the project itself, I want to express why this project matters and what prompted the idea behind it. Though this project was preceded by a couple of different print projects created many years prior, what ultimately motivated me to spend the time creating Pride Guide is the increasing dangerous rhetoric, ill will, and abuse of the queer community as a political talking point to amass votes as a means to maintain or grow political power.</p><p>My goal with Pride Guide is to simply do my part by participating. To advocate. To celebrate. To educate. Through recent decades, our community has seen tremendous growth in support. But the current political landscape is trying to push us backwards. As a gay man, I want to continue to have the freedom to marry my male partner and not fear that right may be taken away. But using our votes and voices to fight against our abusers is not the only way to seek positive changes. I believe that creating a space online for all of us to enjoy and learn from can help us discover and celebrate the vast richness of our community, building love and light to spread and share.</p><p>Now, with that out of the way, let’s get into how this specific project came about.</p><h3>Background</h3><p>At a previous role, I volunteered to help my employer participate in Atlanta Pride. I designed swag to wear and hand out in the parade. We came up with various ideas such as stickers, bandanas, and t-shirts. But the two most successful ideas were pocket-sized guides intended for the queer community. The first was a small foldable guide to Atlanta resources for the LGBTQIA+ community, listing organizations where individuals could go to receive support.</p><p>In a later year, we designed the 2nd guide, which showcased 13 of the most common pride flags, most of which represent specific groups within the community, such as the transgender, intersex, or pansexual identities. We wore matching-themed t-shirts and passed these out to the crowd as we made our way through the parade. As we handed them out, we saw faces light up with huge smiles and bright eyes as recipients unfolded the guides and discovered what they were. People loved them. And it was so heart-warming to watch as I sat in the back of the pickup truck with a large box, grabbing handfuls and passing them to my coworkers who were taking them to the crowds and coming back for more. I knew I needed to take this project further.</p><p>While at that same job, I also volunteered as a leader within the company’s employee resource group (ERG). One of our projects was an internal digital resource aiming to educate fellow employees about queer identity as well as offering advice for allies to better support us with specific ways the LGBTQIA+ community prefers to be supported. Because the flag guide was already created, it became the foundational starting point for the internal online resource.</p><h3>Research</h3><p>To build out the flag guide, I needed to do some research to understand where the various flag designs originated and what each was designed to represent. For example, I had known that the original pride flag had a different meaning for each color, but wasn’t sure what they were. I also knew there were additional flags I didn’t know much about, and some I had only seen once or twice before.</p><p>During my research, I realized there are many more flags out there that represent various genders, orientations, biological traits, and more. It’s truly extensive. I also learned about various terminologies such as “demigirl” and “demiboy”, which seemed fitting for a trans friend of mine who had not yet discovered those terms herself. A whole new world opened up to me. And I went exploring.</p><p>As a result, I had found way more flags than what could fit in the printed guide; and more than I had time to write about in the company’s internal resource I worked on through the ERG. So I picked the most common and a few lesser known — just enough to help spread awareness and draw more people into the conversation.</p><h3>Going digital</h3><p>Building the internal company resource sparked the idea to create something public for everyone. And in 2025, I finally started exploring it. Given that we’re not living in the “AI era”, if you will, I was testing various vibe-coding tools to see how they performed. So initially, this project was an excuse to play around with Lovable and see what kind of results I’d get. It seemed to be one of the better choices at the time for design-focused prototypes.</p><p>I didn’t really have a design in mind, yet. And I was curious what the tool would come up with. So I just loosely described what I was looking for and let it cook. As expected, the design it came up with was mostly uninspiring. But it was a place to start. What I did appreciate, though, was the inclusion of a couple features I didn’t directly ask for. One was the inclusion of a quiz, which would add more user engagement. The other was content meant for allies, sharing recommendations on how they can best support queer individuals with their own behavior. That’s helpful because while good intentions are appreciated, they don’t always have the desired results. So providing some guidance and simple reminders can go a long way.</p><p>At this stage, it was a simple one-pager with a hero, simple nav, and grid with placeholders for the flags, which would be the main focus. I had some ideas for the hero section and played with that for a while before moving on to the flags.</p><h3>Early inspiration — animated flags</h3><p>One idea I had was to try animating the flags to add more life to the page. I got curious and went looking around for some ideas. Little did I expect to find the <em>perfect </em>inspiration! Josh Comeau is an experienced software engineer from Montréal. In the summer of 2023, he posted an article about his <a href="https://www.joshwcomeau.com/animation/pride-flags/"><strong>Animated Pride Flags</strong></a>. He developed a method to split flag designs into vertical strips and apply looping CSS animations to shift each strip’s position up and down with a short delay per strip, creating a sort of waving effect. He shares his approach in a tutorial using React, HTML, and CSS. It’s fantastic. And it was an excellent source of inspo for the guide, helping solidify the primary design element moving forward.</p><h3>Color theming</h3><p>One of the other fun parts of this process was going beyond standard light and dark color modes. Because this project is inherently colorful with a variety of pride flag designs, it warrants having some fun with how the content and controls are expressed through color across the interface. I had already wanted to explore color theming more deeply anyways, so this was a great excuse to do that. What came to mind was trying a “chill wave” theme. Chill wave, as a music style, is something I really like listening to. And I thought it might translate well to a UI theme. So I thought I’d give it a shot. This was another experiment I wanted to give to an AI model and just see what it came up with. In one of the earlier iterations of the UI, I also suggested it try adding a glowing neon effect around parts of the UI. Where the project landed, the “Chill Wave” theme is basically a dark mode-derivative theme that uses warmer pink and orange as accent colors whereas the dark theme uses cooler blue accents. It’s also the default theme. It could be pushed further, but I think it works well for launch. I’ll likely explore adding more themes in the future.</p><h3>Accessibility</h3><p>In the spirit of inclusivity, designing and building for everyone needs to be a priority. Thankfully, building with UI frameworks like Radix makes accounting for accessibility much more approachable. Things like keyboard navigation, focus management, and more are already accounted for in their prebuilt components. Additionally, I made sure to account for reduced motion preferences and color contrast. And as I used agentic AI models throughout the build, I ensured they followed suit, set AAA compliance as the bar, and ran occasional checks.</p><h3>Design iterations</h3><p>Lastly, let’s talk about the iteration process. Because this project was a bit unique, given it wasn’t for a client, didn’t have a project brief, and was partially an experiment to test new AI-powered tools, it started out extremely loose and lacking in clear direction. But as the project formed, it became more clear step-by-step what about the design and UX worked and what didn’t. The early designs were too flat, boring, and didn’t excite me. A grid of 17+ flags built with HTML, all animating in loops was not performant. Component styling was too basic, out-of-the-box. And the one-pager design left it feeling too lightweight to have the level of significance I wanted.</p><p>Playing around with component styling, transitions, and small layout changes only got me so far. I wasn’t feeling inspired yet. And to be honest, I was relying way too much on just “vibe-designing” new solutions. I eventually had a reset in my process. I went looking for more design inspiration and started collecting various design samples from unique web animations to colorful digital art, and pieces that could be reimagined into a web interface.</p><p>After sleeping on the new inspo board and taking a couple breaks from the project, I came back refreshed and started breaking down the project, looking at it from a different angle. In summary, here are several steps I took to reimagine the project into something more custom that I could be proud of:</p><ul><li>selected a new set of fonts to be used across the project</li><li>extracted the hero section into its own landing page that describes the project; includes a loading animation</li><li>nixed the flag grid + per-flag dialog pattern in favor of a one-at-a-time full-page carousel to provide a far richer and more focused experience per flag while simultaneously improving performance by only displaying a single animated flag at a time</li><li>divided up the other sections into their own pages (quiz, ally guide, and about); later added a print shop page</li><li>created display settings to control the animated flag’s visual styling, which also gets set to random values on page reloads by default</li><li>experimented heavily with a “docked” navigation for easy access to settings</li><li>performed heavy responsive testing, re-designs, and tweaking</li><li>added an experimental GIF export option to allow visitors to save a copy of the animated flag they’re currently viewing as a GIF, including the same styling currently being used</li></ul><p>So in the end, what started as a complete experiment in leveraging AI to design and build a conceptual project ended up becoming a much more thoroughly designed and heavily refactored web app that I’m pretty happy with. Now, it’s time to get it out there and share it with the community.</p><h4>Experience it at <a href="https://pride-guide.com/"><strong>pride-guide.com</strong></a></h4><h3>Want to collaborate?</h3><p>If you’re interested in collaborating with me on this or future projects, reach out via <a href="https://www.michaeldtodd.com/get-in-touch"><strong>my contact form</strong></a>. I’d love to get introduced and see what we could create together! Thanks for visiting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c085435a83b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a Design System at a Young SaaS Company — The Process, the Tools, and the Burnout]]></title>
            <link>https://medium.com/ui-ux-code/creating-a-design-system-at-a-young-sass-company-the-process-the-lessons-and-the-tools-91ce57f643b8?source=rss-ac55381d8680------2</link>
            <guid isPermaLink="false">https://medium.com/p/91ce57f643b8</guid>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Michael Todd]]></dc:creator>
            <pubDate>Wed, 29 Apr 2026 04:36:33 GMT</pubDate>
            <atom:updated>2026-04-30T04:05:38.015Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9jVj-KwOFRdap-nGm_0UoQ.png" /></figure><h3>Creating a Design System at a Young SaaS Company — The Process, the Tools, and the Burnout</h3><h4>A Look Back at an 8-Year Journey as a UI Designer Within a Growing SaaS Company.</h4><p><em>For context, this timeline begins in 2015. If you were working in software at the time, you’ll remember tools like Sketch, InVision, and Bootstrap.</em></p><h3>Background</h3><p>Back in January of 2015, I joined CallRail’s four-person UX team as their second designer and first full-time UI designer. We were approaching 30 employees across the company and beginning to grow out of our startup phase and transition into a more mature, mid-size SaaS company. I could tell the team had built a solid product and foundation for the company’s growth. But there was one giant hole that needed filling: design documentation — none existed.</p><p><strong>Design documentation</strong> is generally a collection of notes and specs on various visual patterns (like UI), interactions (how users interact with your UI), UX patterns (different types of user flows used in your product), content strategy, and brand design. This information and the process around creating and maintaining it are essential for scaling and maintaining a product, especially in terms of QA. Add in the associated front-end engineering documentation, tools used across design and development to create and maintain your design patterns, and all the processes that tie them together… and you get your <strong>design system</strong>.</p><h3>The Problem — Inconsistency &amp; No Documentation</h3><p>In my first week on the job, my director asked me to start defining rules for color, border, spacing, etc. His example was showing how we had inconsistent styling for text inputs — just one UI component needed height, border color, border width, border radius, text color, font size, padding, and margin defined. To get some sort of baseline, I pulled examples from our existing form text inputs, made a reference design file, and documented all the styling. Little did I know this was only the beginning of a longer journey to track down and define <em>everything</em>.</p><p>At this stage of the company, we had a front-end CSS framework (Bootstrap) to manage the overall structure of how we built our pages, but lacked a style guide or any kind of design documentation to standardize styling and streamline the design and front-end build process. We found several style variations of the same design components across different files and within the app itself. It was impossible to tell which instances were considered <em>correct</em> ones to model after. Every time anyone needed to mock up a new screen, we had to search for existing instances of each UI component across multiple files and copy them into a new design file. You get where I’m going with this — it was painful, frustrating, and time-consuming.</p><p>Lack of design documentation limits productivity across teams, causes UI, UX, engineering, and QA staff to work harder than necessary, and causes quality concerns for your product’s interface due to inconsistencies and fragmented user experiences.</p><h3>The Solution — Create a Source of Truth</h3><p>We realized we needed to begin standardizing and cleaning up our styling. But before establishing new standards, we had to account for all the UI patterns that needed to be standardized into components. So we performed an audit: combing through every page of the app to look for every unique pattern and listing them in a spreadsheet to group them and add other details for the next stage — building a style guide. This was painful and time-consuming but done slowly over several weeks, with the 2 designers on our team dividing the workload.</p><h3>Our First Style Guide</h3><p>Once we finished building the spreadsheet, we had a clearer picture of what needed designing and documenting. The groupings settled into things like alerts, typography, modals, buttons, forms, etc. We started putting together a new reference file in Sketch with examples of all the UI patterns found during our audit, grouped and organized as well as possible. Visualizing each set helped us get a better grasp of what we had and what needed attention: inconsistent typography styling, mismatching colors, seemingly arbitrary spacing patterns or lack thereof.</p><p>Each major grouping from the audit mapped to an artboard in the Sketch file. On each artboard, we defined related UI components, their styling, and added documentation for our engineering team so they knew exactly what styling had been established as standards moving forward. We then shared this file via an InVision clickable prototype that any engineer could easily browse to see its contents.</p><p>On the engineering side, we created a new code repository <em>separate</em> from our main code base to house just our app’s styling. We built a new internal site displaying examples of all UI patterns in a similar fashion to how we had laid them out in the Sketch file, which became a clickable prototype in InVision. The coded version became the product — our first official “Style Guide,” as we called it. This was a huge leap forward for our team and the state of design at the company.</p><h3>From Style Guide to UI Kit</h3><p>Over time, the Style Guide evolved from being just a gathering of styling options and basic examples into a comprehensive resource. We added more interactive patterns, code samples, diverse documentation, and relied on it increasingly as a source of truth for what our UI patterns looked and behaved. As a result, the InVision prototype became redundant since the coded version was now the product: our “UI Kit.” Around this time, we also renamed “Style Guide” to “UI Kit,” fully establishing it as not just documentation but an internal tool regularly used by both UX and Engineering teams. It became the <strong>single source of truth</strong>, even over the Sketch library, which established patterns <em>before</em> being translated into code and adopted into the UI Kit afterwards.</p><h3>Maintenance and Growth</h3><p>As the team adapted to referencing our design patterns in the UI Kit before building new pages and features, the next big challenge became apparent: maintaining and evolving our patterns and the tools we use to build them. Originally, anyone on the engineering team had free rein to modify the UI Kit at any point (though a code review process existed). But this proved challenging for engineers less fluent in front-end development, especially CSS. It was hard to police updates and maintain a clean and orderly set of standards. Often, different product teams planned new projects requiring design pattern changes or new components not yet built, leading to “scaled-back” projects that butchered the UI/UX to save time.</p><p>To address this, we decoupled UI Kit updates from project requirements, essentially making them <em>prerequisite tickets</em> that could be scoped and planned independently. We introduced a dedicated team for UI Kit and design pattern updates consisting of a product manager, two front-end-capable engineers, and myself as the UI design lead. This structure allowed us to <em>work ahead</em> of other teams so they wouldn’t have to rescope or stop to address UI needs. It also helped ensure strong front-end resources focused on improving our user interface and experience overall.</p><h3>Evolving from UI Kit to Design System</h3><p>In December 2018, I attended a conference called <strong>Clarity</strong> after an Atlanta meetup by its founder. This gave me <em>clarity</em> on what we had been chasing with our “design patterns” in the UI Kit — essentially building a design system: a network of design patterns and components that fit together and work, inform one another, and create identity around an interface, brand, and experience. Meanwhile, the marketing team was working hard to redefine and elevate our brand and online presence outside the product. Collectively, these improvements created what we knew as our “Design System.”</p><h3>Migrating to Figma</h3><p>One of the biggest changes on the road to a design system was migrating from Sketch to Figma in 2019. In Sketch, we edited files independently and synced them via Dropbox. The Sketch version of our UI Kit synced to Sketch Cloud as a shared library. But Figma offered live collaboration, instant file saving with native version history, built-in file storage with team and project structures, and more design system-oriented features that were too much to ignore. I had learned more about it at another Clarity conference and decided to give it a try, ultimately getting buy-in for the team to switch over. It was a game-changer.</p><h3>New Challenges</h3><p>Of course, positive change often comes with new challenges. The 2020s brought new ups and downs in how tech companies operate. One month, layoffs; the next, hiring sprees. You had to roll with the punches in an increasingly volatile industry where teams were expected to move faster while given fewer resources. Though this is where a design system can make or break productivity, its efficacy depends on how mature it is.</p><p>Some of the challenges we ran into involved scaling the design system, improving documentation, encouraging collaboration and inclusivity around its development, and bridging changes happening across product and marketing teams. In 2023, we explored creating a Design System Guild to bring together anyone interested in supporting it through discussing pattern needs, technical challenges, roadmapping, and cross-team/departmental alignment. This was honestly a mixed bag of success and struggle due to conflicting opinions and a lack of official support from the org.</p><h3>The Corporate Tech Rollercoaster</h3><p><em>From here, I’m going to get more personal and a little bit raw about my experience working in tech. It won’t be focused on process or tooling but will be focused on lessons.</em></p><h3>The 2020’s Curse</h3><p>The 2020s brought new ups and downs not just for the world but also for the workplace: fires, wars, a global pandemic, mass layoffs, hiring sprees, more layoffs. It was a lot. And even if we isolate the chaos to what happened in the workplace, losing some of your best coworkers, jobs, or spouses/partners who lost theirs is hard, it was still devastating. You don’t recover from that quickly.</p><p>This is where things started to fall apart for me: stress from world events, losing people at work, constantly changing priorities, several years of corporate capitalism was beginning to take their toll. It became harder to roll with the punches as I began wearing thin. There were fewer wins, more uncertainty around job security, growing concerns about pay inequity. I realized what I really needed was stability above all else: knowing what was coming next — good, bad, or otherwise. I started to become cynical, closed off, and apathetic even when positive news about design systems felt too unlikely to happen. So I began quietly quitting as a way to self-preserve and protect my energy.</p><h3>The End of an 8-Year Journey</h3><p>By summer of 2023, I made the decision to get off the rollercoaster and stop giving so much energy to my job. My mental health was in decline, and it needed to come first. I spent a few months winding down my role, helping the team plan ahead and ensuring my direct report would be well-supported with what she needed to move things forward. Though I didn’t want her to feel abandoned, I took solace in knowing that I wouldn’t be a barrier to her career growth. Leaving behind people I had become so invested in was hard, but we left on good terms and stayed in touch.</p><p>My story doesn’t end here. There’s much more I want to share about what I learned while taking time for myself — burnout, healing, letting go, discovering new ways to solve old problems — all before AI even enters the picture. If you found any of this insightful, stay tuned for the next chapter. I’ll be sharing more soon.</p><h3>A Quick Thank You</h3><p>If you got this far, I sincerely thank you for taking the time to read about my journey. I hope you found something positive or helpful in it. I write as a way to give back to the design and tech community because I’ve found it invaluable learning about others’ experiences. So please pay it forward by leaving a comment or sharing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91ce57f643b8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ui-ux-code/creating-a-design-system-at-a-young-sass-company-the-process-the-lessons-and-the-tools-91ce57f643b8">Creating a Design System at a Young SaaS Company — The Process, the Tools, and the Burnout</a> was originally published in <a href="https://medium.com/ui-ux-code">UI/UX/Code</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Encouraging Adoption in Your Design System]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Thoughts and examples based on my personal experience from building a design system over 7 years.</p><p class="medium-feed-link"><a href="https://medium.com/ui-ux-code/encouraging-adoption-in-your-design-system-9136ae869c62?source=rss-ac55381d8680------2">Continue reading on UI/UX/Code »</a></p></div>]]></description>
            <link>https://medium.com/ui-ux-code/encouraging-adoption-in-your-design-system-9136ae869c62?source=rss-ac55381d8680------2</link>
            <guid isPermaLink="false">https://medium.com/p/9136ae869c62</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[design-management]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[sass]]></category>
            <dc:creator><![CDATA[Michael Todd]]></dc:creator>
            <pubDate>Wed, 21 Dec 2022 07:37:27 GMT</pubDate>
            <atom:updated>2022-12-21T20:20:30.318Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[My role as a Design Systems Manager at a growing SaaS Company]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/ui-ux-code/my-role-as-a-design-systems-manager-at-a-growing-saas-company-f09fcb39960b?source=rss-ac55381d8680------2"><img src="https://cdn-images-1.medium.com/max/2600/1*5p9oYDvoy-kJjfiCoPSBJA.png" width="2800"></a></p><p class="medium-feed-snippet">Six years in at a quickly growing SaaS company where I began as a midlevel UI designer, here&#x2019;s what my role looks like today.</p><p class="medium-feed-link"><a href="https://medium.com/ui-ux-code/my-role-as-a-design-systems-manager-at-a-growing-saas-company-f09fcb39960b?source=rss-ac55381d8680------2">Continue reading on UI/UX/Code »</a></p></div>]]></description>
            <link>https://medium.com/ui-ux-code/my-role-as-a-design-systems-manager-at-a-growing-saas-company-f09fcb39960b?source=rss-ac55381d8680------2</link>
            <guid isPermaLink="false">https://medium.com/p/f09fcb39960b</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[design-system-manager]]></category>
            <category><![CDATA[tech-companies]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Michael Todd]]></dc:creator>
            <pubDate>Sat, 02 Jul 2022 17:09:38 GMT</pubDate>
            <atom:updated>2023-06-05T04:06:48.374Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Designing for Code — SVGs]]></title>
            <link>https://medium.com/ui-ux-code/designing-for-code-svgs-496050dae1a6?source=rss-ac55381d8680------2</link>
            <guid isPermaLink="false">https://medium.com/p/496050dae1a6</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[svg]]></category>
            <dc:creator><![CDATA[Michael Todd]]></dc:creator>
            <pubDate>Tue, 26 Jun 2018 18:11:37 GMT</pubDate>
            <atom:updated>2022-12-25T03:23:27.529Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>Setting up SVGs intended for animation and interaction design.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BQJvnwnHU2lCvpShyBTu4A.png" /></figure><h4><strong>Intro 👋</strong></h4><p>If you’re looking to add visual interest or interactivity to a website or webapp, SVGs are a fantastic option for visuals. Since they’re vector-based, you get unlimited scalability and clarity compared to raster and bitmap images. And because they’re made up of code, you can manipulate every single shape with CSS — add animations, interactions, or dynamically change the color scheme—something that you cannot do with icon fonts. However, as with any method of coding, there are many things to watch out for to avoid making writing or maintaining code any harder than it has to be. This article aims to cover how that applies to creating SVGs that are intended to be animated.</p><h4>Who is this article for?</h4><p>Web, UX, or UI designers who want to create <strong>animated SVG </strong>graphics (icons, illustrations, etc.) for the web.</p><h4><strong>What will you get out of this article?</strong></h4><p>A step-by-step guide on what to do with your SVG graphics <em>after</em> you’ve designed them and <em>before</em> you start animating them with code. Nothing in this guide is <em>required</em> to add animations to SVGs. But it will make your life (or the life of whoever is adding the animations) much much easier, as well as avoid creating potential bugs or code conflicts.</p><h4>Why SVGs?</h4><p>Need some selling points to your manager or developer on why you should SVGs? I’ve got a shortlist <a href="https://medium.com/ui-ux-code/why-you-should-use-svgs-f2600a801a54">here</a>.</p><h3>Step By Step Instructions 📝</h3><p>If you haven’t created your graphic, yet, go ahead and read through section 2 (Clean up your design), as some of those steps can be done <em>during</em> the design phase to save you time. I personally recommend working in Sketch, especially if you’re creating icons, because it’s specifically intended for creating web graphics. Some of the steps in this guide are also easier to perform in Sketch. But if you’re making more complex illustrations, you may find it better to design in Illustrator. If you’re using a design tool other than Sketch or Illustrator, you’re probably fine, but may run into questions not anticipated in this guide. You can also try opening your design in Sketch if saved as an SVG.</p><p><em>Note: These steps are simply advisories for best practices. They are not required. Furthermore, if you’re not animating individual layers inside the SVG — for eample, basic hover states such as scale or rotate that would also work on a JPEG or PNG — this guide is not necessary and will have no affect on your animation.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aDcyn00zXDwQO1m7KvfcZA.png" /></figure><h3>1 ) Clean up your design</h3><p>This section focuses on things you can do in your design software to help clean things up and avoid issues later on.</p><h4>Setup your file</h4><p><strong>Sketch:</strong> If you’re working in Sketch, either create a new artboard with the graphic you want to export or create a new file with just the graphic. Either way, make sure you keep a copy of the original graphic in case you want to change the design later.</p><p><strong>Illustrator: </strong>If you’re working in Illustrator, it’s best to make sure the only layers in your file are part of the graphic you plan to export. Keep a copy of the original file in case you want to change the design later.</p><h4>Vectorize strokes</h4><p>Web browsers sometimes have trouble rendering strokes that are aligned to the <em>inside</em> or <em>outside</em> of their shapes. I recommend either re-constructing those lines to be center-aligned <em>or</em> flattening them to solid shapes to avoid potential rendering issues in the browser. Or, to make things even simpler, any strokes that you <em>do not</em> plan to animate, go ahead and flatten to filled shapes just to be safe. If you do leave strokes aligned to the inside or outside, make sure you do thorough browser testing once it’s been exported to SVG. <strong>Tip:</strong> Check out this great tutorial from CSS Tricks on <a href="https://css-tricks.com/svg-line-animation-works/">SVG line animation</a>.</p><h4>Outline text</h4><p>Rendering live text inside an SVG is possible, but requires the font being made available in the web page where the SVG is being displayed. So unless you need the text to be actual text and you’re able to serve up the font file it needs, you’ll need to convert it to outlines.</p><h4>Add a container</h4><p>If you select your artboard and export it as an SVG, design software usually does not honor empty white space and crops it out. So if your graphic needs white space around it, add a transparent rectangle in the back to enforce a bounding box.</p><h4>Round to nearest whole pixel</h4><p>This is more important the smaller your graphic is. Keep in mind that you’re designing for the screen, which means each pixel is a perfect sqaure. If you have any straight lines or edges that don’t sit exactly between pixel grid lines, that’s going to result in a fuzzy line, especially on screens with lower pixel density (non-retina). Your graphics will look more crispy and clear across all devices if they’re pixel-perfect, especially if adding animation causes your viewer to pay more attention to the deails. If your design software offers a pixel preview, you can use that to test the results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*XbJ1JcnV3WZeGg9YBRCDQw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*QmcdfsWkj5jRLNGPR_hOUA.png" /><figcaption>Pixel grid view of a 1px horizontal line</figcaption></figure><h4>Check rounded corners</h4><p>Let’s say you have a rectangle that’s 10px tall with rounded corners set all the way up to 100px. A radius more than a 5px (half the rectangle’s height) won’t actually look any different, just yet. But if the height on the rectangle increases once it’s been animated, the border radius <em>will also </em>grow if it can. So just keep in mind that if you want your border radius to stay fixed, make sure it’s set to exactly the size you want before exporting your SVG. As of this writing, Sketch v 50.2 automatically reduces the border radius on a shape if you apply a radius beyond what it’s capable of rendering, unless you override it in the text field. So if you’re using Sketch, you may be able to ignore this step entirely. <strong>Tip: </strong>You can also override a border radius with CSS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4qBjRMwU6mDIDJGacLDD1w.png" /><figcaption>Comparing border radius (rounded corners)</figcaption></figure><h4>Check for raster images</h4><p>If you have any raster or bitmap images <em>inside</em> your graphic, those can be embedded or linked. Embedded images get converted to Base64 code when saved/exported. Linked images (an option in Adobe Illustrator) requires that you store the image outside of the SVG somewhere, which can allow the image to be updated independently of the SVG code. If you’re working with a developer, just be sure to check in with them and decide which method is most appropriate for your situation.</p><h4><strong>Limit groups</strong></h4><p>Using groups can be helpful in keeping your design files organized and easy to edit later. But when applying animation, simplifying your layer structure can help you focus on just the few parts of your graphic you want to animate. Additionally, for every group in your file, there are 2 extra lines of SVG code. So keep things simple by reducing the number of groups to the essentials that you plan on animating.</p><h4>Limit layer names</h4><p>When your SVG gets exported, all group and layer names will be converted to id tags. And chances are you have a ton of layers with pretty generic names. For example if you duplicated an oval multiple times, you may have something like “Oval 1”, “Oval 1 Copy”, “Oval 1 Copy 2”, etc…Most likely, those names aren’t going to be helpful to you at all and will be a nightmare to get rid of in the code. I’ll explain more on why they would need to be removed under <strong>Clean up ID tags</strong>, down below. For now,<strong> </strong>here’s what you can do in your design file to help make the code far more manageable:</p><p>Imagine all the layer names in your file disappeared and you only restored the most important layer names needed in order to navigate your file for applying the animations you have in mind. Which ones would you chose? Rename all non-essential layers to the same thing. For the purposes of this exercise, rename these layers to “#remove#” just because it’s super unique. This will save you <em>a ton</em> of time, later. And if you’re using Sketch, you can make this even faster by using the <a href="https://rodi01.github.io/RenameIt/">Rename It</a> plugin for bulk renaming layers in a flash!</p><h4>Separate responsive layers</h4><p>I’ll go more in depth on responsive SVGs in another article. But here’s the gist: to show different versions of your graphic under different situations, like screen sizes or hover states, separate those versions into different top-level groups in your design file. For example, your main groups might be named “Mobile”, “Tablet”, and “Desktop” or “Default” and “Hover”.</p><h4>Export/Save your SVG</h4><p>You’ve cleaned up your design file! Good job 👏. It’s time to export it.</p><p><strong>Sketch: </strong>If you’re using Sketch, select either your graphic or the artboard it’s sitting on and use Sketch’s Export menu in the bottom-right of the window. Your settings should look like the image, below. Click the “Export…” button and select where you want it to be saved. That’s it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/423/1*MmLXnZ5TOR1IUNNIY3w9iA.png" /><figcaption>SVG export settings in <strong>Sketch</strong></figcaption></figure><p><strong>Illustrator:</strong> If you’re using Illustrator, make sure your file is clear of anything you don’t want exported. Select File → Export… from the main menu. After you select where you want it to be saved and hit Export, you’ll see an additional menu:</p><p>Here are my recommended settings if you’re going to be animating the SVG. If you want to learn more about these settings, Adobe has the details <a href="https://helpx.adobe.com/illustrator/using/svg.html">here</a>. When you’re done, hit OK and you’re all set.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*YzhBAsCfyW7cm5b3wWzCEg.png" /><figcaption>SVG export settings in <strong>Adobe Illustrator</strong></figcaption></figure><h4><strong>Test your SVG</strong></h4><p>Now that your SVG has been exported, open it in your web browser to make sure everything looks good. If you made responsive layers, it’s going to look a little funky for the moment since they’re all going to overlap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QvAOKA8IQpWbtroD1gI0vQ.png" /></figure><h3>2) Clean up the code</h3><p>You’ve been a real trooper, so far. You did a bunch of work cleaning up your design file and got it exported to a slick SVG that’s almost ready to be animated. Hang in there! There’s not too much more to go!</p><p>Open the SVG you just exported in a code editor. If you don’t have one, check out <a href="https://atom.io/">Atom</a>, which is what I like to use. We’ll walk through how you can clean up the SVG code so that when you get started with adding animation code, you’ll have a clean and tidy file that’s easier to navigate.</p><p><strong>Tip</strong>:<strong> </strong>After each step, open the SVG in your web browser to make sure everything still looks okay just in case something goes wrong. If you made responsive layers, go ahead and comment out the non-default layers so you can see what your graphic should look like more clearly.</p><h4>Remove unnecessary tags</h4><p>Design software tends to add extra code that you won’t need in your file. Here are some things to look for that can be deleted:</p><p>XML tags:</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</pre><p>Auto-generated comments, titles, and description tags:</p><pre>&lt;! — Generator: Sketch — <a href="http://www.bohemiancoding.com/sketch">http://www.bohemiancoding.com/sketch</a> --&gt;<br>&lt;title&gt;Artboard&lt;/title&gt;<br>&lt;desc&gt;Created with Sketch.&lt;/desc&gt;</pre><h4>Clean up ID tags</h4><p>All group and layer names appear as id tags in the code. To avoid CSS conflicts, IDs should be converted to classes or simply removed if they’re not going to be used. For reference, these are examples of a circle with an id vs. class vs. comment:</p><pre>&lt;circle <strong>id=&quot;Dot&quot;</strong> fill=&quot;#D8D8D8&quot; cx=&quot;20&quot; cy=&quot;10&quot; r=&quot;41&quot;&gt;&lt;/circle&gt;</pre><pre>&lt;circle <strong>class=&quot;Dot&quot;</strong> fill=&quot;#D8D8D8&quot; cx=&quot;20&quot; cy=&quot;10&quot; r=&quot;41&quot;&gt;&lt;/circle&gt;</pre><pre><strong>&lt;!-- Dot --&gt;</strong><br>&lt;circle fill=&quot;#D8D8D8&quot; cx=&quot;20&quot; cy=&quot;10&quot; r=&quot;41&quot;&gt;&lt;/circle&gt;</pre><p>Back in the <strong>Limit Layer Names</strong> step, I recommened that you rename a bunch of layers in your design file to “#remove#”. If you did that, you can now bulk remove the IDs those turned into by using your code editor’s <strong>find and replace</strong> tool. In the <em>find</em> field, type id=&quot;#remove#&quot; and leave the <em>replace</em> field blank. If picked a different layer name, then type between the parentheses instead.</p><p>Now that all the extraneous IDs are gone, you can focus on the IDs that are left. Again, these should be converted to classes unless you have a specific reason to use an ID. To change each ID to a class, use <strong>find and replace</strong> again, but find id= and replace with class=. Or you can manually change them if you want to leave some as IDs. I recommend going one step further to make sure your ID and Class names are unique. I like using something relative to the specific SVG, like this:</p><pre>&lt;svg id=&quot;<strong>SVG-logo</strong>&quot;&gt;<br> &lt;g class=&quot;<strong>SVG-logo-top&quot;</strong>&gt;<br>  &lt;circle fill=&quot;#D8D8D8&quot; cx=&quot;20&quot; cy=&quot;10&quot; r=&quot;41&quot;&gt;&lt;/circle&gt;<br> &lt;/g&gt;<br> &lt;g class=&quot;<strong>SVG-logo-bottom</strong>&quot;&gt;<br>  &lt;circle fill=&quot;#D8D8D8&quot; cx=&quot;20&quot; cy=&quot;10&quot; r=&quot;41&quot;&gt;&lt;/circle&gt;<br> &lt;/g&gt;<br>&lt;/svg&gt;</pre><p>That way I know for sure it’s not going to conflict with anything else in the code where the SVG might be used.</p><p>Another handy thing you can to do make your code easier to navigate is to add comments above main sections of your SVG, like above groups. For example:</p><pre>&lt;svg id=&quot;SVG-logo&quot;&gt;<br><strong> &lt;!-- Top --&gt;</strong><br> &lt;g class=&quot;SVG-logo-top<strong>&quot;</strong>&gt;<br>  &lt;circle fill=&quot;#D8D8D8&quot; cx=&quot;20&quot; cy=&quot;10&quot; r=&quot;41&quot;&gt;&lt;/circle&gt;<br> &lt;/g&gt;<br><strong> &lt;!-- Bottom --&gt;</strong><br> &lt;g class=&quot;SVG-logo-bottom&quot;&gt;<br>  &lt;circle fill=&quot;#D8D8D8&quot; cx=&quot;20&quot; cy=&quot;10&quot; r=&quot;41&quot;&gt;&lt;/circle&gt;<br> &lt;/g&gt;<br>&lt;/svg&gt;</pre><p><strong>FYI:</strong> Those “&lt;g&gt;” tags in your code are your layer groups.</p><h4>Organize responsive versions</h4><p>If you made responsive layer groups in your design file, then you’re going to want to add some CSS to your SVG by creating a “style” tag inside your SVG:</p><pre>&lt;svg id=&quot;SVG-logo&quot;&gt;<br>  <strong>&lt;style&gt;<br>    // Add your responsive CSS here<br>  &lt;/style&gt;</strong><br>  &lt;g class=&quot;mobile&quot;&gt;…&lt;/g&gt;<br>  &lt;g class=&quot;tablet&quot;&gt;…&lt;/g&gt;<br>  &lt;g class=&quot;desktop&quot;&gt;…&lt;/g&gt;<br>&lt;/svg&gt;</pre><p>For now, just add some basic CSS to hide anything that shouldn’t show by default. Then you’ll be ready to preview your file in a web browser and make sure things are looking good. <em>More on responsive SVGs coming soon. Stay tuned.</em></p><h4>Save your file!</h4><p>Save your file and give yourself <strong>2 big pats on the back </strong>because you just completed a ton of really picky file prep!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WrZMionh2IlZ1s1Qr6XCVg.png" /></figure><h3>START ANIMATING!</h3><p>Now that your SVG is exported and cleaned, the real fun starts…adding animation! If you’re interested in another how-to with some tips, tricks, and examples, stay tuned. I’ll be posting another article on <strong>SVG animation</strong>, where we’ll delve into applying CSS animation into our beauiful new vector graphics. <strong>Get excited.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=496050dae1a6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ui-ux-code/designing-for-code-svgs-496050dae1a6">Designing for Code — SVGs</a> was originally published in <a href="https://medium.com/ui-ux-code">UI/UX/Code</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you should use SVGs]]></title>
            <link>https://medium.com/ui-ux-code/why-you-should-use-svgs-f2600a801a54?source=rss-ac55381d8680------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2600a801a54</guid>
            <category><![CDATA[svg]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Michael Todd]]></dc:creator>
            <pubDate>Tue, 26 Jun 2018 17:56:12 GMT</pubDate>
            <atom:updated>2018-06-26T18:28:23.136Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<h4>My shortlist on when to use SVGs over icon fonts or raster images.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LHAmyrAHgUSZ5Nqdc0X08Q.png" /></figure><h4>✨ Benefits of SVGs ✨</h4><p>If you need some selling points to your managers or developers on why your team should be using SVGs, here’s why I recommend them:</p><ul><li><strong>Resolution independence.</strong> Because they’re made to be scalable, there’s no need to export multiple sizes to accomodate different screen sizes, saving your team time and reducing maintenance.</li><li><strong>Smaller file sizes.</strong> This is because they’re vector-based instead of pixel-based (like JPEGs or PNGs). Smaller file sizes = faster load times.</li><li><strong>Responsive!</strong> A single SVG can include multiple variations and be made responsive through CSS, just like HTML. <em>An upcoming article will delve into responsive SVGs. Stay tuned.</em></li><li><strong>Interactive!</strong> Through CSS and JavaScript, you can bring icons and illustrations to life, improving user engagement and making your website or app visually dynamic. <em>I’ll also delve into this in an upcoming article on interactive SVGs!</em></li><li><strong>Color-dynamic.</strong> Let’s say you have a color palette that your icons and illustrations need to adhere to. Because SVGs can be styled with CSS, you can dynamically change their colors for different situations or even when updating brand colors. If you have a ton of icons and illustrations across your site and you need to shift your color palette across the board, you can either update/override colors with CSS <em>or </em>use a find/replace code method across all of your SVG files rather than manually updating a ton of images and re-uploading them all. This is particularly useful for white-label service! Combine this with <em>responsive</em> or <em>interactive</em> methods and the creative possibilities are endless.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6dNA1Cc-KQy5X9ivOLem9w.png" /></figure><h4>More writeups on SVGs:</h4><ul><li><a href="https://medium.com/ui-ux-code/designing-for-code-svgs-496050dae1a6">Setting up SVGs for adding animations and interactions</a> — Check it out!</li><li>Animating SVGs — <em>Coming soon!</em></li><li>Responsive SVGs — <em>Coming soon!</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2600a801a54" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ui-ux-code/why-you-should-use-svgs-f2600a801a54">Why you should use SVGs</a> was originally published in <a href="https://medium.com/ui-ux-code">UI/UX/Code</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ R.I.P. Paper, the best app ever created.]]></title>
            <link>https://medium.com/@michaeldtodd/r-i-p-paper-the-best-app-ever-created-af86a33b35e5?source=rss-ac55381d8680------2</link>
            <guid isPermaLink="false">https://medium.com/p/af86a33b35e5</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[paper]]></category>
            <category><![CDATA[facebook]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Michael Todd]]></dc:creator>
            <pubDate>Fri, 01 Jul 2016 05:26:05 GMT</pubDate>
            <atom:updated>2016-07-01T05:29:20.978Z</atom:updated>
            <content:encoded><![CDATA[<h4>Today, I received some very sad news…</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*qxpLN46_PGgeLV2X5hi57w.png" /></figure><h4>Paper, an alternative mobile experience for digesting posts, news, and articles shared on Facebook, will soon be shut down.</h4><p>For those unfamiliar with <a href="http://Paper%20–%20stories%20from%20Faceboo">Paper – Stories from Facebook</a>, it is arguably one of the absolute best mobile user experiences ever created. If you’ve not had the opportunity to use it, I’m truly sorry. You’ve missed out, but take a quick peek at this <a href="https://www.youtube.com/watch?v=Zq6-b9_V9lA">video review from 2012</a> by The Verge if you want to see more than some cached screen shots from the App Store (the app is no longer available to download). <em>Scroll to the end to see the official announcement.</em></p><h4>What I’m going to miss:</h4><p>To get back to my point of writing this, I wanted to share some of the main things I’ve loved about Paper that will sorely be missed by myself and other Paper diehards that will be clinging on for dear life until Facebook officially pulls the plug next month:</p><p><strong>Minimal interaction effort</strong>: Paper uses incredibly few buttons throught the app, providing a fluid navigational experience though swipe gestures, very similar to Pinterest’s mobile app.</p><p><strong>Incredibly simple and clean UI:</strong> Paper’s card-based UI creates incredibly clean and well-organized layout, making it stupid simple to understand hierarchy of information, improving readability of all content tenfold compared to Facebook’s traditional mobile app and web interface.</p><p>Combine the minimal interaction style with a clean and modern card-based UI, and you have an app that allows the user to quickly swipe between different views, categories, and settings without ever having to tap or move your finger to a specific part of the screen. Swipe anywhere. Instantly know what content you’re interested in actually viewing. Interact with comments. Post something new. It’s all so effortless and so so beautiful.</p><p>With a much simpler and far more enjoyable method of browsing content on Facebook, I immediately deleted the traditional app from my phone and have been incredibly happy with getting rid of it. Because Paper’s intent was to primarily be a method for browsing articles and news, I also felt compelled to ignore other news apps or websites. I just didn’t need them. I had everything I needed all right here in this beautiful interface that I couldn’t put down.</p><h4>Quite frankly, other apps just suck.</h4><p>The Facebook app, along with the desktop web interface is simply too visually cluttered and creates far too much friction to make it worth while browsing unless I’m just <em>that bored</em> and need something to pass the time. But I’ve made it a point to stop wasting time on my phone unless I’m actually enjoying the experience of using the app itself, not just because I want the content within it. Paper made that happen. I hated using Facebook before Paper came around. Discovering Paper simply prevented me from discontinuing my use of Facebook altogether (for the most part). I wouldn’t have been anwhere near as active on Facebook over the last couple of years, otherwise. I got addicted to the experience just as much as the need to check my phone to see what new notifications or content I can look at throughout the day.</p><h4>This is goodbye.</h4><p>Paper was only actively developed for about a year after it’s launch in 2014, as it was only intended to be experimental. After that, no features were added and bug fixes were rare. It has already been removed from the App Store, but users have been able to use it all along. But as of July 29th, 2016, Facebook will no longer allow Paper to connect to it’s services, meaning we won’t be able to login and see any content. It will die and it’s soul will float away into App Heaven.</p><h3>“Thank you for using Paper”</h3><p>Here’s the official announcement that appeared in my feed this afternoon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bvt97KfJLpvJ2asm5d5C8g.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af86a33b35e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Sketch Is the UI Designer’s Best Friend.]]></title>
            <link>https://medium.com/sketch-app-sources/why-sketch-is-the-ui-designer-s-best-friend-9497b9d80998?source=rss-ac55381d8680------2</link>
            <guid isPermaLink="false">https://medium.com/p/9497b9d80998</guid>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Michael Todd]]></dc:creator>
            <pubDate>Sun, 29 Nov 2015 17:02:39 GMT</pubDate>
            <atom:updated>2015-12-22T15:41:34.090Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QLBJ6ywa_QKRp6V055_sWQ.png" /></figure><h3>Why Sketch is the UI Designer’s best friend.</h3><p>If you’re a web/UI/UX designer, work with one, or would like to become one, this article is for you.</p><p>Earlier this year, I decided to check out this app called Sketch, which seemed to be an indie design tool that was getting more and more attention. I hadn’t thought much of anything that wasn’t an Adobe product to use for design. I assumed that newer tools, often found on the App Store for around $99, would be sub-par and probably a waste of money to try. Well, as it turns out, one of these newer inexpensive indie apps is actually one of the best design tools you can buy and absolutely fantastic for web and UI design. Here’s why it’s quickly become my new best friend:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IZCBBiXP2EzXAUbNEtMRLg.png" /></figure><h3>Let pages set you free.</h3><p>Let’s first assume you’ve at least moved on from Photoshop to Illustrator; and if you haven’t, I HIGHLY recommend researching the advantages of vector-based design and how these tools also tend to be better for responsive web design. It will change your life. If you do use Illustrator, then you know how useful it is to have multiple artboards to design with in a single file. And you also know that it can be annoying that:</p><ol><li>There’s really no way of organizing your artboards other than grouping them together, visually.</li><li>The limited canvas size means you only have so much room for artboards before you don’t have any more room to place them.</li><li>The 100 artboard limit is also pretty restrictive for larger projects.</li><li>Larger files tend to be sluggish and occasionally crash.</li></ol><p>Enter <strong>Pages</strong> in Sketch. Pages are essentially the equivalent of having multiple (and unlimited) canvases in Illustrator. Here’s why that’s awesome:</p><ol><li>Group artboards together just like you group layers.</li><li>Make as many as you want. Pages and artboards are unlimited and don’t slow down Sketch as your project grows.</li><li>Smart alignment (like Smart Guides in Illustrator) helps your maintain equal spacing and alignment between your artboards. So if you’re a little obsessive about that sort of thing, Sketch understands you.</li></ol><h4>How I use pages:</h4><p>I tend to use pages to separate my different design templates. For example, one page is usually dedicated to the homepage and each artboard on that page is a design variation or a different state, and includes the desktop, tablet, and mobile designs all in one place where I can see them all together and easily move design elements from one to another. I also keep a page for my style guide, where I keep examples of styled text, button styles, or other UI elements that I’ll use throughout (read on to hear about <strong>Layer &amp; Text Styles</strong>). I also keep a page reserved for <strong>responsive grid settings</strong> (see the next section) that I can duplicate for new pages so that I always start out with the same artboard sizes with the same grid settings.</p><p>With Illustrator, I used to try using separate files to organize my designs because keeping too many in 1 file made it slow, but that method had it’s own problems. Sketch’s performance and pages feature fixes all of this and does it well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TbZffytXwI1zH4gJ8bxwlg.png" /></figure><h3><strong>Responsive grid guides, built-in.</strong></h3><p>Sketch understands that it’s 2015 and <strong>responsive web design</strong> is a standard that heavily influences the way we design and build websites and web-based apps alike. That’s why it’s got built-in grid guidlines that intelligently calculate sizes for you so you can set custom grid sizes without having to do the math yourself or manually draw guidelines. Sketch calls it <strong>Layout</strong> and you can turn it on/off as needed, per artboard.</p><p><strong>Layout Settings</strong> allows you to set variables that grid dimensions, but I usually specify only 2 things and let it calculate the rest accordingly: <em>Total Width</em> and <em>Gutter Width</em>. You can also switch between the guides being filled versus outlined, depending on your preference. If you use the same settings often, you can set them as the default so that every new artboard you create inherits those same settings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*rOvMToPU27DoiojcJ-lpmA.png" /><figcaption>Layout Settings</figcaption></figure><p><strong>Tip:</strong> Apply grid settings to multiple artboards or all artboards within a page all at once by selecting them before bringing up the <strong>Layout Settings</strong> menu.</p><p>Sure, there are Photoshop and Illustrator templates you can download with grid guides already drawn, but a) you might want tighter gutters or a wider row width; b) they’re usually made 1 screen size (desktop) and don’t include smaller versions for tablet and mobile; c) you still have to copy/paste them onto every artboard you make that needs the grid guidelines overlaid on them, which is pretty much all of them; and what if you decide to change them during the project? If you want to calculate grid sizes for a custom grid or different screen widths, have fun doing the math…You’ll wind up using an online grid tool for that, but then you’re still stuck with problem c).</p><p>This is what my page for responsive artboard sizes typically looks like with the grid layout turned on:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i6TweOz8s68Ms_Rvk8_tUQ.png" /><figcaption>Artboards with Show Layout turned on.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kN1g9P1NYUn2DTP71M8dwQ.png" /></figure><h3>Speed things up with <strong>Layer</strong> and <strong>Text Styles.</strong></h3><p>You’re familiar with text styles. You know, defined styles for headlines, body copy or paragraph text, things like that. Illustrator and InDesign has this. Even word processors have this. It’s important to use consistent typography in our designs to ensure readability and cognition, as well as minimize production time. Sketch’s text styling helps you do this by allowing you build a style list for all your variations. For example, a basic list might look something like this:</p><ul><li>Navigation Link</li><li>H1</li><li>H2</li><li>H3</li><li>Body copy</li><li>Body copy link</li><li>Button text dark</li><li>Button text light</li></ul><p>Sketch also styles the list using the selected font, color, and size, showing you context for easy selection. But here’s where this really helps: Let’s say you’ve designed several screens with the navigation already in place when you realize the color, size, font, or line height just isn’t right. You can change each and every single instance of text that uses that text style, instantly. All you’ve gotta do is change one piece of text and they all change to match.</p><p>While this is available in Illustrator, it’s cumbersome and not too intuitive. Sketch’s version is very easy to access, straight-forward, and shows visual previews in your styles list, making it a time-saver and more joy to use.</p><p>No, I didn’t forget about <strong>Layer Styles</strong>. Those are just as awesome, if not more. Essentially, it’s the same, but a matter of setting fills, strokes, opacity, blending modes, shadows, etc. Let’s say you have a few different button styles you want to use throughout your design. Creating them as layer styles will allow you to make sure any button, wether they are a part of a symbol or not, is always styled the same as the others. I’ve also found this useful in wireframing when I decide that I want to create new placeholder objects that share the same visual style as ones I’ve used previously in my file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jEIU4TXD65yB-IuGov6czQ.png" /></figure><h3>Plug-in and App Integration Galore</h3><p>From interactive prototyping to documentation, there are some great integrations with 3rd party apps and services for Sketch that can be greatly helpful. There are also plenty of awesome plug-ins that speed up productivity or make presentations suck less. Here’s a list of <em>my top favorites</em>:</p><ol><li><a href="http://framerjs.com/">Framer JS</a> (desktop app)— This powerful prototyping tool gives you the control of using code (CoffeeScript) to fine-tune micro-interactions and test innovative interactive concepts without the need ever mark up your designs in HTML and CSS first. It’s high-fidelity protopying at it’s finest. Use it to prototype for smartphones, wearables, computers, or anything with a web browser. If you’re not familiar with writing CoffeeScript, Framer’s documentation, tutorials, and built-in text editor are all fantastic at getting you up-and-prototyping quickly. Using Framer was my first time with CoffeeScript, and while it took a little bit to wrap my head around the concepts, learning to write the code required was pretty painless.</li><li><a href="http://uxpin.com/">UXPin</a> (web app)— For code-free no-hassle prototyping, UXPin has a great intuitive web interface with support for syncing Sketch files into your online project. Adding transitions and realistic interactions is super simple. With familiar buttons and drop-down menus, any designer can produce great low or high fidelity prototypes in minutes.</li><li><a href="http://zeplin.io/">Zeplin</a> (desktop &amp; web app) — When you’re ready for developers to get involved, don’t waste any time red-lining your designs. Just export your artboards to Zeplin and let it handle the rest. It shows developers what colors and fonts you’re using across the entire project, as well as any distance between objects they want to know simply by hovering over them, much like you’d do in Sketch while holding down the Option/Alt key. Even image assets can be exported from Zeplin without the developer or designer having to export them from Sketch. In fact, the developer won’t even need Sketch at all. This is an ESSENTIAL tool that will save you HOURS and ensure developers have everything they need to get your designs built right the first time.</li><li><a href="http://sketchtoolbox.com/">Sketch Toolbox</a> — Browse plug-ins and install them instantly with this fantastic companion app. There’s no better way to find new useful plug-ins and manage which ones you’d like to install/uninstall. This is another essential tool for Sketch users.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p0UnqmvzxVlNCfXkxoDvEQ.png" /></figure><h3>Export Assets Like a Boss.</h3><p>One killer feature of Sketch is how simple and fast it is to export assets. Wether you need 1 icon or all of them exported, wether you want 1 version as a <strong>@1x PNG</strong> or several <strong>@1x</strong><em> </em><strong>@2x</strong> and <strong>@3x</strong>, plus a version as an <strong>SVG</strong>, it’s fast and easy. Click on any layer, then click the “Export +” button and set your preferences for size, prefix, and format. You can even drag and drop the thumbnail preview off the screen as a shortcut for saving an asset to your desktop or into a file upload field in your web browser (you’ll have to try that to see what I mean). And having support for exporting to multiple file formats (PNG, JPEG, TIFF, PDF, EPS, and SVG) <em>and</em> sizes (1x, 2x, 3x, 0.5x, custom x, or max height/width) or all at the same time is pretty slick! You can also export a set of assets all at once and Sketch will remember what settings you chose for each and every one them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/212/1*VitBQdbcPeYpcgPeSzN_cQ.png" /><figcaption>Export settings, visible when a layer is selected for export.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fURN9bXDomkuGwV450VGzw.png" /></figure><h3>Documentation? Oh, you can do that, too.</h3><p>With the help of a fantastic plug-in called <a href="https://github.com/marcosvidal/Sketch-Notebook"><strong>Sketch Notebook</strong></a>, you can add annotations to each of your artboards. It also lets you turn them on/off easily, and even re-style what your annotations even look like, giving you the opportunity to keep them on brand for presentations. I cannot express how much of a time-saver this is. I used to export my screens as images and import them into a separate presentation where I’d have to manually add lists of annotations, style them, and constantly update the images to keep synced up with the latest designs. It was such a time suck. But now I can annotate as I design and turn them off to keep them out of the way when I don’t want them while I’m designing. It’s another essential tool for me. But try it out for yourself to fully appreciate it. Really.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*bVDKr2d42G9ylGEA2o79JA.gif" /><figcaption>Adding annotations with Sketch Notebook</figcaption></figure><p><strong>Tip:</strong> Re-style your annotations to match your brand.</p><p>By default, the annotations side-bar is dark gray with white and light gray text and green markers (the dots). You may want to re-style these elements to match your brand by changing colors, fonts, or remove unnecessary details, or add your logo, for example.</p><p>To do this, add your first annotation. A new page is then created automatically that houses an artboard used as a template for all your annotations. Editing the <em>layout, adding, or removing elements </em>on this artboard will affect <em>new</em> annotation side-bars. You’ll have to delete any you’ve made so far and re-annotate them to get the new layout or set of elements. Editing the existing text/layer styles, however, will instantly change the colors/fonts on all your existing annotations. I also suggest turning the headline text into a symbol so that it can be changed at any time and updated across <em>all</em> your annotations instantly, just in case you do decide to change that text later on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0SGzQki3xaMmSlj1icIFrw.png" /></figure><h3>Context is King!</h3><p>We’re all used used to seeing our own reflection on the mirror. But take a photo of yourself and see your face as everyone else does, and you immediately notice how your left ear is actually higher than your right, or that one eye opens slightly more than the other. This is what it’s like seeing your design in context of where it actually ends up after starting at it for hours without a frame around it in your design tool, or the UI of an address bar and several tabs open. You notice things about your design you didn’t notice before. It just <strong>feels <em>different</em></strong>.</p><p>Wether you’re presenting to a client, your peers, or just want to see the design for yourself, you’ve GOT to have context if you want to see what your design will <strong><em>actually look like; </em></strong>what it will <strong><em>feel like</em></strong> in it’s final form. This subtle difference in how you <em>look</em> will change what you actually <em>see</em>, allowing you to address details you may have missed.</p><p>Now, Adobe has you covered if you’re trying to mirror your designs onto a mobile device, and Sketch does that, too, with their <strong>Mirror</strong> feature and companion mobile app. But for the context of a desktop web browser, there’s another great plug-that comes in handy. It’s called <a href="https://github.com/Freakland/sketch-browser-preview">Sketch Browser Preview</a>. What it does is take a snapshot of your current artboard @1x resolution and opens it into your web browser for an instant preview. I use this constantly throughout my design process and it helps a great deal. I even use it for facilitated presentations where there’s no need for an actual click-through demo or annotations. I can simply throw all the screens I need into the browser and toggle through each tab, screen by screen, as I present each one. It’s the fastest and easiest way to present desktop designs in context.</p><h3>Try it!</h3><p>Download the <a href="http://sketchapp.com/">Sketch</a> free trial and give it a run if you haven’t already. I’ve been using Sketch for about 6 months and it’s transformed my work-flow, increasing my speed, quality of work, and innovation. It’s become my go-to design tool that works for a range of steps in my design process. I’m sure you’ll find it useful in yours, too.</p><p>Please share your thoughts and comments! I’d love to hear how you’re using Sketch in your design process, as well as your thoughts on how it fits into your ideal workflow.</p><p>Happy Sketch-ing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9497b9d80998" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sketch-app-sources/why-sketch-is-the-ui-designer-s-best-friend-9497b9d80998">Why Sketch Is the UI Designer’s Best Friend.</a> was originally published in <a href="https://medium.com/sketch-app-sources">Design + Sketch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>