Some of the more enjoyable surfaces (for example, the grain of a fine mahogany table top or a Japanese sword) have an interplay between pattern and texture which, though two-dimensional, suggests the unseen internal three-dimensional array.
As we draw closer, we see that the three-faceted planes of the museum are fabricated out of rectangular panels made of white bronze that was poured directly into dammed forms on the concrete floor of the foundry, producing a surface texture similar to both metal and stone.
I’m now more inclined to attribute Looseleaf’s power to its visual texture than to some cognitive media-style abstraction. And the visual texture owes more to the beauty (yes, beauty!) of the original pdfs from the Vasulka Archive. Perhaps the demo is best understood not as a prototype generic tool, but as a specific curated experience in its own right, with form and content claiming equal importance in its overall success.
Even so, I think there are some general lessons that can be drawn from this demo:
Content is not inert
Visual texture lets content breathe
Visual texture lets the eye wander without losing itself
In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us.
However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap.