AWS turned storage, computing, databases, and more into an API call. Twilio did the same to phone calls and SMS messages. Stripe did that to money. Sendgrid and Mailgun and more did that to email.
Everything's an API, or so it seems, and you can rapidly turn your idea into an app without negotiating credit card processing rates and telecom deals, or hosting real servers in metal racks.
But that doesn't cover everything. What are the next APIs and computing building blocks that are needed, that can do what AWS did for this generation of SaaS for the next generation of software? Or which of today's computing building blocks could be vastly improved?
I love APIs so listing some that are great examples of building blocks:
Abstract - Collection of APIs to build common features such as email verification, phone validation, Geolocation, etc.
Courier - Design and deliver notifications across multiple channels -- email, SMS, Push, Slack, etc.
Pusher - In-app chat, location tracking, notifications, and charts/dashboards for your app.
Obviously - Add ML-based predictions or NLP to your app.
Datawaves - Add visualization of event analytics to your app.
Mux - Live and on-demand video experiences.
Cloudinary - Image and video manipulation
I believe the next wave of building blocks will not belong to a behemoth such as AWS. Instead, best-in-class products will offer APIs to expand the distribution of their existing products.
Tray embedded is also a great example. Want to enable your users to integrate your product with hundreds of others? Why build them when you can use a best-in-class product's API to do this?
Great tweet about this -
And feel like there is so much potential to wrap important building blocks of businesses into an API call. Some fav examples are:
Shipping - https://goshippo.com/
Direct mail (Yep, still matters) - https://www.lob.com/
Content Management - https://www.contentful.com/
Ecommerce - https://commercelayer.io/
Search - https://www.algolia.com/
And so many more still to be built...
Sad to say this, but probably the ability to target people better once you've build your application. Currently, only big companies who can pay DSPs to get troves of user data or the main providers themselves (Google, Facebook, etc.) let you have access to these millions of cookies for advertising purposes. I think this will be democratized where a maker could pay by the request (e.g. I have an email address, give me everything you know about that person) to better target that person with features, content, and in-app messaging. Guessing one of these providers will set up a model where you can purchase a cookie like a serverless function.
Disclaimer: I’m VP sales for the company.
We’re working to make the pains of privacy compliance (GDPR, CCPA, etc.) just go away.
Dataswift provides APIs and a PaaS that provides secure, privacy compliant mobility of PII across apps, services, and borders using PDAs, or personal data accounts. They're hosted by us, legally owned by the individual customer, and accessible on-demand by app builders.
Ever been frustrated learning how to use a new piece of software because of all the options and not sure where to start? Is there any software that can switch to a "beginners" mode? Meaning, hide...
Over the last couple of years, we’ve personally experienced substantial business challenges associated with navigating from manual onboarding of customers to self-service onboarding of customers. L...
Sometimes you need a new app—and there's nothing that exactly fits the need. That's part of what's made tools like Notion so popular, since you can customize them and build new tools that fit what ...