This observation, the basis of our work on Intention Space as in Fig 4, aligns with observations made by the famous UI/EX expert Dr Don Norman in his book on Emotional Design \cite{wikipediaa}. While Dr Norman takes his view on the UI/UX of what is designed, Intentional Space allows one to take it to the micro units of software development. It opens up a means of human communication between the designer and the user of an artifact.
Use Of Designed Artifact and Software Execution Analogy: Re-engineering Affordance
The whole approach of Intention Space to software development is hinged on our view of any software artifact as a design piece, similar to any design artifact like a spoon, a door, or a staircase, where the execution of the software piece is akin to the usage of the design artifact in real life. As the software developed in Intention Space carries the extra dimension of its behaviour and specification being narrowly defined within the boundary of a design chunk at execution time with some specific intentions, we believe Intention Space opens up new possibilities in the Design world where affordance can be re-engineered based on human-readable Intentions embedded with design, giving pointers to the 'why' of any design artifact.
By considering software as a design piece, Intention Space emphasizes the importance of defining clear intentions and behaviours for each design chunk, similar to how a physical artifact is designed with a specific purpose and function in mind. The execution of the software, driven by these intentions, aligns with the usage of a physical artifact based on its design and intended purpose.
Open Pool of Shared Intents in a Society that Transacts Artifacts
An App in an Intention Space will typically have hundreds of Intentions. As intention work as pointers to code, sharing Intentions will be a common practice when developing multiple Apps in an Intention Space.
Sharing Intentions across multiple artifacts in social settings has a similar benefit in cooperative design. People design and construct things in components because there is a cognitive load boundary of how much an individual or group can handle and manage. Many times components build a hierarchy by putting one component within another.
Intention Space provides a linear representation of Intents, which allows for easy access to shared Intentions from multiple components while an Artifact is in use. This accessibility of Intentions at execution time enhances the design-time decisions and enables a more coherent and flexible user experience.