INTERFACE DESIGN AND DEVELOPMENT: COMMUNICATION AS A DECISIVE FACTOR

“Designers create the design for a product, and developers implement that design.” But is it really that simple? In reality, misunderstandings sometimes arise regarding the implementation of design specifications or the roles of team members.
One might think that “good design” is something universally valid and the same for everyone. But that is far from the case. While some appreciate the complexity of a long table with scroll bars and consider it good design, others are shocked by such a “designless” Excel look.
So how do we arrive at a common understanding of what constitutes a good program or website?

Are We Talking about the Same Thing...

“A problem well put is half-solved” (John Dewey)

A shared understanding of what the end result should look like is important for the success of a project. To achieve this, designers and developers need to talk to each other and exchange ideas at an early stage. In order to create a common basis, designers should not only present the design to the developers for implementation, but also explain the concept as a whole. This allows the developer to grasp the underlying design idea and gives them the opportunity to contribute their own ideas.

The specifications should be formulated by the designer in as much detail and as comprehensively as necessary. For example, the developer needs to know how a button should behave and look in the mobile view. This provides them with guidelines and avoids misunderstandings.

... in the Same Language?

“Design should lead development, and development should inform design. Separating these two roles or facets of your application can cause bad experiences for users.” (Andrew Chalkley)

Early and regular communication between developers and designers also helps to see a requirement or problem from the other’s perspective. It is important to bring together the different biotopes in which, according to the cliché, “technically clueless designers” and “design-immune nerds” each romp around.

A common language of principles is important for this. Designers who do not work exclusively in the print sector should be familiar with the terminology used for technical components. Through communication between designers and developers, designers gradually gain a better understanding of the scope and possibilities of technical implementation. This exchange of experience enables them to better assess the complexity of implementing the design and to design it in such a way that it can be implemented appropriately, both technically and in terms of cost.

Ideally, the developer also has a basic knowledge of design principles and is familiar with the basic technical terminology used by designers. Their task is to provide the designer with feedback at an early stage if something cannot be implemented or cannot be implemented in the desired way. It is important for harmonious cooperation to accept each other’s expertise in their respective fields. In the case of the developer, this means sticking to the design and only implementing changes after consultation.

Designers and developers should never lose sight of the end user in everything they do. They must be aware that they themselves are not the target audience and keep this in mind when conceptualizing the design and during development.

In summary, we can say that designers and developers are team members with different skills and perspectives. Only when they work together smoothly can an outstanding product be created. Good communication, a basic knowledge of the capabilities, possibilities, and limitations of each other’s areas of work, and a focus on the user create the conditions for this.