Summary (80–120 words):
The post argues that modern products can be assembled from APIs across two layers of the product stack: infrastructure (hosting, communications, payments, security, analytics) and features (user-facing capabilities). Historically, teams built both layers in-house; from 2005–2010, infrastructure providers emerged, and the 2010s saw an explosion of APIs both horizontally (more infra components “API‑fied,” e.g., Stripe) and vertically (“Features‑as‑a‑Service” unbundling product features). A hypothetical app—search, referrals, messaging, booking, maps, social feed—can now be built largely via third‑party APIs, even for small elements like emoji. The drivers are market maturity (more products, larger demand) and tech maturity (better infra APIs enabling feature APIs), a trend expected to continue.
Search Terms & Synonyms (10–20 total):
API-first product development, features-as-a-service (FaaS), unbundling of SaaS, vertical APIs, horizontal APIs, infrastructure APIs, feature APIs, composable product stack, build vs buy software components, API economy, third-party integrations, headless SaaS, backend-as-a-service (BaaS), microservices architecture, developer tooling APIs, modular SaaS, API orchestration, embedded payments API (Stripe), cloud infrastructure (AWS), componentized software