Myles Braithwaite

Lets say you run a website that allows people to store what they ate for lunch. So you have an input box that asks a simple question, What did you eat today for lunch? Your users enter what they ate for lunch and it post on the website. Simple eh. While your users want to be able to share what they ate for lunch with their friends so you add the ability to do that. Still pretty simple eh. Soon you might add cross tagging and the like to create pretty graphs and statistics to show that one of your users has eaten peanut butter and jelly for the last two years. Still some what simple.

One common thing about the features added above is that they are all back-end features. You don't have to change you design to implement them.

Okay so your little startup has become extremely popular and maybe it just got bought by some large corporation. One of your new co-workers keeps talking about how Ajax and how it is the future of web applications and your small fun application should change to a complex JavaScript version soon.

This is the issue that is facing many simple web applications. Lets take as an example Delicious. Why do Delicious users use Delicious? To keep a copy of their bookmarks in a central location. Sounds simple enough. Then why do they have to make it so JavaScript intensive. I use to be able to easily load Delicious on any mobile device (Nokia N800, iPhone, etc.) and it would work. But now it is pretty much unnavigable.

This is why I started iDelicious a simple bare bones front-end to Delicious. No fancy JavaScript any where (while maybe Google Analytics).

Read this next
You might enjoy