frameworks that offer a seamless way to develop web apps at a large
scale. The days of adding a few animations, light interaction and
form validation then calling it a day are numbered.
It’s amazing how just in the past 3-4 years, users have begun to expect
native-like functionality from their websites. Much of this has to do
with the emergence of the smartphone/tablet and the gamut of rich applications people interact with daily. The bottom line is that people are looking
for a richer, interactive and more fulfilling experience. Why shouldn’t
they? So much of our life is now tied to technology, why not make it
At GraphEffect we knew that version 2 of our product had to be both
performant and fun to use. Currently in the Ad space, most of the UIs
are archaic and filled with useless dashboards and horrible usability.
We knew we wanted to do things differently and to do so meant designing
and developing our app differently than our competitors.
We were at an interesting cross-roads. With our requirement
for an immersive(cross platform) web experience, there were relatively few tools to help us do the job efficiently and not send us spiraling into code hell. Micro-frameworks were an option, but they were fragmented. As these micro-frameworks matured we didn’t want to maintain multiple projects and APIs to run our app.
So after ruling out micro-frameworks we were down to two choices in the
Sproutcore and Cappuccino. After doing some research the answer was
clear that we would be using Sproutcore. Without going too far down the
rabbit hole here is why.
- The developer community was much more active and vibrant
- Apple had already proven it’s use case with Mobile Me and iWork
(iCloud is now using Sproutcore as well)
talent is easier.
In this series of blog posts I will detail the trials and tribulations
of implementing sproutcore into your app and how to get it to production