Good tips on prototyping using the very materials that the final product will be built in—HTML, CSS, and JavaScript.
The only thing I would add is that, in my experience, it’s vital that the prototype does not morph into the final product …no matter how tempting it sometimes seems.
Prototypes are made to be discarded (having validated or invalidated an idea). Making a prototype and making something for production require very different mindsets: with prototyping it’s all about speed of creation; with production work, it’s all about quality of execution.
The power of prototyping:
Most of my work is a set of disposables rather than deliverables, and I celebrate this.
I like the three questions that Chris asks himself:
- What’s the quickest, cheapest thing I can create to help make the next design decision?
- What can I create to best demonstrate the essence of the concept?
- How can I most effectively share the thinking behind the design with decision-makers?
A good looking artifact too early in the process gains buy-in too quickly and kills discovery.
Cennydd enumerates what design sprints are good for:
And also what they’re not so good for:
This is a clever quick’n’dirty way of prototyping iterations on an existing site using dev tools and screenshots.
I’ve thought often of how our design and prototyping tools for the web are often not of the web. Tools like Photoshop and Sketch and Invision create approximations but need to walk the line between being a tool to build native apps and to build web apps. They do well in their ability to quickly validate designs but do little to validate technical approach.
A presentation at An Event Apart Seattle 2019.
Write what you need to test a hypothesis. Then throw that code away.
Once again, Safari has fucked up its implementation.
Some handy tips courtesy of Chris Ferdinandi.
Turning accessibility awareness into action with HTML.