76
Designing (Deciding) in the Browser Sang-Min Yoon August 16th, 2014

Designing (Deciding) in the Browser

Embed Size (px)

DESCRIPTION

Slides from my talk at 2014 WordCamp Maine: http://2014.maine.wordcamp.org/session/designing-deciding-in-the-browser/

Citation preview

Page 1: Designing (Deciding) in the Browser

Designing (Deciding) in the Browser

Sang-Min Yoon August 16th, 2014

!

Page 2: Designing (Deciding) in the Browser

Let’s change the phrase “designing in the browser” to “deciding in the browser.”

-Dan Mall

Page 3: Designing (Deciding) in the Browser

When I mention “PSDs”, I’m referring to fully fleshed out comps

Page 4: Designing (Deciding) in the Browser
Page 5: Designing (Deciding) in the Browser

Sang-Min Yoon

Web Designer & Front-End Developer at Wentworth Institute of Technology

(Boston, MA)

Page 6: Designing (Deciding) in the Browser

I have designed and/or developed websites for

Page 7: Designing (Deciding) in the Browser

I learned web design & development with WordPress

Page 8: Designing (Deciding) in the Browser

About 4 years ago…

Page 9: Designing (Deciding) in the Browser

Typical Workflow• Set clear Goals and Objectives

• Content Inventory/Strategy

• Wireframe

• PSDs (Design)

• Front-end Development

• Back-end Development

• Testing

Page 10: Designing (Deciding) in the Browser

Typical Workflow• Set clear Goals and Objectives

• Content Inventory/Strategy

• Wireframe

• PSDs (Design)

• Front-end Development

• Back-end Development

• Testing

Most of the design decisions were made

Page 11: Designing (Deciding) in the Browser

Design• Create the PSD

• Get feedbacks

• Make millions and millions of edits

• Get sign off

• Start building the website only when clients/stakeholders are satisfied with the PSDs.

Page 12: Designing (Deciding) in the Browser

Typical Workflow• Set clear Goals and Objectives

• Content Inventory/Strategy

• Wireframe

• Design (PSDs)

• Front-end Development

• Back-end Development

• Testing

Most of the design decisions were made

Page 13: Designing (Deciding) in the Browser

Does this make sense?

Page 14: Designing (Deciding) in the Browser

We aint talkin ‘bout how the website looks on a browser

We talkin ‘bout how the website looks on a PSD.

Page 15: Designing (Deciding) in the Browser

How silly is that. We talking about PSDs.

!

-Allen Iverson

Page 16: Designing (Deciding) in the Browser
Page 17: Designing (Deciding) in the Browser
Page 18: Designing (Deciding) in the Browser
Page 19: Designing (Deciding) in the Browser
Page 20: Designing (Deciding) in the Browser
Page 21: Designing (Deciding) in the Browser
Page 22: Designing (Deciding) in the Browser

These are printouts of websites and not websites.

Page 23: Designing (Deciding) in the Browser

Even more issues now

Page 24: Designing (Deciding) in the Browser

Pictures of Phone Usage

Photo Credit: www.flickr.com/photos/lukew

Page 25: Designing (Deciding) in the Browser

Create PSDs for every single one of these devices?

Page 26: Designing (Deciding) in the Browser

“We only need designs for desktop computer, iPhone and iPad.”

Page 27: Designing (Deciding) in the Browser

“Most of our users use a desktop computer, iPhone and iPad.”

Page 28: Designing (Deciding) in the Browser

“we’ll see a larger screen, with a 4.7-inch model launching first and a 5.5-inch model also being

unveiled at the same time”

Page 29: Designing (Deciding) in the Browser
Page 30: Designing (Deciding) in the Browser

Touch Experience

Page 31: Designing (Deciding) in the Browser

Touch Experience

Page 32: Designing (Deciding) in the Browser

Interactions (hover, animations and transitions)

Page 33: Designing (Deciding) in the Browser

