Mobile: should we treat mobile clients different than regular “wired” webbrowser clients? Yes.
When you use a webbrowser you’re used to waiting a bit and submitting a form and waiting for the response and so. And the connectivity might be down for a while. The behaviour is synchronous. One action after the other.
On a mobile phone, you’re used to native apps and everything just works. So a web application “feels” different. The behaviour is asynchronous. You just send a tweet and it’ll submit itself in the background while you continue working.
At the end there was some discussion about mobile web apps versus native apps. A big problem with native apps is the fragmentation. Iphone is fine with just 3 models or so. But for android, to get the best experience, you basically need to take into account 800-1000 different models. That’s the best thing about mobile web apps: a decent html5+css3 web app generally works fine in most recent mobile phones’ web browsers. And you don’t have to go through the apple store…
My name is Reinout van Rees and I work a lot with Python (programming language) and Django (website framework). I live in The Netherlands and I'm happily married to Annie van Rees-Kooiman.
Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):