That's really too bad. I guess to be on the safe side I'm going to have to start interpreting everything else that comes out of his mouth as pure horseshit from here on out.
Sure the Safari engine is a great piece of technology. I've seen what it's done for the S60 browsing experience. But developers knew even before the iPhone was announced that you'd be able to browse to your GMail account from it. This announcement isn't some opening up to third parties: it's a definitive closing. No access to any device features except for dialing the phone (something you've been able to do from some of the first mobile phone browsers ever developed). Not the camera, not the microphone, not the accelerometer, not the proximity detection, not the multitouch events, really not the touchscreen at all except as mediated by HTML events. So basically no direct access to any form of user input. Not much output, either, unless you're posting character data to a server: no Bluetooth radio transmissions, no display or sharing of captured video, images or sounds, no 3D or even 2D graphics APIs. I guess we could play AJAX Sudoku games created with HTML table tags.
Oh yeah, and no access to local data stores. Of any kind. All your data has to be loaded down from a server over a slow EDGE network every time you want to access it. Hopefully that won't be while you're inside a large office building or riding the subway.
It's not just that users want more from their mobiles than web applications. It's that people want their mobile applications to "just work," not to work dependant on the presence of a service that the carriers themselves consider to be "best effort" in quality.
Posted by cervezas at 20:03:15. Filed under: Mobile Web
Comments
Add Comment