Very well written. As an API company ourselves the hardest choice we have to make is when to use another API vs build on our own. eg: If you are shipping mobile SDKs can you use firebase to have a remote config for your own sdk
I'm not sure that the Shopify decisions to partner with Stripe is a trap-door decision, or comparable to being married. After all, doesn't the Stripe setup abstract out all of the bank account stuff? Such that in concept, in the future, Shopify could still migrate all of the 'Shopify Balance' stuff into some other API -- such as one that Shopify builds?
I assume that Stripe has some path to Power (as per 7 Powers) by way of Scale Economies that may even matter beyond Shopify's scale. But in any case, perhaps in the meantime this at least enables Shopify to embed itself more tightly with its customers thus attaining some Power of Switching Costs, and in the meantime does not necessary cede any power. So perhaps an approaching 100% net gain.
APIs abstract (away) code complexity. Without the nonsense "away" it would read like you're just adding complexity through another layer of abstraction. Which is in reality what Cloud development is. This article is part of the problem. We devs no longer get to write real software and solve interesting problems, just write glue code for one business to skim the margin off a smaller business. Welcome to the Web 4.0. Don't forget to update your dependencies.
Great article, as per usual. What upcoming API first companies are you watching?
I have my eyes on WorkOS, for one. They provide APIs that abstract all the features B2B apps need before they can land enterprise deals. Think SSO, logs, etc. API magic and bundle magic happening in the same company.
Very well written. As an API company ourselves the hardest choice we have to make is when to use another API vs build on our own. eg: If you are shipping mobile SDKs can you use firebase to have a remote config for your own sdk
Not boring at all. Not by a long shot.
Great stuff, Packy! Now I just spent half my morning down the API rabbit hole. Ha!
This is a really great article. Read on 4/27/2023.
Memo to myself: https://share.glasp.co/kei/?p=gYS3sne2FVtIWVndQ6md
The best piece ever written on APIs.
I'm not sure that the Shopify decisions to partner with Stripe is a trap-door decision, or comparable to being married. After all, doesn't the Stripe setup abstract out all of the bank account stuff? Such that in concept, in the future, Shopify could still migrate all of the 'Shopify Balance' stuff into some other API -- such as one that Shopify builds?
I assume that Stripe has some path to Power (as per 7 Powers) by way of Scale Economies that may even matter beyond Shopify's scale. But in any case, perhaps in the meantime this at least enables Shopify to embed itself more tightly with its customers thus attaining some Power of Switching Costs, and in the meantime does not necessary cede any power. So perhaps an approaching 100% net gain.
This was a great post
great post.
ioio
APIs abstract (away) code complexity. Without the nonsense "away" it would read like you're just adding complexity through another layer of abstraction. Which is in reality what Cloud development is. This article is part of the problem. We devs no longer get to write real software and solve interesting problems, just write glue code for one business to skim the margin off a smaller business. Welcome to the Web 4.0. Don't forget to update your dependencies.
This is incredibly comprehensive and easy to follow. Thanks!
Great stuff! Bravo.
Superb note. Nice work.
Great article, as per usual. What upcoming API first companies are you watching?
I have my eyes on WorkOS, for one. They provide APIs that abstract all the features B2B apps need before they can land enterprise deals. Think SSO, logs, etc. API magic and bundle magic happening in the same company.
Fantastic article. As someone who works adjacent to tech (but isn’t a coder) this was so helpful.