ritual
Sort of underway by then
The most incidental detail
A ritual of unpacking
I love the process of unpacking something. You design a ritual of unpacking to make the product feel special. Packaging can be theater, it can create a story.
Dwelling in ritual
Even a dwelling is a device that generates a distinct pattern of daily activities and their relationships. Some buildings are explicitly built for ritual, but the repetition of any activity, either mundane or religious, tends to ritualize them, and by facilitating this, an architectural structure can turn gradually – sometimes even unnoticeably – into an instrument of ritual.
The ritualized use of a place
The association of comfort with people and place are reinforced by the ritualized use of a place. Using a place at a set time and in a specific manner creates a constancy as dependable as the place itself. It establishes, in time and behavior, a definition of place as strong as any architectural spatial definition, such as an aedicula, might be. Ritualized use can do more than reinforce the affection for a place. Through ritual, a place becomes an essential element in the customs of a people.
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.