Posted on 08-20-2014
I depend on a number of cloud services to make my personal and business world go round. Even as a programmer, who can hand code just about any script to integrate, automate, and orchestrate my world, I find myself using more reciprocity services like IFTTT and Zapier.
API reciprocity providers are one of the most important evolutions of the API space, because they make the whole world of APis accessible to the normals, and not just to the geek crowd. My time is valuable, and personally I'd rather being using existing tools and services, rather than re-inventing the wheel, and when it comes to orchestrating my online life, I need all the help I can, which is why I am looking IFTTT and Zapier for help.
I’ve been using both platforms in 2014, but as I do with any other software I’ve been dating for any sustained period, I start looking at getting a little more serious. This is where I have to part ways with IFTTT, and other other platforms that don’t have clear relief valves for their free tier, allowing me to start paying monthly or annually for my use of their service, and sensibly scale up as my needs grow.
Zapier has a pretty straightforward pricing framework, giving you just enough room to get hooked, then you can pay for more usage as needed. Having a free tier for any cloud service is essential, but having a tiered business model, and clear monetization strategy, so I know that you will be around in the future, is a requirement.
I will keep my IFTT account to play with, but when it comes operating my business, continuing to integrate Zapier into my workflow makes sense as they have a clear business model that fits my needs. Plus Zapier has an API. Ummmm…hello? An API for your automation and integration layer across all the services you depend on, via their APIs--how cool is that!
When launching your own APIs, make sure it has a clear, visible, intuitive and ascendable service framework--it is something that will go a long way in helping companies decide if they will use your APIs, or not.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- My API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API
- Relationship Between APIs And Containers
- Real-time and Visualizations Will Be Key in Financial API Deployments
- Notification Focused Startups Within Leading API Ecosystems