No, they pay *me* to say that. They pay *you* to make it true.

The browser on the latest BlackBerrys (i.e. Storm and I think even Bold) are using WebKit (with a much improved experience, I might add).

You have a “rendering problem”!

Are you using WebKit? ;-(

A fair question. Turns out that what’s good for mobile is good for Chrome and Safari too! All of the optimizations in this version are applicable to desktop webkit-based browsers. If you know you’re going to be targeting Safari/AIR/Chrome, then this is also the version of dojo.js you might want to be using. If nothing else, it’ll boot up faster due to the reduced parse time.

Regards

Is there some tradeoff that means this would reduce performance/functionality for Chrome, Safari etc.? Or would any performance increase be effectively unmeasurable on a proper desktop machine?

Mobile is new territory. There is an early leader but it’s still all about standards support in the long run. If Opera Mini worked just like its big brother then I’d take it more seriously. That’s not too far away.

Dean: Opera Mini’s great, but you can’t really make it do interesting interactive stuff quite yet (although I admit I had to fall back to OM3 because OM4 doesn’t work right on my phone). I did ping the OM guys to say: is it possible to do iUI-style effects? Apparently all this sort of stuff is going to be possible in OM5, hopefully, which will probably bring OM5 up to par with mobile WebKit. That’s going to be a good day, then, because you can have smartphone-quality web browsing on any arbitrary phone. A pleasing day.

I’d like to see Fennec take off, but I suspect it’ll be a while before it gets close enough to be viable, and by then WebKit may have eaten its lunch entirely in the mobile world. I hope not; I like Fennec (the little amount I’ve played with it) and Mozilla-based browsers have always had the most advanced JS support.

That said, I’m happy to use Ajax for Opera mobile but not CSS-based animations. There is some kind of weird re-rendering for Opera that screws with your JS.

PS. Anyone who says that you can build a mobile site just by changing your style sheets is crazy.

In this experiment, I’ve taken the position that non-smartphone browsers will usually get the “degraded” page (i.e., no scripting). Even as they pick up better and better CSS, those browsers really do kind of trail browser progress by a generation or so. That kind of split makes a lot of sense to how I think about building apps and I think that if you say “there’s webkit and there’s everyone else”, you can do a relatively good job of delivering the right experience to each. It’s one of those places where “progressive enhancement” isn’t so much a mantra or design philosophy as it is a high-functioning coping mechanism for folks who won’t build a site twice…which is most of us.

Regards