Structure
What the advancing interface leaves behind
A kind of moiré pattern
If the features of many are compared
Architecture equals structure
The brilliance of notion
The shape of the sentence
The right overlap
Separation of surface and structure
The nineteenth century saw an increasing separation between the treatment of the surface and the structure of designed objects. Mass production and a mobile market economy encouraged the production of heavily ornamented yet cheaply fabricated products. Affordable manufacture allowed the burgeoning middle class to acquire “luxury” goods fashioned after objects formerly reserved for an elite.
Rearranged
Put together with odd bits of the useless Clarice, a survivors’ Clarice was taking shape, all huts and hovels, festering sewers, rabbit cages. And yet, almost nothing was lost of Clarice’s former splendor; it was all there, merely arranged in a different order, no less appropriate to the inhabitants’ needs than it had been before.
Structural complexity
The idea of overlap, ambiguity, multiplicity of aspect, and the semilattice are not less orderly than the right tree, but more so. They represent a thicker, tougher, more subtle and more complex view of structure.
What we are accustomed to call beautiful
Most objects which we are accustomed to call beautiful, such as a painting or a tree, are single-purpose things, in which, through long development or the impress of one will, there is an intimate, visible linkage from fine detail to total structure.
The resistant virtues of the structure
A Quote by Eladio DiesteThe resistant virtues of the structure that we make depend on their form; it is through their form that they are stable and not because of an awkward accumulation of materials. There is nothing more noble and elegant from an intellectual viewpoint than this; resistance through form.
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.