[This is the second in a series of 3 articles. See previous article here.]
After more than 6 hours of learning, playing and testing on various devices, I’ve come to a decision about Opera 9.5. Beta. It’s technically a great browser with a very good user interface. Unfortunately though, there’s a core problem out there that’s out of Opera’s hands. Hardware. Opera does a good job but limited processing power and small screen sizes and resolutions hold it back from presenting a full Internet experience.
In this review (video below) I’ll be looking at Opera Mobile 9.5 Beta on the iPaq 214 (see previous article for information on the iPaq 214) from a mobile computing perspective. I’ll be comparing the browser to what I’ve seen on MIDs and on Ultra Mobile PCs. In effect, I’m comparing it to the desktop. Not fair you say? I think it is. Mobile devices are now capable of running desktop software and full desktop browsers at impressive speeds. For many, the slower, although cheaper, mobile Internet experience offered by many consumer devices is probably good enough but if you rely on your browser for more than just browsing, you’ll want the fastest and most accurate mobile browsing platform you can find. In the near future, consumers are going to be more demanding of their mobile browsers too. Unfortunately, as I write this, there are very few Windows Mobile devices out there that have the screen-size and processing throughput, from network to rendering, that are able to offer users the chance to experience modern web pages, AJAX applications and to come anywhere near to a desktop-standard browsing speed. Opera 9.5 doesn’t appear to be any more efficient than it’s predecessor either. It has some other issues too issues which i’ll highlight here but please note that this is Beta software. While we are unlikely to see any more features (apart from the ones listed as disabled in the beta here), there could still be bug fixes and optimizations to sort out.
