I came across a situation recently where a JavaScript widget didn’t ‘work’ on the iPhone. It did technically work, but without knowing about two-fingered scrolling (and when you need to use it), it didn’t appear to work. So how do you differentiate the iPhone (and other touch based devices) from a regular browser?

I’ve just gotten back from a great day at the Stackoverflow Dev Day, I didn’t take my usual copious notes, but I thought a flavour of proceedings would be good to get down. For those who don’t know me, I have to add the caveat that I’m not a…

The new iPod nanos (4th generation) now have speech-enabled menus, so you don’t have to be able to see the screen to operate it. This is obviously a boon for the visualy impaired, but with my old iPod I quite often used it from my pocket, or whilst driving. Could…

I’m not sure whether to put this down to an issue with my (mobile) ISP, or whether it should count against using XHTML sent as application/xhtml+xml? I’ve recently found that even a well authored site using valid XHTML can display as an XML error in browsers that support XML mime types.

I’ve recently moved to using GMail as my primary interface, and I noticed a new mobile feature. The mobile access for GMail is much better than the one I installed on my hosting, which frankly was unusable on my phone despite an excellent mobile browser. Then I tried the Symbian GMail client.

Mobile browsing has been, frankly, rubbish so far. But now there are two new mobile browsers that confound the generally dire opinion of mobile browsers.