Argh, this would've been so useful just 48 hours ago at a big client meeting where I presented a dozen wireframe layouts with a responsive design. As a designer

Argh, this would've been so useful just 48 hours ago at a big client meeting where I presented a dozen wireframe layouts with a responsive design. As a designer, I tried something new by skipping Fireworks and going straight from sketches to laying it out in Bootstrap. Pros: saved an insane amount of time - a dozen templates instantly became 48 templates because each page had 4 resolutions. Cons: * it was awkward to resize the browser window 4 times per page, so this Responsive.is tool would've helped immensely, especially with how it highlights the active window port and allows the rest of the content to be masked but still faintly visible, so the layout doesn't feel cramped because you can see a quick preview of the rest of the content "below the fold". * the default Bootstrap styling is so plain that it felt like half of the critiques were about the boxiness of the visual design, not the visual hierarchy of the information itself. Themes wouldn't help for this particular client because they're a big giant company that have their own branding anyway. So prototyping with Bootstrap gave me way more templates in a short of amount of time but it's ugly enough that stakeholder critiques were distracted by it (which is why I usually stick to high fidelity mockups and use wireframes only for internal team collaboration, if at all). More production-ready in some ways (the frontend dev on the team finally got engaged with feedback and is ready for handoff) and less in others (stakeholders won't give real feedback until they see it styled with polish).