«« Unexpected Exercise NextGen GUI Choices »»
blog header image
DHTML is a Rubber Band?

While I was away in Las Vegas, Joel Spolsky did what he does best -- stir the pot -- by writing about How Microsoft lost the API War. At the end of it he describes the problem: Microsoft is losing to web apps in DHTML. Even though he laments the progression to web apps, Joel writes a list of ways that DHTML could be improved and made more useful.

I agreee that DHTML isn't quite there yet but ironically that's one of its strong suits. The fact that in order to remain cross-browser compatible a developer has to use the lowest common denominator of DHTML (which itself is pretty basic) keeps UIs simple. This is why ordinary people prefer web apps like Hotmail to Outlook. They are just simpler.

The disadvantage of DHML is that developers don't realise this. They continue to hack on top of it, making browser-specific apps and JavaScript tricks. Is this OK for intranets? Maybe. The next update of IE could break your app though, and those updates are usually out of your control as a developer. Then you get blamed when the hacks break and you have to figure the problems out and fix them. Is this OK for Internet sites? Definitely not.

An example of stretching DHTML is Google's GMail, which doesn't work in Safari. While it's an impressive web app, it seems overcomplicated to me. There are a lot of eye candyisms and a lot of non-web app features. Ordinary people familiar with web apps will have to take more time to get used to GMail's non familiar features because it's not simple DHTML any more.

GMail has crossed into the grey area between web apps and standard apps. Is this a good thing? I think it's a good gamble on their part. If an established webmail provider like Hotmail tried to make this change, people would bitch. With a brand new service comes a brand new way of doing things. People will look at GMail and say "gee, I didn't know this was possible with web apps". Good or bad, this is the direction it looks like we're heading in.

Posted at June 24, 2004 at 04:47 AM EST
Last updated June 24, 2004 at 04:47 AM EST
Comments

For your example: I don't know if you should judge a piece of sw that's still in beta... And what version of Safari do you have? On the GMail account it says they support "... Safari 1.2.1 and newer (Macintosh)"

http://gmail.google.com/gmail/help/about.html#sys

» Posted by: Jim at June 24, 2004 08:59 AM

Hey, good to know. Safari support must be pretty new.

As for judging beta software feature-wise, I think it's fair. Features don't change between beta and final, just bugs are fixed.

» Posted by: Ryan at June 24, 2004 11:05 AM

I have to disagree with that. I would expect features to change from a Beta to a Final release. Especially in a wide beta like Gmail.

(Note that by saying feature changes, I'm talking about already implemented features, not adding in new features)

Beta's are done in order to shake the system down, and also to get feedback from actual users. If alot of people hate the way that a particular part of the app behaves, then you'd be stupid not to make use of that feedback before releasing.

» Posted by: peter bernier at June 24, 2004 12:41 PM

It depends on the size of the feature. Most of the time a product is "feature complete" at beta and changing features could increase the possibility of introducing regressions (bugs). Then you have to beta all over again.

Betas aren't released to critique *how* a product works, it's too late at this point. Betas are just to make sure that the product isn't broken.

Now in GMail's case, it's a server app. They can make updates without having to worry about deployment -- the next time the user goes to the site, the changes are there.

They've probably had multiple beta versions, AKA release candidates (RC) all under the moniker "beta". They don't need to worry about releasing a single beta program, so they have more of a chance to incorporate feedback.

However over the last month or so of using GMail I haven't noticed any changes.

» Posted by: Ryan at June 24, 2004 06:52 PM
Google
 
Search scope: Web ryanlowe.ca