One thing that pissed me off about the old (well, 2 years or so is a long time in internet-time) ways of internet development was browser dependency. Now, I’ve always been an untiring web standards advocate, so now that developing new websites using web standards is pretty much the norm and browser developers are realizing that they need to comply, we’re walking towards another era of browser dependency. And it’s making me sick.
Ajax (yes, he’s talking about ajax again). People are using it everywhere, as I predicted some time ago. The problem is, most new developers don’t realize they’re limiting their audience to a small share of web users. Let’s take as an example pretty much all Ajax-based new age Web 2.0 applications. Limited to no safari/opera support, no IE support under 6.0, and sometimes it only works on Firefox (period).
Now, I do use Firefox as my primary browser so I don’t get to complain as often as some people, but there are times when I use Safari because I like the speed; or, heck, I even test some sites on IE sometimes. And it pisses me off that most Ajax-based web-apps cease working: and that’s not the worst part. The worst part is that developers don’t seem to give a damn. As a developer myself, this leaves me flabbergasted. Get a new pair of eyes, people.
I’ve said this before, but I guess I’ll have to say it again. Ajax isn’t the be-all end-all of web applications. From a Usability standpoint, ajax is beneficial because it reduces page refreshes to get to a piece of information but there’s a couple of things that most new developers need to realize:
- Ajax creates several problems that limit usability and decrease user satisfaction. Most of the times, the responsiveness trade-off isn’t worth the use of Ajax in the first place.
- Second, if developers want to use Ajax to reduce page refreshes, they should first consider the possibility of revising their navigation flow: most of the times the problem they’re trying to solve is only a matter of more proper consideration of navigation (and ways to actually see content).
I don’t even know why I’m talking about information architecture and usability, though, because fact of the matter is, most companies are using Ajax for the sake of using Ajax. Because it’s a buzzword and everybody seems to care. You just need to say something is ajax powered in order to get everybody’s attention. The rule should be to use ajax, meaningfully. Where it actually has a purpose, and where it actually helps the user.
Update: Kevin Hale in the comments points out to an article he and his gang over at the great Particletree set up about degradable Ajax. A must-read if you’re deploying Ajax-powered applications and want to make sure you satisfy all your userbase. Read the article here.