Slide 1

Slide 1 text

DEATH TO WIREFRAMES RAPID LONG LIVE PROTOTYPING

Slide 2

Slide 2 text

1. A TYPICAL PROCESS 2. KILLING IT WITH FIRE 3. FROM THE ASHES 4. RAPID PROTOTYPES 5. QUESTIONS

Slide 3

Slide 3 text

MANUFACTURING, PRINT, AGENCY, STARTUP, ENTERPRISE, PRODUCT, EDUCATION, CONSULTING 13 JOBS / 15 YEARS

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

TYPICAL PROCESS DISCOVER DESIGN DEVELOP DEPLOY

Slide 6

Slide 6 text

TYPICAL PROCESS DISCOVER DESIGN DEVELOP DEPLOY • STAKEHOLDER INTERVIEWS • BUSINESS GOALS • RISK ANALYSIS • COMPETITIVE ANALYSIS • PROJECT BRIEF • CONTENT • STATEMENT OF WORK • FUNCTIONAL SPECS

Slide 7

Slide 7 text

TYPICAL PROCESS DOCUMENTATION

Slide 8

Slide 8 text

TYPICAL PROCESS DISCOVER DESIGN DEVELOP DEPLOY • STATIC WIREFRAMES • PHOTOSHOP COMPS

Slide 9

Slide 9 text

TYPICAL PROCESS MORE DOCUMENTATION

Slide 10

Slide 10 text

TYPICAL PROCESS MORE DOCUMENTATION

Slide 11

Slide 11 text

TYPICAL PROCESS MORE DOCUMENTATION

Slide 12

Slide 12 text

TYPICAL PROCESS MORE DOCUMENTATION

Slide 13

Slide 13 text

TYPICAL PROCESS DISCOVER DESIGN DEVELOP DEPLOY • HTML • CSS • JAVASCRIPT • BACKEND

Slide 14

Slide 14 text

TYPICAL PROCESS DISCOVER DESIGN DEVELOP DEPLOY

Slide 15

Slide 15 text

TYPICAL PROCESS DISCOVER DESIGN DEVELOP DEPLOY

Slide 16

Slide 16 text

MONTHS PASS (OR MAYBE YEARS)

Slide 17

Slide 17 text

TYPICAL PROCESS DISCOVER DESIGN DEVELOP DEPLOY

Slide 18

Slide 18 text

TYPICAL PROCESS • CLIENTS • STAKEHOLDERS • WIREFRAMES • PHOTOSHOP COMPS • HTML • CSS • JAVASCRIPT • BACKEND DISCOVER DESIGN DEVELOP DEPLOY • STAKEHOLDER INTERVIEWS • BUSINESS GOALS • RISK ANALYSIS • COMPETITIVE ANALYSIS • PROJECT BRIEF • CONTENT • STATEMENT OF WORK • FUNCTIONAL SPECS OR NOT BECAUSE LEGAL DIDN’T DO THEIR DO DILIGENCE AND THE PRODUCT YOU WERE BUILDING WAS PATENTED BY ANOTHER COMPANY SO YOU JUST WASTED MILLIONS OF DOLLARS AND A YEAR AND A HALF OF MANPOWER ON A PRODUCT THAT CAN’T BE LAUNCHED AND YOU CAN’T SHOW ANY OF YOUR WORK BECAUSE THE LAWYERS WON’T LET YOU.

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

WIREFRAMES

Slide 21

Slide 21 text

http://www.analyticdesigngroup.com/files/ADGi-home-wireframe_0.jpg

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

WIREFRAMES NOT SUITED FOR DYNAMIC INTERACTIONS

Slide 24

Slide 24 text

WIREFRAMES OPEN TO INTERPRETATION

Slide 25

Slide 25 text

WIREFRAMES NOT USER FRIENDLY

Slide 26

Slide 26 text

WIREFRAMES CREATES A LOB IT OVER THE FENCE MENTALITY

Slide 27

Slide 27 text

WIREFRAMES DRAGS DOWN THE ENTIRE PROCESS

Slide 28

Slide 28 text

MOCKUPS

Slide 29

Slide 29 text

http://www.analyticdesigngroup.com/files/ADGi-home-wireframe_0.jpg

Slide 30

Slide 30 text

MOCKUPS PLAGUED BY THE SAME PROBLEMS OF WIREFRAMES

Slide 31

Slide 31 text

MOCKUPS TIME CONSUMING PIXEL PERFECT DETAIL

Slide 32

Slide 32 text

MOCKUPS DON’T TAKE INTO ACCOUNT USER INTERACTIONS

Slide 33

Slide 33 text

