No Flash Required: SproutCore Project For Rich Browser Apps

EddieC 0 Tallied Votes 435 Views Share

Apple has done it again. This time with SproutCore, a JavaScript framework that simplifies development of native-looking Web-based applications without the need for Flash or any other specialized runtime. Apple has reportedly contributed loads of resources to the project, which was originally developed by SproutIt creator Charles Jolley. He now works for Apple’s MobileMe service (formerly known as .Mac).

Though most of the reports I’ve read about SproutCore are calling it a Flash killer, the I’ve seen make it look more like an Ajax than Flash. And comparing it with Microsoft’s SilverLight makes even less sense; Flash at least uses ActionScript, which is based on JavaScript. There are other parallels.

Like Flash, JavaScript is ubiquitous, perhaps ever more so than Adobe’s plug-in. With Apple developers no longer dependent on the Flash runtime, they are free to build apps intended for both Mac OS X and iPhone, for which only Flash Lite is available. And like Flash apps, those built for SproutCore will run just about anywhere, provided there’s a browser with JavaScript.

According to the SproutCore help page, “SproutCore is a framework for building applications in JavaScript with remarkably little amounts of code. It can help you build full 'thick' client applications in the web browser that can create and modify data, often completely independent of your web server, communicating with your server via Ajax only when they need to save or load data. JavaScript applications are faster, easier to use, and a lot easier to write than complicated Ajax-driven applications. When you use a framework like SproutCore to help you, they can also be a lot of fun to write."

What’s more, Apple no longer as has to wait for Adobe to get around to releasing updated Flash players and plug-ins for its platforms.

An excellent AppleInsider article calls SproutCore “Cocoa for the Web,” referring to the native development environment for Mac OS X. The also includes a tutorial, excellent , a, and.

Dani AI

Generated

flagged an important moment in client-side UI history back in 2008; the landscape changed a lot after that. The SproutCore codebase split: the “next‑generation” rewrite (SproutCore 2.0) was renamed and released as Ember.js in December 2011, and Ember has continued as the actively developed descendant of that effort. (en.wikipedia.org)

SproutCore 1.x persisted as a separate project but moved into a lower‑activity, legacy state (the last widely noted 1.x release is 1.11.0 from early 2015). (en.wikipedia.org) For modern greenfield work, choosing an actively maintained framework is usually more practical; Ember remains a solid, convention‑driven option for large single‑page apps. (emberjs.com)

For threads like this where someone (for example, ) is curious about “trying SproutCore,” here is a compact, practical checklist for dealing with SproutCore code today:

  • Inventory: capture app dependencies (package.json / Gemfile), build tools, browser support matrix, and any server API contracts.
  • Stabilize: add or improve automated tests and a repeatable build pipeline before touching feature code.
  • Options: continue maintaining SproutCore (small teams), migrate to Ember (architectural similarity), or perform an incremental rewrite to another modern framework—split the UI into small components to make phased migration feasible.
  • Tooling note: modern SproutCore build tooling is available via npm; projects that still use older Ruby‑based tools will need tooling updates as part of the migration. (npmjs.com)

Short summary: SproutCore mattered historically and influenced Ember; however, for new projects in the current ecosystem the maintenance burden of a legacy SproutCore codebase should be weighed against migration to a maintained framework and the team’s capacity to support older tooling.

Member Avatar for Member #949455
Member #949455

No Flash Required: SproutCore Project For Rich Browser Apps

Thanks for the article. I never heard of SproutCore til now. I might test this out.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.