Brian 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.
While the client has some knowledge of his symptoms, he may not understand the real causes of them, and it is foolish to try to cure the symptoms only. Thus while the systems engineers must listen to the client, they should also try to extract from the client a deeper understanding of the phenomena. Therefore, part of the job of a systems engineer is to define, in a deeper sense, what the problem is and to pass from the symptoms to the causes.
Just as there is no definite system within which the solution is to be found, and the boundaries of the problem are elastic and tend to expand with each round of solution, so too there is often no final solution, yet each cycle of input and solution is worth the effort. A solution which does not prepare for the next round with some increased insight is hardly a solution at all.
I suppose the heart of systems engineering is the acceptance that there is neither a definite fixed problem nor a final solution, rather evolution is the natural state of affairs. This is, of course, not what you learn in school, where you are given definite problems which have definite solutions.