MOCKUPS DON’T TAKE INTO ACCOUNT THE EBB AND FLOW OF THE WEB

Slide 34

Slide 34 text

MOCKUPS SETS UNREALISTIC AESTHETIC EXPECTATIONS FOR CLIENTS

Slide 35

Slide 35 text

MOCKUPS DESIGN CHANGES CONTINUALLY OCCUR CAUSING LOST HOURS IN DEVELOPMENT REWORK

Slide 36

Slide 36 text

MOCKUPS NEARLY IMPOSSIBLY TO MANAGE IN A RESPONSIVE CONTEXT

Slide 37

Slide 37 text

WHY DO WE CREATE WIREFRAMES?

Slide 38

Slide 38 text

TO CREATE STRUCTURE

Slide 39

Slide 39 text

WHY DO WE CREATE MOCKUPS?

Slide 40

Slide 40 text

TO CREATE AESTHETICS

Slide 41

Slide 41 text

WIREFRAMES

Slide 42

Slide 42 text

WIREFRAMES

Slide 43

Slide 43 text

MOCKUPS

Slide 44

Slide 44 text

MOCKUPS

Slide 45

Slide 45 text

FROM THE ASHES

Slide 46

Slide 46 text

“SPEED FIRST, AESTHETICS SECOND.” – JASON FREID

Slide 47

Slide 47 text

CONCURRENT PROCESS DISCOVERY DESIGN DEVELOP • STAKEHOLDER INTERVIEWS • BUSINESS GOALS • USER RESEARCH • USER STORIES • PERSONAS • SKETCHES • STYLE TILES • ELEMENT COLLAGES • STYLE GUIDES • RAPID PROTOTYPE • BACKEND ITERATE & TEST DEPLOY

Slide 48

Slide 48 text

STYLE TILES

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

No content

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

No content

Slide 53

Slide 53 text

No content

Slide 54

Slide 54 text

No content

Slide 55

Slide 55 text

No content

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

Serious About a Web Built Right Serious About a Web Built Right (without taking ourselves too seriously) (without taking ourselves too seriously) Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Etiam porta sem malesuada magna mollis euismod. Maecenas sed diam eget risus varius blandit sit amet non. Vie w this p roje ct Vie w this p roje ct C A L E N D A R

Slide 58

Slide 58 text

ELEMENT COLLAGES

Slide 59

Slide 59 text

No content

Slide 60

Slide 60 text

No content

Slide 61

Slide 61 text

No content

Slide 62

Slide 62 text

STYLE GUIDES

Slide 63

Slide 63 text

No content

Slide 64

Slide 64 text

No content

Slide 65

Slide 65 text

No content

Slide 66

Slide 66 text

No content

Slide 67

Slide 67 text

No content

Slide 68

Slide 68 text

Style guide HOME IDENTITY WEBSITES SANDSTONE OVERVIEW BUTTONS COLORS FORMS GRIDS TABLES & LISTS TABZILLA TYPEFACES EXAMPLES COMMUNITY SITES DOMAIN STRATEGY COMMUNICATIONS PRODUCTS Sandstone grid system Sandstone grid system Responsive Responsive grids grids The default grid system for Sandstone is 12 columns at a width of 940px. See the chart to the right and the grid examples below for further details including tablet and smartphone sizes. Screen format Width Column Gutter # of col. Smartphone (vert.) 320px 40px 20px 5 col Smartphone (horiz.) 480px fluid expansion of smartphone Tablet 768px 40px 20px 12 col Desktop 990px 60px 20px 12 col Download PSDs Download PSDs Desktop Tablet Phone Smartphone Smartphone Tablet Tablet PREV NEXT

Slide 69

Slide 69 text

