Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Design Workflows for Rails

John W. Long
October 07, 2011

Design Workflows for Rails

We've come a long way since the early days of Rails. And the entire Rails system, while much more robust, can be intimidating and downright frustrating for designers to get started with. In this talk we'll discuss a couple of different strategies for integrating designers into your team and what you can do to optimize your current designer/developer workflow. We'll be discussing a couple of tools that can assist you in this (including John's very own Serve project) and will ask the if any of this can be applied to Open Source. Along the way we will be talking a lot about the value of taking a design-first approach to software development and you will walk away with a number of practical approaches that you can apply to your current project even if you aren't working with a designer. (Given at ArrrrCamp 2011)

John W. Long

October 07, 2011
Tweet

More Decks by John W. Long

Other Decks in Design

Transcript

  1. 1. Passionate Users 2. Fewer Support Issues 3. Easier to

    Program 4. Competitive 5. Conversions 6. It’s fun! Why Design?
  2. 1. Users First 2. Guides Users 3. Avoids Surprises 4.

    Delights 5. Lightweight 6. Compromises Good Design
  3. What do you think about this? Would you actually pay

    money for this? How much? How can we make this better? Should we remove anything?
  4. 1. An Idea 2. An Assertion 3. An Experiment 4.

    Customer Feedback Customer Development
  5. Allow a regular user to view an activity stream generated

    from other users interactions across the system Example 3
  6. Allow a regular user to keep track of what his

    friends are doing on our site Example 3
  7. User Stories 1. Start here 2. Loose definitions / big

    picture 3. Keep team focused on end user 4. Wonderful with clients 5. Single most important tool
  8. Whiteboards • Great for brainstorming with customers • Great for

    illustrating flow • Lightweight • Hard to take with you
  9. Wireframes • Moderately lightweight • Capture more detail • Easy

    to showoff to customers and stakeholders • Anyone can build them
  10. Hi-Fi Mockups • One step from HTML • Help establish

    look & feel (also tone) • Typically require professional help • Most potential for error
  11. HTML Prototypes • Allow you to test flow • Can

    be improved over time • Great for client and customer conversations • Can leveraged for actual application (1/4 effort; makes estimating a cinch)
  12. Functional Prototypes • Great for refining algorithms, user interactions, gestures,

    anything that is complex • Also great for client and customer conversations • Don’t need to be written in/for target language or platform • May also be leveraged for the actual application
  13. Serve • Made for designers • Rails newbies are right

    at home • Keeps designers out of the app • Can become unwieldy with iterative design/dev cycles http://get-serve.com
  14. • Rails Plugin (direct integration) • Creates a “/mockups” route

    • Use app layouts/partials/etc • Great for iterative development http://github.com/adamlogic/showoff Showoff
  15. The Challenge What can we do to make it easier

    for designers to get started with Rails?