we're doing it wrong: prototyping the future of the web

We’re Doing It WrongPrototyping the Future of the Web

Steve Hickey — @stevehickeydsgnUX Designer & Developer at Fresh Tilled Soil

Requirements

Research

Ideate

Design

Code

Launch

A brief “reminder” of waterfall.

Plan

Design

Develop

Test

Build

MeasureLearn

What about agile or lean?

¡Mentirosos!(Liars!)

The traditional point of first contact...

Requirements

Research

Ideate

Design

Code

Launch

“D t!”****

... and its result.

But it’s ok. We can fix that.

Research/Understand Ideate Design

CodeTest

and repeat...& Design & Code & Ideate & Code

& Ideate & Design

Step 1 → Step 2 → Step 3 → Step 4

= Very Pretty BULLSHIT

“Design is not just what it looks like and feels like. Design is how it works.”

Today’s obligatory Steve Jobs quote.

“Form ever follows function.”

A grating reminder of something we all claim to know, from architect Louis Sullivan.

Understanding the problem.

Ideation through sketching.

“Great is the enemy of good.”

Paraphrased from Voltaire, an enlightened dude.

Wireframes. Or are they...

Wireframes. Or are they...

Testable. ASAP.

Sketches are prototypes in waiting.

prototyping on paper

The usual suspects:

Balsamiq Axure InDesign Keynote PowerPoint

Try a storyboarding app.

Briefs Flinto Proto.io

HTML/CSS/JS

Developers need love too.

Fake it.

localStorage.setItem(‘username’, ‘Gary’); var username = localStorage.getItem(‘username’); $(‘div.userinfo’).prepend(‘<h2>’ + username + ‘</h2>’); ======================================================= <h2>Gary</h2>

Make your client fall in love.

Time to test.

“OK, but what about design?”

Mockups = Useless

Try zooming your comps out.

Style tiles use time efficiently.

Design in the browser.

Use the right tool for the job.

Let’s see some examples:

Google Glass

“We were working with the HUD literally on my first day at work. And learning a tremendous number of things that you couldn’t possibly just guess or estimate, or print out on a spreadsheet, or a project map,

and that sort of thing.”

Tom Chi, Google

“Your ears can take a lot more weight than your nose… So if you can create a system where the ear becomes

a fulcrum, then the perceptual weight disappears. This took me about two hours to figure out.”

Tom Chi, Google

Incantor

Our first prototype.

Look, I’m no Olivander. Ok?

Here’s how we overcame my lack of magic.

We made the nav work without looking.

Let’s wrap up.

1) Sketch a lot, it’s quick and efficient.2) Stop wireframing, start prototyping.3) Test early and often.4) Avoid comps for every screen and state.5) Eliminate redundant parts of your workflow.6) Process is not a straight line.

Thanks!