O'Reilly logo

97 Things Every Software Architect Should Know by Richard Monson-Haefel

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Chapter 96. For the End User, the Interface Is the System

Vinayak Hegde is a geek interested in computers, photography, and entrepreneurship. He is currently working as an architect with Akamai Technologies.

Vinayak Hegde
image with no caption

THERE ARE TOO MANY GOOD PRODUCTS hidden behind bad user-interfaces. The end user will access the system through its user interface. If the quality of the user’s experience while interacting with your product suffers, then his impression of your product will suffer, no matter how technologically advanced and path-breaking your product might be.

The user interface is an important component of architecture and an often-neglected one. The architect should enlist the services of specialists such as user experience designers and usability experts. The user interaction experts, along with the architect, can drive the interface design as well as its coupling with the internal mechanisms. Involving user interface experts at an early stage and throughout the product development phases ensures that the final product is polished, and that the integration of the user interface with the product is seamless. The architect should also look at doing user interaction testing while the product is still in beta with actual end users, and incorporate their feedback into the final product.

Often the usage of a product changes over time as technology changes and features are added. The architect ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required