Nicholas Rougeux
Werner’s Nomenclature of Colours
A Website by Nicholas RougeuxA recreation of the original 1821 color guidebook with new cross references, photographic examples, and posters designed by Nicholas Rougeux.
Title Cities
An Artwork by Nicholas RougeuxA book’s title page contains more than its namesake—including its author, contributors, publisher, and release date, and. Antiquarian books are known for having lengthy titles, especially those of a scientific nature. These books’ frequently unassuming title pages are gateways to a wealth of knowledge and the focal point of this project.
Title pages of antique influential scientific books covering a variety of subjects were coded and reimagined as colorful cityscapes based solely on their words to illustrate the unique body of knowledge readers would find within.
Boxes were drawn around each word of a title page and color-coded by its first letter (words beginning with “A” are one color, “B” another, and so on). Each title page has its own palette. Those boxes were then upended and arranged to form an abstract cityscape while maintaining their original sizes relative to each other.
British & Exotic Mineralogy
A Website by Nicholas Rougeux
The Fidelity Curve
How do we choose which level of fidelity is appropriate for a project?
I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing.
I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing.
Four levels of fidelity
Suppose we have four levels of fidelity…
- Rough sketch (on paper or an iPad)
- Static mock-up (eg. Photoshop or Sketch)
- Interactive mock-up (eg. Framer, InVision)
- Working code prototype (HTML/CSS, iOS views)
Depending on the feature you’re working on, these levels of fidelity take different amounts of time to create. If you plot them in terms of time to build versus confidence gained, you could imagine something like a per-feature fidelity curve.
Time to build versus confidence gained
Take a simple CRUD web UI, where you’re just navigating between screens. It doesn’t take much more time to build the real version than it does to mock it when the design is simple. If you were to build out an interactive mock first, you would end up spending twice as much time in total without gaining much out of it.
Contrast that with a complicated Javascript interaction. Or a native iOS feature that requires programmer time to build out. If it takes substantially more time to build the real code version, then it may be smart to do an interactive mockup first.