0. Overview 0. Overview 1. Buttons 1. Buttons 2. Forms 2. Forms 3. Source Code 3. Source Code 4. Text Styling 4. Text Styling 5. Listings 5. Listings 6. Boxed Groups 6. Boxed Groups 7. Icons 7. Icons 8. Navigation 8. Navigation 9. Behavior 9. Behavior 10. Discussion 10. Discussion 11. Colors 11. Colors 12. Animations 12. Animations 13. Select Menu 13. Select Menu 14. Blank slate 14. Blank slate 15. Alerts 15. Alerts 16. Pagehead 16. Pagehead 17. Repo selector 17. Repo selector 2.1 Typical form groups — with a
containing the label and ` containing the form elements. .required - This group is required to submit the form.
Example Text
Example Label
Choose an option Git   Sign up Sign up Sign in Sign in CSS Styleguide Overview Overview Styling & CSS Styling & CSS Markup & Templates Markup & Templates Behavior & JavaScript Behavior & JavaScript Ruby Ruby Words Words Mobile Mobile Example Value Choose an option Example Text Example Label Example Value Choose an option .required Example Text * Example Label * Explore Explore Features Features Enterprise Enterprise Blog Blog Search or type a command ? ?

Slide 70

Slide 70 text

Chris Chris Sign Out Sign Out Search caring.com Backgrounds Reading text basic paragraph or line. Keep the line height at 21px to preserve out vertical rhythm. Contributed (UGC) text basic paragraph or line. Keep the line height at 21px to preserve out vertical rhythm. Caption or Date Link Bulleted List Containers .low-priority-area: Only transparent backgrounds are allowed for this container type. Forms Form instructions come at the top of the form or at the top of a field group. They tell a user what to do and blah blah blah. Standard input field Helper text Standard drop down -- Choose one -- Selected radio button Not selected radio button Typography H1 H2 H3 H4 Styles A-Z Typographic Care Senior Layout Directory BG & Container Matters Caring Forms My Widgets

Slide 71

Slide 71 text

Introduction Introduction Documentation Syntax Documentation Syntax Generate Styleguides Generate Styleguides View the code on GitHub View the code on GitHub KSS is intended to help automate the creation of a living styleguide. A styleguide serves as a place to publish KSS documentation and visualize different states of UI elements defined in your CSS. It’s sometimes hard to explain what a living styleguide is. The best way to explain is through examples. The GitHub CSS Styleguide is a good example of a living styleguide generated with KSS. In particular, you can see the value of KSS on pages like the buttons section. Generating your own styleguide Generating a styleguide with KSS is pretty easy with Rails, Sinatra or any other framework that you can include gems with. These instructions are for setting up a KSS styleguide with the Ruby programming language. Please keep in mind KSS is not a Ruby-only program! This is just one possible implementation of many. Help me write a binary generator to fix this! In the controller In the controller, create a new instance of the KSS parser like so: # Renders the css styleguide in accordance to KSS. def styleguide @styleguide = Kss::Parser.new("#{RACK_ROOT}public/stylesheets") case params[:reference].to_i when 1.0 render :template => "styleguide/css/buttons" when 2.0 render :template => "styleguide/css/forms" when 3.0 render :template => "styleguide/css/icons" end end

Slide 72

Slide 72 text

Kalei - Style guide Kalei - Style guide Generates bootstrap-like documentation for your own CSS! This project aims at making sure your style sheets are fully documented whilst being synchronized with your webpages styles. To do this it actually uses your live stylesheets in so that at anytime you can review how your styleguide looks. This website is a live example generated from Kalei's style.css Star Star 292 292 Fork Fork 51 51 Getting started 1. Download the repository (git clone git://github.com/thomasdavis/kaleistyleguide.git) 2. Serve it on a HTTP server and it should work! 3. Edit js/config.js to point at your own styles.css Rails Gem

Slide 73

Slide 73 text

HTTPS clone URL https://github.com/darcyclarke/DSS.git You can clone with HTTPS, or Subversion.  latest commit 7fd92eabc0 Documented Style Sheets Merge pull request #44 from darcyclarke/bug/fix-whitespace-in-markup shanejonas authored 7 months ago  .gitignore Fixed state parser, added some more styling to example docs and modif… 7 months ago  LICENSE-MIT Added Grunt support 7 months ago  README.md Update _dss reference 7 months ago  dss.js add newlines back in markup 7 months ago  package.json Update _dss reference 7 months ago   README.md README.md Official Logo NPM Package DSS, Documented Style Sheets, is a comment styleguide and parser for CSS, LESS, STYLUS, SASS and SCSS code. In most cases, you will want to include the DSS parser in a build step that will generate documentation files automatically. grunt-dss is the official DSS grunt task which does just that.   Sign up Sign up Sign in Sign in 62 12   Star Star   Fork Fork darcyclarke / DSS PUBLIC    Code Code   Issues Issues 3 3   Pull Requests Pull Requests 0 0   Wiki Wiki   Pulse Pulse   Graphs Graphs   Network Network   ?   Clone in Desktop Clone in Desktop   Download ZIP Download ZIP  95 commits  9 branches  0 releases  5 contributors     master master branch: DSS /  … DSS Generating Documentation Explore Explore Features Features Enterprise Enterprise Blog Blog Search or type a command This repository This repository ? ?

Slide 74

Slide 74 text

StyleDocco StyleDocco generates documentation and style guide documents from your stylesheets. Stylesheet comments will be parsed through Markdown and displayed in a generated HTML document. You can write HTML code prefixed with 4 spaces or between code fences ( ``` ) in your comments, and StyleDocco shows a preview with the styles applied, and displays the example HTML code. The previews are rendered in resizable iframes to make it easy to demonstrate responsive designs at different viewport sizes. Suggestions, feature requests and bug reports are very welcome, either at GitHub or on Twitter (@jacobrask). Installation StyleDocco requires Node.js. After installing Node.js, run npm install -fg styledocco or clone this repository. StyleDocco is free software, released under the MIT license. Examples Stylesheet The following is the code you would write in your stylesheet, and the Output is what you would see in the documentation. /* Provides extra visual weight and identifies the primary action in a set of buttons. Primary */ .btn.primary { background: steelblue; color: snow; border: 2px outset steelblue; } Output Provides extra visual weight and identifies the primary action in a set of buttons. StyleDocco StyleDocco examples examples source code source code

