Posted on 11-29-2012
The team over at Chartboost have a pretty forward thinking blog post about what they see as the next generation of web application development.
They feel that the future is about creating web applications, not sites. The server side should be an API and the client should be a self-contained app which uses the API as its back-end. With mobile applications following the same pattern.
To practice what they preach, Charboost is overhauling their help site to be an API driven web app using the following approach:
- JSON-API - A REST API providing JSON to drive the site
- Responsive Design - Providing an application design that responds to mobile as well as it does laptops or desktop computers
- Vector (Icon Fonts & CSS) - Using a combination of icon fonts and CSS3 to deliver the UI. SCSS - A new technology that uses CSS-preprocessing to make the CSS code cleaner and res-usable
- Markdown - Using the simple markup language to allow anyone on their team to write and edit help articles
- GitHub - Using Github to manage the help center as an open project
Or as Chartboost puts it:
We believe that the web is finally reaching a tipping point. The culmination of a decade of incremental improvements to web technologies is upon us, and lets us do things in a way that is radically new and better.
I’m also playing around with my own approach to delivering apps in this way using Github + Jeckyll + Mustache Templates with JSON data stores, all running as open repositories using Github Pages.
I’ll have more to publish on this in the near future.
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