Coding Architectural Deisgn

[Original Image © Leszek Glasner Via Shutterstock, Reinterpretation by Stephen Coorlas]


It can easily be overlooked, that software "architects" are becoming more responsible for daily experiences than physical-world Architects. For many, the majority of our daily lives are spent interacting with digital technology and devices. These devices run on very specific software, that have very specific structures & architectures. But, we navigate these programs the same way we navigate through our homes; storing things in places we shouldn't, and labeling them improperly; doing things the way we know, instead of the way we should. The fields & practices of digital user-interface designers and  physical world designers are not as unrelated as one might believe. As designers we can isolate the unique qualities that benefit the desire of navigating a digital software, over a physical environment:
Structure is Hidden. The quality of mystery allows users to focus on what's immediately in front of them; and what's immediately in front of them is exactly what the designer intended for the user to be focused on.
Navigation is Absolute. Sequence is the result of a deliberate link or passage between one frame and the next. Abstract navigation can be achieved, but not unknowingly by the user. 
Atmosphere is Personal. Software allows for custom user preferences; color themes, tool bars, "arrange by" options.
Aesthetic is Transposed. Architectural shape & form are reduced to networks. Visual space is created though interpreted pattern.
Function is Evolving. Functions grow and change based on user feedback. The purpose of an application can evolve with the industry. The purpose is adaptable. 
Architecture should be more deliberate. Through the consideration of the above mentioned criteria, we will create registered forums to explore meaningful new experiences.

- Stephen

Inspired by Michael Kilkelly's article on ArchDaily: