Developing the Invisible

by Luke Wroblewski May 7, 2006

In my Communication Design column this month, I try to smooth the transition from design documentation to front-end code by discussing how to see “invisible” requirements. Hopefully, this perspective enables folks on the engineering and business side of product development to think about layout requirements from the designer’s point of view.You can read the full article on UXmatters:

Developing the Invisible

“Development teams are responsible for putting interactive features and content into a product. Empty space is neither feature nor content. Therefore, it is not a requirement. For a designer, however, whitespace is often just as important as the content on a page.” Read more...