Skip to main content

Evolution of UI/UX Designer Tools

Over the last 15 years I have used many different tools to help me create great design experiences. One of the largest changes I have seen is the shift to using one tool that basically does it all. I have sort of come full circle when it comes to software / hardware within my design career.

I first started off in school using a Mac to create digital art using Adobe Photoshop and Freehand from 1998-2001. My first job out of college I was producing illustrations for a publishing company and I used Photoshop, freehand, and illustrator exclusively. Then came 2003 and what I call my era of SharePoint where I ditched the Mac, grabbed a Windows Laptop and started doing all my wireframes in Visio. It was not until 10 years later (2013) that I came back full circle. I jumped back on the Mac Powerbook bandwagon and started using Axure. Axure for me has been amazing but I am starting to see another shift where Sketch has become that next best thing.

Sketch by itself is pretty limiting, however what makes it so powerful is that it has so many extensions and integrations with other tools such as Invision and Zeplin. Invision allows me to organize my Sketch concepts and provide a lightweight prototype to review with clients using hotspots. I don’t think Invision will ever replace the advanced prototyping features that Axure provides however it provides enough to get the point across. I am a bit on the fence since I see a huge value for visual designers to create amazing designs in Sketch and exporting them into Zeplin to create very detailed design specs that are super helpful to the developers who will be implementing the designs. However it is kinda weird to think of a product called "Sketch" and producing really high fidelity designs from it which are on the opposite side of sketches…

One of the biggest things that keeps me from fully converting over to Sketch from Axure is the inability to easy create flow diagrams, sitemaps, connected boxes, tables and lack of built in prototyping directly in Sketch.

My design lifecycle right now looks like this:
1. Sketches (Paper)
2. Conceptual Designs (Axure/Sketch)
3. Wireframes (Axure/Sketch)
4. Interactive Prototypes (Axure/Invision)
5. Functional Annotations (Axure/Sketch)
6. Visual Design Mockups (Sketch)
7. Developer Style Guide (Zeplin)

As you can tell from the above I am using both Sketch and Axure for some of the same tasks. It really depends on the type of project and team on what tool I will use to create my concepts and wireframes. If I know I will need to do heavy prototyping I will go with Axure. Or if I know it will be a large team effort and all of the other designers will be using Sketch I will use that instead.

There are some other players in the game like Invision Studio, Adobe Experience Design, Balsamiq, and JustInMind. It really comes down to a few core factors that makes a tool productive and worth using.
1. The core features on how you will use them
2. How long will it take you to learn and start being productive
3. Collaborative features to share and interact with others
4. Cost of initial use and publishing plans

Things are changing fast and furious and the major players are all working to make their product the best it can be for all user types. I still don’t think there will ever be a single one size fits all tool but if there is I will be happy to jump on that bandwagon.

In the coming months, I hope to post some hands on tutorials for both Axure, Sketch and Invision Studio. Post a comment on what tools work the best for you.

Popular posts from this blog

SharePoint 2010 Base CSS Classes

This will be the first of many SharePoint 2010 posts. I will be focusing on a few of the main CSS classes used for SharePoint 2010 Public Beta. As the product becomes more final there might be some changes to the class names but I will be sure to create a new post if that happens. This will be quite a lengthy but it should be helpful. The default CSS given below are just highlights of the full CSS attributes for that class.I will be using a basic team site as my base for the screenshots. Here is a basic structure of the main areas that I will cover.Ribbon RowTable Row Left Site Actions Navigate Up Edit Tab List Browse Page Table Row Right Give Feedback Welcome Menu WorkspaceBody Container Title Row Title Title Logo Title Text / BreadcrumbPage DescriptionSocial Data SeparatorI like It Tags/Notes Top Header 2/Top Links li Static-Selected li Static SearchHelpStatus Bar Container Main A…

How To: Hide Left Side Navigation on Home Page

I was recently asked: "How can I hide the side nav bar on the main homepage layout ?? I want to be able to use the side NAV with in the team site etc etc, but I don't want it on the front page.. " There are a couple of ways to do this in SharePoint 2010. If you are using a non-publishing site you can add a Content Editor Web Part to the page and add the following to the HTML Source.
body #s4-leftpanel
display: none;
margin-left: 0px;
Basically the CSS above hides the left navigation Div, and then sets the content area to not have a left margin. Once you are done, simply modify the web part and hide it on the page. If you are using a publishing site for your homepage simply add the same styles specified above to a custom page layout. That way if you have a need for other pages that do not need the left side navigation you can re-use the page layout.

SharePoint 2010 Content Query for Blog Posts

I hope this post will help many of you feel comfortable with using the Content Query Web Part.In this post I will walk you through the process of creating a content query web part and configuring it to show custom field types. I will also give details on how to use XSLT to stylize and format the data being pulled. I will be using the following scenario as an example. Say that you had a site collection with a top level publishing site. This publishing site would display a the most recent blog posts from all blog sites within its own site collection. To solve this problem we will use a Content Query Web Part and a customized ItemStyle.xsl using XSLT.Please note that the “SharePoint Server Publishing Infrastructure” needs to be enabled at the site collection to display the content query web part.Step 1: Add a Content Query Web Part to PageNavigate to the site that you want the blog posts to show up and click on edit page. Under Editing Tools in the Ribbon, Click on insert > Web PartUn…