Slide 75

Slide 75 text

RAPID PROTOTYPING

Slide 76

Slide 76 text

FOUNDATION Foundation Features Add-ons Case Studies Docs Training Getting Started Foundation The most advanced responsive front-end framework in the world. Download Foundation 4 12.4k stargazers @foundationzurb Latest Update on Github JUL 12, 2013 Commit a06390f7b8d09447e04204151e970e8e72d8e90c » Clone Now

Slide 77

Slide 77 text

BOOTSTRAP Star Star 52,951 52,951 Fork Fork 17,430 17,430 Follow Follow @twbootstrap @twbootstrap 71.8K followers Tweet Tweet 18.3K Introducing Bootstrap. Bootstrap Bootstrap Sleek, intuitive, and powerful front-end framework for Sleek, intuitive, and powerful front-end framework for faster and easier web development. faster and easier web development. Download Bootstrap Download Bootstrap GitHub project GitHub project GitHub project Examples Examples Examples Extend Extend Extend Version 2.3.2 Version 2.3.2 Version 2.3.2 Bootstrap Bootstrap Bootstrap Home Home Get started Get started Scaffolding Scaffolding Base CSS Base CSS Components Components JavaScript JavaScript Customize Customize

Slide 78

Slide 78 text

RATCHET Star Star 5,076 5,076 Tweet Tweet 3,753 Follow Follow @GoRatchet @GoRatchet 1,884 followers Getting started Once you've downloaded Ratchet, here's what to do next. Prototype iPhone apps with simple HTML, CSS, and JS components. Download Ratchet Download Ratchet R A T C H E T Getting started Components Page setup View on Github

Slide 79

Slide 79 text

MIDDLEMAN + SASS

Slide 80

Slide 80 text

RAPID PROTOTYPING CODE REUSE

Slide 81

Slide 81 text

RAPID PROTOTYPING INHERIT DOCUMENTATION WITH CODE + COMMENTS

Slide 82

Slide 82 text

RAPID PROTOTYPING MORE EFFICIENT USE OF TIME

Slide 83

Slide 83 text

RAPID PROTOTYPING NATURAL FOCUS ON THE EBB & FLOW OF THE WEB & CONDUCIVE TO RESPONSIVE DESIGN

Slide 84

Slide 84 text

RAPID PROTOTYPING CROSS-DISCIPLINE COLLABORATION

Slide 85

Slide 85 text

CONCURRENT PROCESS DISCOVERY DESIGN DEVELOP • STAKEHOLDER INTERVIEWS • BUSINESS GOALS • USER RESEARCH • USER STORIES • PERSONAS • SKETCHES • STYLE TILES • ELEMENT COLLAGES • STYLE GUIDES • RAPID PROTOTYPE • BACKEND ITERATE & TEST DEPLOY

Slide 86

Slide 86 text

4 GOALS OF RAPID PROTOTYPING

Slide 87

Slide 87 text

CREATION IS A SHARED ACTIVITY 1

Slide 88

Slide 88 text

GET TO THE END PRODUCT WITH AS LITTLE WASTE AS POSSIBLE 2

Slide 89

Slide 89 text

CREATE ONLY WHAT YOU NEED TO INFORM AND VALIDATE DESIGN DECISIONS 3

Slide 90

Slide 90 text

CREATE SYSTEMS NOT PAGES 4

Slide 91

Slide 91 text

TYPICAL PROCESS • CLIENTS • STAKEHOLDERS • WIREFRAMES • PHOTOSHOP COMPS • HTML • CSS • JAVASCRIPT • BACKEND DISCOVER DESIGN DEVELOP DEPLOY • STAKEHOLDER INTERVIEWS • BUSINESS GOALS • RISK ANALYSIS • COMPETITIVE ANALYSIS • PROJECT BRIEF • CONTENT • STATEMENT OF WORK • FUNCTIONAL SPECS QUESTIONS?