Posted on 01-16-2013
Over the holidays I added a new section to API Evangelist called "trends". One of the areas I’m tracking on is what I’m calling “scripting platforms”. While you can program against any API using the language of your choice, these platforms are aggregating APIs and make available through a custom language stack.
This approach is different than what I’m seeing from aggregate APIs like Singly. Scripting platforms may offer aggregate APIs, but are also providing a way to easily script against them, in new and abstracted ways. I’m still trying to understand each company, as well as the nuances between each approach--so stay tuned.
In the last couple weeks, I’m seeing a possible new approach to programming against APIs come into focus, one that is using HTML instead of scripting--using Markup APIs.
After reading Building Bridges Between GUIs and Code With Markup APIs by Atul Varma (@toolness) from Mozilla, you can really start seeing not just the potential around rich media and content like Mozilla is with its Webmaker platform, but deliver any API resource in abstracted, simplified markup anyone can put to use--without knowing programming.
Lyre Calliope takes this further discussing how, “Webmaker could be an opportunity to define an embeddable API strategy for the entire web”, and that “a Singly Markup API would lower the learning threshold for anyone interested in remixing all of their personal information together in new ways”, in Markup APIs and the Read/Write Web.
I envision Markup APIs, at their simplest working like Mustache Templates where you can easily render data from JSON templates, or be as robust as what Mozilla is doing with their Webmaker platform. Making the web embeddable and remixable like Lyre says.
While scripting platforms are providing an important evolution in APIs for developers, by aggregating top APIs into new resources, the Markup API approach is an interesting evolution in APIs for everyone. And with browser based authentication solutions like Singly's, we can make this a very personalized experience.
I’m still working to understand all the possibilities, but I think both API scripting platforms and Markup APIs will bring us closer to a truly programmable web that is acceptable by everyone.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Will You Add Me To API Evangelist And How To Spot The Cool Kids
- When I Remix APIs Using Swagger How Do I Deal With Authentication Across Multiple APIs
- It Takes A Team Of Evangelists To Raise An API
- Support For Only Two Creative Commons Licenses In The API Commons
- Machine Readable Terms of Service Didn't Read Applied To APIs Via APIs.json
- API Deployment For Non-Developers Using Zapier, Google Docs, and APISpark
- State of Hypermedia Today @ API Craft In Detroit
- Need A Formal API Standard For Your Government Agency? Fork 18Fs, And Make It Your Own!
- CORS Makes Your API Portable And Remix-able
- Chief Data Officer Needs To Make The Department Of Commerce Developer Portal The Center Of API Economy
- An API Definition As The Truth In The API Contract
- Look At Existing APIs In The Space Before Designing Your Own
- Libraries Hacked: UK Library API, Data And Technology Hacks
- Financial Data Aggregator Yodlee Looking For A Director of Developer Evangelism
- AutoDevBot Open Sources Their API Monitor
- Low Hanging Fruit For API Discovery In The Federal Government
- Looking At 77 Federal Government API Developer Portals And 190 APIs
- Applying APIs.json To API Discovery In The Federal Government
- The Power In API Discovery For APIs.json Will Be In The API URL Type
- Fixing The Machine Readability in API Commons
- Evolving How We Approach The API Lifecycle With APIMatic
- APIs Can Open Up Your Company To Outside Ideas
- APIs Are Often Just A Facade That Is Covering Up The Legacy View Of World
- A Mobile Developer Toolkit With The University Of Michigan APIs
- Kicking Off Image Manipulation API Work