Get in touch

Blog

Most people build IPAs, not APIs — what's the difference?

Originally published on LinkedIn, February 10, 2025.

Most people build IPAs, not APIs: they start with the interface instead of the application and the programmer. The acronym is the sequence.

Most people build IPAs, not APIs.

(And no, I’m not talking about your favorite craft beer—remember, API stands for Application Programming Interface.)

✅ Here’s the right sequence for building an API product:

  1. Application: What’s the use case or app?
  2. Programming: Who’s the developer that will use your API to build that app?
  3. Interface: How can you create an interface that serves both the use case and the developer?

❌ The common, but flawed approach is the reverse:

  1. Interface: Start by building out an API from a database schema.
  2. Programming: Generate docs and SDKs, hoping some developers will stumble upon them.
  3. Application: Expect the market to magically build a million apps and throw money your way.

This backward process often leads to failed API products.

So, build your APIs right by starting with the use case and the user in mind. Only then can you design an interface that truly works.

PS. Excited to dive deeper? In my course on Maven, “API Fundamentals for Product Managers,” I’ll be teaching exactly how to build API products the right way. Sign up here and save 5%: https://lnkd.in/gdy7v3ue