You can never build something that matches an abstract concept in someone else’s mind. A specific real thing will always be different than an unspecific imaginary thing.
The very looseness that is the main benefit of a static wireframe is its greatest flaw. You’ll end up with each person filling in the blanks with their own ideas, but not communicating them, ending up in endless revisions that try to match the non-defined and ever changing ideas in everyone’s heads.
Seriously. I got this process as close to working right as I think you can get it, and it was still full of unnecessary pain.
The goal is to do as little work as possible to create something as close to reality as possible. By making a live, working user flow in code, with interactions very close to the real thing, you enable everyone to understand the same specifics.
Don’t do things slower and less effectively just because you’re used to being slow and ineffective.
http://www.starbucks.com/ You can see it work by changing the size of your browser window. Other examples: http://css-tricks.com/http://www.fork-cms.com/http://lanyrd.com/To test, go here: http://mattkersley.com/responsive/
An intro: http://johnpolacek.github.com/scrolldeck.js/decks/responsive/A tutorial: http://blog.teamtreehouse.com/beginners-guide-to-responsive-web-design
When your wireframe is in code, you can test it on any device you have, and it adapts to the device.
When your wireframe is just a graphic, it either doesn’t work on mobile devices, or you have to make different graphics for each device.
Tony Stark didn’t care about his suit being perfectly styled. He cared about it kicking ass.
All the tools you need are free, and you should already know how to use enough to make a prototype if you’re in this industry. Beginning level knowledge should be enough.
You need to validate you’re making the right thing as early as possible in the process. This is just common sense. The farther into development you are when you discover you’re building the wrong thing, the more time and money you’ve wasted.
The hard stuff is already done for you.
Once you learn how to use these tools, you can move very, very fast. Because you’ll stop wasting time doing things that aren’t important, and spend it on things that are vital instead.
I’m not kidding about this. Each page should take 1-2 hours, maybe 3 if the interactivity is very complicated. Four if you’re just getting started.
If you use SASS, you may want to try the Foundation framework. Or do like I do and write code so DRY (Don’t Repeat Yourself) you don’t really need tools to help you deal with badly planned CSS.
Fuel UX adds several useful components. http://exacttarget.github.com/fuelux/Font Awesome makes icons that scale without pixelating because they’re an embedded font. Great for Responsive Design. http://fortawesome.github.com/Font-Awesome/
The thing that makes Bootstrap so easy is you define it’s functionality with HTML and CSS. Use the right elements and classes, and Bootstrap does the rest.
We have seen serious, tangible gains from adopting this process. We will soon be using these interactive prototypes for User Testing, and doing early Accessibility testing, which will accelerate things even further.
All of the code you’ve written is production ready, and perfect for building on.
1. Rapid and Responsive UX To Prototype with Bootstrap
2. What I’m Going to Say• Build things faster and better• Important Words: Responsive, Prototype, Framework• What is Bootstrap• A startling revelation
3. But first…
4. I’m Josh Jeffryes• Lead UI Developer at The College Board• Mentor at Acceleprise• Veteran of a few startups• Advise various startups on UX & UI• I will help you, just ask
5. Make Web Stuff RightThe bad old way: – Requirements – Go straight to code and design – End up with something that can’t match the magical unicorn they originally wanted
6. Make Web Stuff RightThe bad old way: – Requirements – Go straight to code and design – End up with something that can’t match the magical unicorn they originally wanted
7. Make Web Stuff RightThe slightly less bad new way: – Requirements – Make a really nice wireframe – Write a lot of code – Descend into development hell because a static wireframe is nothing like the site you build from it
8. Make Web Stuff RightThe slightly less bad new way: – Requirements – Make a really nice wireframe – Write a lot of code – Descend into development hell because a static wireframe is nothing like the site you build from it
9. Make Web Stuff RightThe better way: – Requirements – Sketch out some loose wireframes – Create a fast prototype with a little code – Iterate the small pile of code until right – Write a lot of code – End product matches the prototype, everyone is happy
10. Make Web Stuff RightThe better way: – Requirements – Sketch out some loose wireframes – Create a fast prototype with a little code – Iterate the small pile of code until right – Write a lot of code – End product matches the prototype, everyone is happy
11. Make Web Stuff RightIf making a prototype in code is as fast or fasterthan making a wireframe in Illustrator, and getsbetter results, why wouldn’t you?
12. Three Important Words Responsive Prototype Framework
13. What is Responsive? This is all the same site.
15. What is Responsive?On a Computer: On a Phone: This wireframe is responsive.
16. What is Responsive?On a Computer: On a Phone: This one is not.
17. What is a Prototype?
19. What is a Prototype? A prototype makes sureyou’re building the right thing, not the right look.
20. What is a Framework?
21. What is a Framework?• Pre-built HTML, CSS, and JS• A structure you can build on• Here are some wheels, stop reinventing them
22. Merge to Form Awesome!Responsive + Prototype +Framework means you canquickly build things with loadsof features that look nice andwork well on any device
23. Merge to Form Awesome! Quickly as in hours.
24. Merge to Form Awesome! Quickly as in hours. Use them on anything
25. Twitter Bootstrap
26. Twitter Bootstrap• Recently updated to 2.2.1• Released August 2011• 156kb total minified• OOCSS structure (DRY CSS)• Many included Components• Uses LESS• You don’t have to
29. Twitter BootstrapA Grid Content of some kind here This is the main area Sidebar<div class=“row”> <div class=“span9”> Content of some kind here <div class=“row”> <div class=“span6”>This is the main area</div> <div class=“span3”>Sidebar</div> </div> </div></div>
32. Recap• Go from sketch to interactive prototype• Responsive: adapts to any device• It’s easy and crazy fast
33. Recap• Go from sketch to interactive prototype• Responsive: adapts to any device• It’s easy and crazy fast• My team is 2 months ahead now
34. A Startling Revelation
35. A Startling RevelationWhen your prototype is done, you don’t throw it away
36. A Startling Revelation It’s your site.
37. That’s All, Folks Thank You, Here are Some Links• http://twitter.github.com/bootstrap/• http://fortawesome.github.com/Font-Awesome/• http://exacttarget.github.com/fuelux/• email@example.com or @jjeffryes on Twitter