Well, at least kill the need for Flash on the iPhone? Daring Fireball says a simple “yes” to Yahoo! Tech’s question.

The idea is that a standards based technology, open and broadly used, could make redundant proprietary and sometimes bloated and buggy plugins like Adobe Flash, Microsoft Silverlight, and Sun JavaFX.

Apple’s Safari, including Mobile Safari on the iPhone, and Mozilla Firefox are already supporting HTML5 features. Microsoft’s Internet Explorer — so far — isn’t.

The article gives pros and cons for both sides of the debate. Since Apple is introduction the third generation of their iPhone software tomorrow, and still no Flash in sight, we likely have a good idea which way they’re leaning already…

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Could HTML 5 Kill Flash on the iPhone?

If the next great future of computing in the Cloud, as many pundits — not to mention Google — think, then the next great race is delivering that future via Rich Internet Applications. Right now, there are two major ways of doing this. The first involves using a proprietary, locked in technology (admittedly with increasing “openness”) like Adobe’s Air/Flex/Flash trifecta, or Microsoft’s .Net/Silverlight double team. The second is with truly open standards such as HTML, CSS, and AJAX (Asynchronous Javascript and XML) like Google, Yahoo, and many others use.

With the iPhone Apple has squarely planted itself in the second category. They even promoted them as a pseudo-SDK for a time! (And maybe gave up too soon?)

Flash-free, Silverlight-less, but full of interactivity and cloud-based applications, Apple just unleashed .Mac upgrade MobileMe complete with “desktop class” mail, calendar, contacts, and photo gallery web apps.

And according to this year’s WWDC buzz, they used SproutCore’s Javascript frameworks to do it? Why?

SproutCore not only makes it easy to build real applications for the web using menus, toolbars, drag and drop support, and foreign language localization, but it also provides a full Model View Controller application stack like Rails (and Cocoa), with bindings, key value observing, and view controls. It also exposes the latent features of JavaScript, including late binding, closures, and lambda functions. Developers will also appreciate tools for code documentation generation, fixtures, and unit testing. A key component of its clean MVC philosophy that roots SproutCore into Cocoa goodness is bindings, which allows developers to write JavaScript that automatically runs any time a property value changes. With bindings, very complex applications with highly consistent behavior can be created with very little “glue” code.

Check out the read link for more on Apple’s use of SproutCore, and how it might just be part of a growing trend for open standards-based web interactivity.

Read

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

SproutCore Another Nail in the iPhone Flash Web App Coffin?

We’ve covered the iPhone Flash saga ad nauseam here, but in an interesting post involving the technology itself, NetNewsWire developer Brent Simmons (via DaringFireball) shares some interesting error/crash logs highlighting the instability-adding benefits of Flash, and the rapid catchup of Microsoft’s copycat, Silverlight:

I’ve said it before — one of my favorite things about the iPhone is no Flash. I will now add and no SilverlightPlugin.

As a web developer who uses Flash routinely, I’ve also come to enjoy its absence on the iPhone (and the absence of like technologies, and even prehistoric kin like animated GIFs), and the amazing increase that absence give to the information over noise ratio. It’s led me closer towards “Web 2.0″-style AJaX for interactivity, and away from the proprietary, and often overkill, that is plugin technology.

What do you think?

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Flash and Silverlight to Make MobileSafari Crashier?