This was presented at DevRelCon 2018 in London: https://london-2018.devrel.net/matthew-oriordan/
API design is a relatively new discipline, and one could easily fall into the trap of believing there is little experience to draw on, and we are now largely in an unchartered territory. Whilst this is true to some degree, it’s a mistake not to take inspiration from other industries that share common problems. In the last 100 years, graphic designers have learnt through research, trial and error, how to visually communicate messages and content.
Whilst how to apply UX to DX has been covered many times, the visual design process, which typically starts once UX is completed, is rarely talked about. Yet design, following the UX process, is an essential activity that helps communicate the content more effectively and make interfaces more intuitive and approachable.
For example, a car goes through the equivalent of a UX design process to define the function of the car. The form however, is defined as part of the visual design process and is arguably the most important aspect of what creates a lasting impression for buyers. Skipping the visual design phase in our APIs may still result in functional APIs, but in a form that is not pleasing to developers who use them.
In this talk, we will explore common visual design principles and how they apply to API design. By the end of the talk, you will have a basic understanding of popular visual design principles, and be able to incorporate these principles into your DevRel handbooks or API style guides. Specifically, what you will learn is how to create a positive lasting impression for developers who use your APIs.