Daisy Alioto
Sonic architecture
An Article by Daisy AliotoBrian Eno is well-represented in iOS. His other apps like Bloom, Trope and Air invite listeners to touch the screen to make their own composition. Reflection ($30.99) is different, there is no interaction for the listener. The interface has three buttons: a pause button, a sleep timer, and AirPlay. Reflection produces endless permutations of Eno’s 2017 album, an hour and five minute long title track.
“Just calling it an app is akin to saying Falling Water is just a building,” writes one app store reviewer. “I would not call this an app,” agrees another, “Between the music and visuals it’s more like sonic architecture.” The visuals consist of slowly morphing rectangles that only seem to change in the split second you look away from the screen.
Trees and graphs
A tree is a kind of graph, but a graph can be considerably more complex than a tree.
I have reason to believe, which for brevity’s sake I will treat elsewhere, that the most complex class of processes and structures we humans can consciously prescribe, reduces mathematically to a tree. A tree has a top, bottom, left and right. Its branches fan out from the trunk and they don’t intersect with one another. They are discrete, contiguous, identifiable objects which persist across time. Trees are Things.
Software and websites, however, reduce to arbitrarily more complex structures: they are graphs. A graph has no meaningful orientation whatsoever. No sequence, no obvious start or end—at least none that we can intuit. It is better considered not as one Thing, but as a federation of Things, like the brain or a fungus network, or perhaps a composite artifact left behind from an ongoing process, like an ant colony or human city.