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
- 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
- APIs That Do One Thing And Do It Well Like ZipLocate
- Which API Do I Need?
- The Expanding API Conference Landscape