Why Designers Should Code
Upcoming SlideShare
Loading in...5

Why Designers Should Code






Total Views
Views on SlideShare
Embed Views



4 Embeds 177

http://www.linkedin.com 128
https://www.linkedin.com 45
http://www.slideshare.net 3 1



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Sorry, but you own all touch points/ where user experience doesn’t end at layouts/ navigation designIn fact, it opens up whole new world of creative possibilities. Yes, but pick it up you won’t regret itOnce you get the hang of it – it’s whole lot of fun
  • Understanding your medium thoroughly

Why Designers Should Code Why Designers Should Code Presentation Transcript

  • Why designers should code?
    - Sunit Singh
    Sunit Singh
  • “Design is not just what it looks like and feels like. Design is how it works.”
    —Steve Jobs
    Sunit Singh
  • Sunit Singh
  • Sunit Singh
  • Sunit Singh
  • Ring’s a bell?
    WTF? This is no where close to the original design!
    The original mocks were much better, the developers screwed up!
    I need a better design spec tool?
    The page looks quite empty after the real data has come in...!
    Most of the key elements are going below the fold…
    How am I meant to implement that?
    Not possible!... Do we really need this?... Will affect performance...
    Sunit Singh
  • Responsive, Light Weight Experiences
    Google Maps
    Word Press
    Sunit Singh
  • Schools of Thoughts
    Designers should focus on design?
    Coding restricts creativity?
    Coding, a steep learning curve?
    Sunit Singh
  • “…coming up with an idea is the least important part of creating something great. It has to be the right idea and have good taste, but the execution and delivery are what's key
    —Sergey Brin
    Sunit Singh
  • Why?
    Know the rules if you want to bend them!
    Understand the possibilities of your medium, leverage what it already offers
    Design for efficiency, performance, best design decision given constraints, lean design
    Get real - sooner than later, see how real data looks and works
    Sunit Singh
  • Why?
    Be ready for change, quickly iterate, reduce back and forth
    Baby step towards embracing technology
    More credible/ better bargaining position
    Inbuilt Accessibility / SEO
    Stay ahead of the curve
    Sunit Singh
  • Beware!
    Self-censoring - avoid compromising on the best possible user experience
    Never lose sight of the bigger picture
    Sunit Singh
  • Good Reads
    6 Reasons Why Designers Should Code
    Good Reasons Why Designers Should Code, Mike Kus
    Design at Facebook - by Luke Wroblewski
    Designers are not Programmers - by Lukas Mathis
    The Case For Code - Alex Dunae
    Should Web Designers Know how to Code? - Martin Ringlein
    Web designers should do their own HTML/CSS – Davi, 37 Signals
    Why Designers Should Learn How to Code - John Urban
    Designers who are technical: The More You Know, The Better Your Work
    The Case Against Code II - by Stuart Thursby
    Sunit Singh
  • Getting Started
    Designing with Web Standards
    by Jeffery Zeldman
    CSS - The Definite Guide
    by Eric Meyer
    Sunit Singh
  • Brushing Up
    Web Standards Solutions
    by Dan Cederholm
    Sunit Singh
  • Questions?
    Sunit Singh