I believe that REST and JSON are breaking up the web, into smaller more understandable, re-usable, mashable pieces that potentially anyone can use, even non-developers.
I have written several posts on how tools like API explorers and standards like oEmbed are making APIs accessible by non-developers. And I’m always on the look out for new ideas, for new ways to arm the masses with tools that take advantage of APIs.
Evolving on a piece I wrote a couple a months ago about a Widget Builder Environment for APIs, I was envisioning taking Yahoo Pipes to the next level, add in better API support with OAuth, and make it much more simpler to use. I did not get much time to think about it before Audrey introduced me to if this then that (ifttt).
ifttt allows you to creates tasks. Tasks are defined like this: when something happens (this) then do something else (that).
- this (triggers) - The this part of a task is the Trigger. Some example Triggers are "if I'm tagged in a photo on Facebook" or "if I tweet on Twitter."
- that (actions) - The that part of a task is the Action. Some example Actions are "then send me a text message" or "then create a status message on Facebook."
Triggers and Actions come from Channels. Channels are the services and devices we use every day, such as: Twitter, Facebook, Instagram, Email, Phone Call or Weather.
You can put one channel's trigger together with another channel's action to create a task that runs every 15 minutes and can be turned on and off.
Channels are made possible because these services have APIs. ifttt does a remarkable job at simplifying this in a way, I never even imagined, and allows any user to take advantage of two APIs, apply meaningful business logic, and automate the task to run regularly.
What really makes it cool is you can save tasks as “recipes” and share them with friends making this type of API usage and automation a potentially very social thing.
Right now it appears that the ifttt team creates the new channels that are available. Think of the possibilitis if they opened it up to developers to build their own channels and recipes, and created a marketplace of these API automation recipes?
if this then that (ifttt) is pretty cool! I will be playing with more and incorporating into my daily operations, and see if we can make it stick.
|Automation, Facebook, Google Reader, Instagram, RSS, Schedule, Tasks, Twitter|
blog comments powered by Disqus
Latest Blog Posts
- APIs in DFW
- Adding API Broker Under Monitoring for API Aggregators
- The Dark Matter That Make APIs Work
- Potential for API Aggregators to Provide Valuable Industry Data
- My Talk Tomorrow Night at the Dallas-Forth Worth API Professionals Meetup
- The White House Releases An Open Data Strategy
- When API Success Signals Begin Working Against You
- Get To Know Which Languages Your API Developers Are Using
- Twitters Developer Area is More Embeddable Than API
- Overview Of Backend as a Service (BaaS) White Paper
- Make Sure And Have Multiple KPIs For Your APIs
- API Enabled Toys For Our Children
- I Am Speaking At The Dallas-Forth Worth API Professionals Meetup May 14th
- How Much Do You Spend Attracting and Supporting Freemium API Developers?
- What Does The API Evangelist Do?
- Startups Need To Work Together on API Definitions
- Parse Is Successful By Truly Solving Problems for Mobile Developers
- API Commandment: Thou Shalt Not Forego Talking to a Person
- API Trends
- API Priorities
- Have You Taken A Look At AT&T APis Lately?
- Helping People Understand APIs Through Real World Examples
- Evolving Beyond API Service Providers and Tools to Goal Based API Toolkits
- APIs & The Federal Government
- After Last Couple of Weeks, It's Clear There Is Big Opportunity In The API Space