<?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 Martin Sitar on Medium]]></title>
        <description><![CDATA[Stories by Martin Sitar on Medium]]></description>
        <link>https://medium.com/@martinsitar1?source=rss-1fff11488cea------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MkMVChrZTxIJK2KASmXLMQ.png</url>
            <title>Stories by Martin Sitar on Medium</title>
            <link>https://medium.com/@martinsitar1?source=rss-1fff11488cea------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:38:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@martinsitar1/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[Don’t skip over the “rough work”]]></title>
            <link>https://craft.faire.com/dont-skip-over-the-rough-work-c3327c884bdf?source=rss-1fff11488cea------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3327c884bdf</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[exploration]]></category>
            <category><![CDATA[ideation]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Martin Sitar]]></dc:creator>
            <pubDate>Wed, 31 May 2023 16:07:10 GMT</pubDate>
            <atom:updated>2023-05-31T16:07:10.978Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why exploration should always be a part of your design process, and how to make time for it</h4><figure><img alt="A graphic illustration with various shapes (circles, triangles, hexagons, and 8-pointed stars) in different colors connected by lines, suggesting the ideation process." src="https://cdn-images-1.medium.com/max/1024/1*d0MNkXjvR-lygJOG7VFBsQ.png" /></figure><p>Five years ago I wrote <a href="https://ux.shopify.com/how-to-level-up-your-portfolio-5795173a8f48">an article</a> about why it’s important to include your explorations, wireframes, sketches, and other “rough work” in case studies and portfolio presentations. I wrote it at a time when I was conducting a lot of design interviews and noticed that designers often glossed over or completely skipped showing the rougher, iterative parts of their process. This left out crucial details about how they approached a problem, the tradeoffs they had to make, and how they ultimately arrived at a final solution.</p><p>The article ended up becoming surprisingly popular, and I continue to hear from designers about it today. Since then, I’ve had the opportunity to reflect more deeply on the value of exploration as part of the design process and the power it has to unlock your creativity and design better products.</p><p>Here are my updated thoughts on how exploration can help grow your skills and why you should make it a regular part of your product design process.</p><h3><strong>Working with constraints</strong></h3><p>As a product designer, I often deal with a stream of inputs informing any piece of creative work. Business requirements, research and data insights, stakeholder input, timelines all shape and impact a project in different ways. While these are critical in helping me gain clarity and unblocking a project, I’ve observed two ways they can challenge my creativity, especially early on in the design process.</p><p>The first is just trying to factor in too many inputs, which can lead to feeling stuck in a project, unsure of the best next steps, and feeling blocked creatively. This has the effect of stifling ideation because you feel like you have to address too many things at once, before you’ve had a chance to fully explore the problem space.</p><p>The second is narrowing in on a specific solution too early by jumping far ahead in the creative process and making too many unproven assumptions. This is especially risky because it can feel rewarding and comes with a sense of progress. In an effort to move forward, I’ve found myself latching onto a single idea and making smaller iterations that fit within the perceived constraints. I’ve found this can often lead to missed opportunities or worse — prevent me from uncovering major blockers until a very late stage in the project.</p><h3><strong>The power of exploration in design</strong></h3><p>One of the best ways I’ve found to combat these challenges is by prioritizing exploration early in my creative process. Exploration means ideating and chasing different ideas to see where they lead, what they may uncover, and how they may shape the design of a particular solution. By giving myself time to explore, I’m able to dive into an idea without constraints. I can let go of the noise from all of those inputs for a moment and start exploring ideas with less pressure.</p><p>Even when I face a complete creative block, I find that just by starting to do some light exploration, my ideas will start to flow, and I quickly reach a state where I feel more creative. Exploring many different ideas quickly is surprisingly powerful by helping unblock me and serve as a base for refined exploration.</p><p>Now, you might be asking, how do I actually create the time and space for exploration? I have deadlines, stakeholder inputs, product requirements, and other limitations! I’ll get to that, but first: a story.</p><figure><img alt="A graphic illustration showing four different vases in block colors with shadows below them." src="https://cdn-images-1.medium.com/max/1024/1*PmTfY69Kdtmi8E-ovDl5-Q.png" /></figure><h3><strong>Why aiming for quantity is more effective than aiming for quality</strong></h3><p>Whenever I get stuck on a project, I find it helpful to return to a short allegory from a wonderful book, <a href="https://www.amazon.com/Art-Fear-Observations-Rewards-Artmaking/dp/0961454733">Art &amp; Fear: Observations On the Perils (and Rewards) of Artmaking</a> by David Bayles and Ted Orland, which illustrates the importance of doing lots of exploratory work:</p><blockquote>The ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality.</blockquote><blockquote>His procedure was simple: on the final day of class he would bring in his bathroom scales and weigh the work of the “quantity” group: fifty pounds of pots rated an “A”, forty pounds a “B”, and so on. Those being graded on “quality”, however, needed to produce only one pot — albeit a perfect one — to get an “A”.</blockquote><blockquote>Well, came grading time and a curious fact emerged: the works of highest quality were all produced by the group being graded for quantity. It seems that while the “quantity” group was busily churning out piles of work — and learning from their mistakes — the “quality” group had sat theorizing about perfection, and in the end had little more to show for their efforts than grandiose theories and a pile of dead clay.</blockquote><p>We learn by doing, and the reason I love this story is because it illustrates how creating and producing work is the path to quality. On a macro level, producing many pieces of work helps you become an expert in your craft. Similarly, on a micro level, taking the time for creative exploration on a project improves the quality of that singular piece of work and leads to better solutions you can feel confident about.</p><h3><strong>Finding your groove</strong></h3><p>Part of our product development process at Faire is a dedicated “explore phase.” Having time specifically carved out in the project timeline to go broad enables us to evaluate as many possible solutions to a problem, and ultimately arrive at the one that serves our brand and retailers the best. However, it’s important to remember that exploration can be big or small and can fit into whatever process you participate in. It can be as simple as a quick sketching session or as big as extended time dedicated to exploring more complex flows and prototypes.</p><p>Personally, my not-so-secret and favourite way to generate lots of ideas very quickly is sketching. It’s such a lo-fi way to let your ideas flow where there really are no constraints. The nature of the medium allows me to focus on high-level concepts and ideas and iterate very quickly, something I am personally not able to do as efficiently on the computer.</p><figure><img alt="A photo of two sketchbooks pictured from above. A pen is on top of one of them. On their pages, there are sketches of various wireframe ideas." src="https://cdn-images-1.medium.com/max/1024/1*w_xN0W1FBoOjzgaG8jWhVQ.png" /><figcaption>Sketching helps me generate ideas quickly.</figcaption></figure><p>A common misconception with sketching, and I see this in my design classes too, is that people often think they need to be artists to sketch their ideas. But it‘s much simpler than that: if you can draw circles and boxes, you can sketch out your ideas too. Here are a few things I do that help me unlock my creativity:</p><ul><li>I put on background music to shift my mood</li><li>I focus away from my computer and towards my notebook or a sheet of paper</li><li>I often use a pen because it helps me ignore mistakes; with a pencil I tend to erase and “fix” things which interrupts the process</li><li>I focus on the main problem I’m trying to solve, and let go of constraints</li><li>I spend about 30 minutes generating and iterating on ideas, no matter how silly they may seem</li><li>I review my work and mark promising ideas with a star as something to explore further</li><li>Last tip, I always date my sketches — just a personal bit of housekeeping, but it helps you see the evolution of a project when you look back on it</li></ul><p>After generating and evaluating multiple ideas, I move to higher fidelity explorations with the ones I feel best align with the project.</p><h3><strong>Making exploration a part of your process</strong></h3><p>If you’re in the early stages of a project, remember to leave room for exploration, it will help you get to a better outcome. If you’re already in the midst of a project, remember that exploration can be as quick and scrappy as it needs to be. If you’re hitting a creative block, just grab a piece of paper and start sketching something, let go of constraints, and focus on quantity over quality. You’ll see ideas start to flow.</p><p><em>Want to stay up-to-date on the latest dispatches from the Faire Design Team? Subscribe to get notifications delivered directly to your inbox: </em><a href="https://medium.com/@FaireDesign"><em>https://medium.com/@FaireDesign</em></a></p><p><em>Interested in learning more about Faire? Explore </em><a href="https://www.faire.com/careers?utm_source=blog&amp;utm_medium=blog&amp;utm_campaign=craft&amp;utm_content=article_04_14-23"><em>open roles</em></a><em> on the team.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3327c884bdf" width="1" height="1" alt=""><hr><p><a href="https://craft.faire.com/dont-skip-over-the-rough-work-c3327c884bdf">Don’t skip over the “rough work”</a> was originally published in <a href="https://craft.faire.com/">The Craft</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to build your creative confidence and deal with tough feedback]]></title>
            <link>https://medium.com/@martinsitar1/how-to-build-creative-confidence-and-deal-tough-with-feedback-f3cefb4bae8d?source=rss-1fff11488cea------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3cefb4bae8d</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[creative-process]]></category>
            <dc:creator><![CDATA[Martin Sitar]]></dc:creator>
            <pubDate>Tue, 18 Sep 2018 14:01:06 GMT</pubDate>
            <atom:updated>2018-09-18T16:24:31.124Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D1a3wrXwc0gWi65Na_fdyg.jpeg" /></figure><p>Designing great products is hard. There are lots of moving parts, big questions to answer and plenty of ambiguity. If you’ve worked on a project in the past, this scenario might be familiar to you:</p><blockquote>You’ve put a lot of effort into coming up with a design for a tough problem. You think you have a great solution, but then get a ton of peer feedback questioning many of the decisions you’ve made.</blockquote><p>Collaboration is a big part of UX design. Using exercises like critiques and feedback sessions can help us design and build the best products for our users. Sometimes, we can fall into a rut where we start to design purely based on peer feedback and lose sight of our goal. This can get frustrating and feel like you’re spinning in circles. From time to time, I find myself slipping into this cycle and notice I start to lose some confidence in my work. Chatting with other designers, I realized this is a feeling many of us experience. The way we perceive feedback and how we choose to act on it impacts our feelings about our work and, ultimately, the final outcome of a project.</p><p>The good news is there are steps you can take that help you perceive feedback positively, use it to your advantage, and build your confidence. Here are some things I do that help me when I seek feedback from my peers.</p><h4>Set clear expectations</h4><p>When you share your work with others, people tend to give you feedback on things that stand out to them. This can be great but you often get a lot to sift through that may not be particularity useful in helping you move forward. A lot of unfocused feedback can also feel overwhelming.</p><p>It helps to be clear on the parts of your work you‘d like feedback on. Being specific helps prepare you for the kind of feedback you‘ll receive, and will help focus the conversation so that the feedback is relevant and actionable. It also makes the feedback easier to compare since everyone is evaluating the same thing. You can be as specific as you need to, depending on the stage of your work. Expect that you will get different types of feedback on sketches, wireframes, prototypes, or the final interface.</p><p>You can even choose to focus it further on things like interactions, the UI of a specific component, iconography, content, the flow, etc. Sometimes it can also help to mention things you’re not looking for feedback on, maybe it’s the copy or the color palette, etc. This will help you set boundaries, and your goal is to get feedback that will help you move forward. Being specific helps your peers focus their efforts, and allows them to be as valuable as they can.</p><h4>Build a deeper understanding</h4><p>People give feedback in different ways. Often their initial statement may not truly represent the underlying issue they‘re trying to bring to your attention. People also tend to give feedback in the form of solutions, for example: make that line thinner, move the button to the right, the button is too small. Make an effort to understand the reasoning behind their feedback. They may say the button should be on the right, when the actual concern is that the current placement of the button makes it difficult for users to complete a task.</p><p>Try to dig deeper by asking why. If it’s still not clear keep going. Digging deep helps you understand their perspective and lets you ask follow-up questions about their underlying concern. This helps you shift the conversation from feeling like it’s about you and puts the focus on the work and the task. You might also uncover their feedback is simply based on personal taste, which is great, but don’t let it undermine your design sense and intuition. Understanding the<em> why</em> will help you gauge how applicable a piece of feedback is to your problem, and how you might act on it to improve your solution.</p><h4>Evaluate against your goal</h4><p>A big part of design is your intuition, which you build with time and practice. Remember that when you get feedback during a critique, it’s not a reflection on you or your skills. Everyone on your team is trying to help you design the best solution to solve your user’s problem. People will have different opinions and different points of view, and part of your job is to evaluate those against your current solution, and the problem you’re solving. Think about if or how this improves your end user’s experience. If through that process you uncover a potentially better solution, then it’s definitely worth exploring further.</p><p>The ability to look at a variety of solutions, evaluate the trade offs, and make a decision is a critical skill to have. It will help you design better products, strengthen your rationale and build your confidence. This gets better the more you practice. Often when you don’t have a strong opinion, you’re susceptible to design purely based on other people’s opinions. You’ll quickly find yourself frustrated and redoing work.</p><p>If you’re ever in doubt over the direction of your design, and feedback sessions aren’t helping, test your design with real users. This should always be a part of your process. In the end, users are the ones who decide how well your solution solves their problem.</p><p>Ultimately, you build your design confidence through constant practice, feedback, and learning. I encourage you to have strong opinions, but hold them loosely and be open to new ideas. Feedback is a gift.</p><p><em>Interested in joining our team? Well we’re currently looking for some awesome folks to join our </em><a href="https://www.shopify.ca/careers/search?specialties%5B%5D=6"><em>UX teams</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3cefb4bae8d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to level-up your portfolio.]]></title>
            <link>https://medium.com/@martinsitar1/how-to-level-up-your-portfolio-5795173a8f48?source=rss-1fff11488cea------2</link>
            <guid isPermaLink="false">https://medium.com/p/5795173a8f48</guid>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Martin Sitar]]></dc:creator>
            <pubDate>Tue, 29 May 2018 18:19:55 GMT</pubDate>
            <atom:updated>2019-06-19T17:37:34.570Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OCUYaavelBT19SNYvlgw6A.png" /></figure><h4>The value of showing your rough work.</h4><p>As a Senior Product Designer at Shopify, I consider myself lucky to meet with aspiring designers, students, and others interested in design and our industry. From these conversations, I find we run into similar challenges, sometimes at different points in our careers. So I’ll be writing a series of short articles aimed at answering some commonly asked questions. This is series one.</p><p>What should you include in your portfolio? You most likely have a series of steps you follow when designing a solution to a problem. You might tweak these from time to time, change, adapt, and hopefully improve them, but this series of steps is what makes up your process. Everyone has a process, organizations have process, and even when people say they don’t have a process they almost always do. Process isn’t a bad thing, as long as you understand how each step provides value, and you’re not doing things just for the sake of doing them. Process should never get in your way. Early on in your career your process might be hard to spot, hard to nail down, but as you gain experience and work through more projects you’ll begin to realize which steps are valuable, where they apply, and what might be missing.</p><blockquote>A huge part of your process is rough work. It’s the path you took, forks you navigated, and the trade-offs you made to arrive at your final solution.</blockquote><p>At the highest level, your process should consist of at least 3 main phases: <strong>d<em>iscovery</em></strong> (conducting research and understanding the problem), <strong>e<em>xploration</em></strong> (iterating on possible solutions), and <strong><em>design</em></strong> or build (creating the final solution). One of the greatest ways you can strengthen your portfolio, and communicate how you work is to show and explain how you went from the initial problem to the final solution<strong> </strong>through these phases. Telling the story of a project by showcasing your process helps the reviewer understand your rationale and the trade-offs you had to make.</p><blockquote>Tell the story of your project in phases. Discovery. Exploration. Design.</blockquote><p>It can be incredibly tempting to start solutioning right from the beginning; resist this urge. The discovery phase is where you become familiar with the problem. It’s where you dig deep to find out everything you can about the problem space; why it exists, how it exists, who it affects, how it affects them, etc.</p><p>A good starting point for a portfolio piece is to clearly communicate the problem you’re attempting to solve. You want to avoid any confusion around the actual problem, so be clear and concise. The discovery phase is also the time to expand your understanding by conducting research, talking to people (target users), analyzing data, performing competitor audits, etc. It’s a great idea to highlight some key points from your research (user personas also work well). This helps reviewers gain additional context and lay the foundation for the story of your project. Showing work from the discovery phase communicates your ability to think thoughtfully and critically before jumping to a solution. It also lays the groundwork for how you formed your opinions moving forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VktiEAOEnhY_YF2Ti2Bu0w.png" /></figure><p>Once you feel like you’re an expert on the problem, you’re ready to begin the solutioning and iteration phase. Mind-map exercises, user flow diagrams, sketches, wireframes, prototypes, and feedback, are tools to help you explore and iterate. It’s easy to include too many artifacts from this phase of your project, resulting in a confusing web of visuals; where it’s difficult to see how the work progressed.</p><p>Your goal is to show the progression of your thinking. Take one or two early artifacts that helped you distill all of the learning from the research phase, a user flow, one or two sketches, and a series of wireframes. Focus on how you progressed from the possible solutions toward something more concrete. Explain the trade-offs and why one solution is better than another. Every project has trade-offs, every decision has consequences; this is one of the biggest challenges designers face. Showing how you evaluate potential solutions, and make decisions is one of the most valuable things you bring to a portfolio review.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rax7RhBgo8fZs2LMattajg.png" /></figure><p>The final design is often what everyone tends to fixate on. This is often the work we see on sites like Behance and Dribbble, and to be honest, it’s usually what catches everyone’s attention. However, you’re applying for a job, so including only the finished piece is simply not giving yourself enough credit. Telling the story from the beginning allows you to showcase your thinking, talent, and hard work that you’ve put into your work.</p><p>The finished piece is like a capstone to the entire project; if you’ve done a good job, the solution seems obvious. You want the viewer to think, “Well, of course it’s like that. It just makes sense.” At the very least, they should have a good understanding of why you designed it a certain way, and how you arrived at the solution.</p><p>Exposing your thinking can be scary, but it usually sparks a healthy conversation. Since you’ve shown the rough work, you can be confident in explaining the rationale behind your decisions. Be proud of the stupid ideas, messy sketches, and <em>x</em> number of iterations. Going through that process, and sharing it with others is how we all get better.</p><p>Good luck!</p><p>Looking to showcase your portfolio and work in an awesome company? Well <a href="https://www.shopify.com/careers/search?specialties%5B%5D=6/&amp;utm_source=uxblog&amp;utm_medium=post&amp;utm_term=a8f48">we’re currently hiring</a> — so check it out!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5795173a8f48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sketch 3 vs. Illustrator — Why I finally switched]]></title>
            <link>https://medium.com/@martinsitar1/sketch-3-vs-illustrator-why-i-finally-switched-231737394997?source=rss-1fff11488cea------2</link>
            <guid isPermaLink="false">https://medium.com/p/231737394997</guid>
            <dc:creator><![CDATA[Martin Sitar]]></dc:creator>
            <pubDate>Fri, 28 Nov 2014 21:29:03 GMT</pubDate>
            <atom:updated>2014-11-28T21:32:33.254Z</atom:updated>
            <content:encoded><![CDATA[<h3>Sketch 3 vs. Illustrator — Why I finally switched</h3><h3>Sketch 3 vs. Illustrator — Why I finally switched</h3><p>November 24, 2014 by <a href="http://martinsitar.com/author/vivixmedia/">Martin Sitar</a></p><p>Thinking back to a few years ago I remember making the switch from using Photoshop for my web and UI work to Illustrator. Almost immediately, I saw a huge improvement in my workflow. Vector files were so much easier to handle, they were generally smaller, editing them was very quick and sharing with other designers easy. Although Illustrator wasn’t really created specifically for web and user interface design, it did the job quite well and still does.</p><blockquote>I can’t help but feel like the time has come again when a better tool is available to help refine and streamline the workflow for UX/UI Designers.</blockquote><p>Originally I heard about Sketch from a colleague and I decided to give the beta a try. I was so engrained in my current workflow that I gave up after a few days and just continued working in Illustrator. I always felt like Illustrator was a little bloated with so many features and tools that as a UX/UI designer I just didn’t really need. As I kept on seeing more and more resources for Sketch on the web I began thinking about giving Sketch 3 another try, especially since there was so much great work popping up on Dribbble. Originally my thinking was clouded with the idea that maybe it’s rise in popularity is related to the low price tag, but the real turning point for me was when I started working on mobile apps using Xcode 6. Regularly exporting assets of varying sizes from Illustrator was the thing I looked forward to the least, and tried to always postpone it as long as possible. In Sketch 3 barely have to think about it, and even the naming convention is taken care of!</p><p>Sketch 3’s UI is so clean and simple, it has all of what you do need and nothing of what you don’t. There doesn’t seem to be that bloat I was experiencing with Illustrator. As a result of this the learning curve is almost non-existent, and I see a huge performance boost in the way I work. Also, switching between Xcode 6 and Sketch 3 feels so fluid and natural it almost seems like they are an extension of each other. Oh.. and the exporting thing, a breeze! Here are some of the main reasons I finally decided to make the switch.</p><h4>Exporting</h4><p>One of my favourite features of Sketch 3 is the ability to export an asset in multiple sizes at the same time. This is a huge win over having to do it manually in Illustrator. It’s just one of those clever features that saves you a lot of time, and was actually the main reason I wanted to start using Sketch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/212/0*bQomGhfdROb0KzZJ.png" /></figure><h4>Templates</h4><p>Sketch 3 has awesome pre-built templates and components for quickly getting started with designing for iOS for example. You really get the feeling that this is exactly what Sketch was made for and it just feels natural to have access to such resources. Additionally there is a growing community of designers constantly creating new templates, UI kits and mockups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*845WDMPsiPAx0FE8.png" /></figure><h4>UI &amp; Layout</h4><p>The interface in Sketch is designed to help you get your work done without distraction, it looks so clean! I will admit, originally I was a apprehensive about the lack of the “tools palette” that I was so used to in Illustrator. In reality, there are only a handful of tools you really use from that palette and Sketch makes these readily available. I love having the inspector on the right, and how similar the layout is to Xcode. It is one of those things that makes switching between the two feel cohesive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KlievdW2eO_4pYql.png" /></figure><h4>Fonts</h4><p>The way Sketch handles fonts is absolutely fantastic. One of my largest complaints about originally switching from Photoshop to Illustrator was that the fonts just didn’t look at nice and smooth. Well, Sketch has does an amazing job of rendering the fonts beautifully, it just makes the whole interface look so much better!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/0*9M0TRvbQYmzbcI8S.png" /></figure><p>There are many other awesome features in Sketch such as how easy it is to work with symbols and how they update across art-boards. I encourage any UX/UI designer to give Sketch 3 a shot and see how it can help improve your workflow. It’s a great piece of software and I am sure it will continue to get even better.</p><p><em>Originally published at </em><a href="http://martinsitar.com/sketch-vs-illustrator/"><em>martinsitar.com</em></a><em> on November 24, 2014.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=231737394997" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>