liveBook · Manning

Developer experience

As explained in Design for Developers

The quality of a developer's interaction with a product and its development-related interfaces or workflows.

Developer experience is how developers interact with a product, API, documentation, or development workflow. Treating it as part of the overall user experience makes products easier to adopt, maintain, and improve. section 1.2.1 section 12.2

Design a useful developer experience by:

  • Making documentation easy to find, clearly branded, and consistent with the product’s design principles. section 12.2
  • Explaining the product’s value and documenting code and APIs thoroughly enough to support adoption and handoff. section 12.2
  • Considering developer needs alongside consumer needs, because difficult implementation work can reduce time available for improving user experiences. section 12.2
  • Use research, planning, wireframing, prototyping, testing, and evaluation as connected parts of an iterative web development process. section 1.2.1

Custom form controls

Custom HTML form controls show how developer experience affects users. When controls are difficult to style or customize, developers may recreate them from scratch, diverting effort from other experience improvements. Better platform support and clearer implementation guidance reduce that burden. section 12.2

Figure 1.3 The iterative process this book covers for a web design or web application project—from identifying the problem to user research, user experience design, design and build phase, and test and evaluate

Use the iterative process to connect problem identification, user research, experience design, building, testing, and evaluation. section 1.2.1

How Design for Developers covers it

How deep it goes
Defines documentation and design considerations, then illustrates implementation costs; stops short of framework-specific procedures.
Examples
Uses API documentation, undocumented legacy code, custom HTML form controls, and an iterative web project process.
What it assumes
Assumes familiarity with developers, products, and web projects while introducing developer experience as a user experience subset.
What you can do after
Apply developer experience principles by organizing documentation, clarifying APIs, and evaluating implementation choices against user needs.
How it connects
Connects user experience, documentation, APIs, web development, accessibility, and iterative design.

Also explained in

Compare how 6 books explain developer experience →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Design for Developers. The section links point to the parts of the book it draws on.