Spannender Podcast hier zum Thema API und Geschäftsmodelle. Hört mal rein!
Keine News mehr verpassen! Jetzt den Newsletter abonnieren .
APIs (application programming interfaces), observe the guests in this episode of the a16z Podcast, can be described as everything from Lego building blocks to Tetris to front doors to even veins in the human body. Because the defining property of APIs is that they’re ways to send and receive information between different parts, that is, communicate between software applications (which often map onto different organizational functions/services in a company too). APIs therefore give companies access to data and competencies they wouldn’t otherwise have — or better yet, that they no longer need — by letting even non-tech and small companies combine these building blocks to get exactly what they want.
Which means companies today — including non-tech companies and small companies — can focus on their core competency instead, access bigger data, and get superpowers to scale and compete with the Amazons of the world. But what does all this mean for design — after all, APIs are interfaces between software, not people — and for other stakeholders (finance, ops, etc.) beyond developers? Who do you sell to? How are APIs changing not only the (inter)face of business today, but how entire companies are being formed from — or around — them?