Designing in the browser is becoming more and more popular with the rise of “designers who code”. But just because we’ve picked up some new skills does it mean we should ditch our paper, sharpies, desktop publishing software and wireframing tools and jump straight into coding prototypes? Browser vs. Photoshop is a Hot Topic If you’re working in the digital space, with designers and developers, you will have seen the rising trend in designers being expected to have (some) coding skills. Many people are all for it, whilst some believe that designers shouldn’t touch code. However, those designers that do code are getting more confident and some are even arguing that designing in Photoshop is no longer relevant in certain scenarios. I’m of the opinion that creativity is tool independent, but I can see the benefits and drawbacks of both approaches in isolation (I’ve listed them below, so you can get my perspective on the discussion). In this article I use the term “Photoshop” and “UXPin” loosely. I am really referring to any tool of this sort, whether you use Sketch, Balsamic or something else! The same argument applies. Photoshop and UXPin just happen to be my tools of preference. Going Straight into the Browser Copyright © 2013 Olle Svensson Attribution-commercial-Share Alike 2.0 license A common situation in which someone in an organization might design in the browser is if they are skilled in visual design, but are also comfortable coding. For example, the purpose might be to communicate to a developer building a CMS what the design will look like.
↧