<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Usability on API Course</title>
    <link>https://apicourse.com/tags/usability/</link>
    <description>Recent content in Usability on API Course</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicourse.com/tags/usability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Designing APIs for Developer Experience: What Makes an API a Pleasure to Use</title>
      <link>https://apicourse.com/designing-apis-for-developer-experience-what-makes-an-api-a-pleasure-to-use/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/designing-apis-for-developer-experience-what-makes-an-api-a-pleasure-to-use/</guid>
      <description>&lt;p&gt;Developer experience is not a soft concern. It determines how quickly developers integrate your API, how many support tickets they file, how many abandon the integration and use a competitor, and how they describe your product to other developers. An API with good developer experience turns integrators into advocates. An API with poor developer experience turns them into complaints.&lt;/p&gt;&#xA;&lt;p&gt;Good DX is not a single feature or a checklist item added at the end of the design process. It emerges from a series of small decisions made throughout design and implementation. Every naming convention, every error message, every documentation page, and every SDK is a DX decision.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