Show Animations

Page 34: Designing (Deciding) in the Browser

Show Animations

Page 35: Designing (Deciding) in the Browser

Can not make these design decisions on a PSD

Page 36: Designing (Deciding) in the Browser

Past Workflow• Set clear Goals and Objectives

• Content Inventory/Strategy

• Wireframe

• PSDs (Design)

• Front-end Development

• Back-end Development

• Testing

Most of the design decisions were made

Page 37: Designing (Deciding) in the Browser

Present Workflow• Set clear Goals and Objectives

• Content Inventory/Strategy

• Wireframe

• Design (PSDs)

• Front-end Development

• Back-end Development

• Testing

Make MOST of the design decisions

Make SOME of the design decisions

Page 38: Designing (Deciding) in the Browser

Designing in the Browser

Page 39: Designing (Deciding) in the Browser

1) Saves Time

Page 40: Designing (Deciding) in the Browser

CSS3 is Powerful

Page 41: Designing (Deciding) in the Browser

CSS3 is Powerful

Page 42: Designing (Deciding) in the Browser

CSS3 is Powerful

Page 43: Designing (Deciding) in the Browser

2) Allows for rapid iteration

Page 44: Designing (Deciding) in the Browser
Page 45: Designing (Deciding) in the Browser

3) Content

Page 46: Designing (Deciding) in the Browser

On a PSD, more time is spent on look and feel of the website. This puts content second.

Page 47: Designing (Deciding) in the Browser

Show Animations

Page 48: Designing (Deciding) in the Browser

CSS3 is Powerful

Page 49: Designing (Deciding) in the Browser

Content is given priority

Page 50: Designing (Deciding) in the Browser

Content is given priority

Page 51: Designing (Deciding) in the Browser

Content is given priority

Page 52: Designing (Deciding) in the Browser

4) Makes RWD easier

Page 53: Designing (Deciding) in the Browser

Let the content determine the breakpoints

Page 54: Designing (Deciding) in the Browser

5) Icon Fonts and SVG

Page 55: Designing (Deciding) in the Browser
Page 56: Designing (Deciding) in the Browser
Page 57: Designing (Deciding) in the Browser
Page 58: Designing (Deciding) in the Browser

6) Browser and Devices

Page 59: Designing (Deciding) in the Browser

Video Credit: https://www.youtube.com/watch?v=_iidwn2kfJU

Page 60: Designing (Deciding) in the Browser

I Use CodeKit

Page 61: Designing (Deciding) in the Browser

BrowserStack

Page 62: Designing (Deciding) in the Browser

8) Performance

Page 63: Designing (Deciding) in the Browser
Page 64: Designing (Deciding) in the Browser
Page 65: Designing (Deciding) in the Browser

9) Accessibility

Page 66: Designing (Deciding) in the Browser

Accessibility

Page 67: Designing (Deciding) in the Browser

Accessibility

Page 68: Designing (Deciding) in the Browser

Testing (user experience, browser & device compatibility, performance, accessibility)

should not be done at the end.

Page 69: Designing (Deciding) in the Browser

Should be done during the design process…

Page 70: Designing (Deciding) in the Browser

..in the Browser!

Page 71: Designing (Deciding) in the Browser

Let's Wrap it up

Page 72: Designing (Deciding) in the Browser

Continue to use Photoshop but quickly move to the browser

Page 73: Designing (Deciding) in the Browser

Workflow• Set clear Goals and Objectives

• Content Inventory/Strategy

• Wireframe

• Design (PSDs)

• Front-end Development

• Back-end Development

• Testing

Make MOST of the design decisions

Make SOME of the design decisions

Page 74: Designing (Deciding) in the Browser

Make all the important decisions in the browser

Page 75: Designing (Deciding) in the Browser

Thank YouEmail: [email protected]

Twitter: @SMY315

Page 76: Designing (Deciding) in the Browser

Questions?