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.
|Markup API, Mozilla, Mustache Templates, Scripting-Platform, Singly, Webmaker|
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