Whereas in a textual environment, the user is forced to face the program from a single point of reference, in Cube, the user can shift their focus to anywhere inside the virtual display, in order to gain a better understanding. The 3D dimensionality of Cube allows more information to be displayed simultaneously than does a 2D or 1D interface. As a metaphor, the Cube system describes program construction in terms of dataflow. The graphical interface of Cube is also very simple for those who often deal with geometry as well as computers to use, as it is composed of cubes, cubes within cubes, pipes, ports, and planes. Inputs and Outputs are metaphorically represented by ports.
Pipes connect all of the individual elements together, much as a simple plumbing system is designed.
Flow of functionality and information is done through the pipes. The cubes are lined up in planes depending on correlations between their functions. The major problem with Cube is its absolute lack of any textual representation which could be used to better and more easily understand its operations. 3D figures tend to become confusing, and therefore, a step backwards towards textual representation, in addition to the visual representation, would be useful, perhaps as an automatically generated help file. Cube can become cluttered, and, as opposed to 2D flowcharts, such clutter may make it more difficult, rather than less, to understand the program.