Opera Mini 2.0
Just as I was getting thoroughly sick of the whole X-2.0 trend along comes a product I can really get excited about. Opera Mini 2.0 is a truly lovely piece of software. It’s a free web browser for your phone, accompanied by a free proxy:
When surfing with Opera Mini, Web pages are optimized and compressed before being sent to your phone. This means that even though your mobile provider may charge you for the data which is transferred to your phone, the amount of data transferred is significantly less than it would normally be, making mobile surfing cheaper.
Most UK mobile data plans are pretty extortionate. I was quoted over £500 a month for an unlimited plan recently; compare that to Leonard Lin who pays $15 a month in the US. Having a compressing proxy is essential.
In stark contrast to the desktop edition the user interface is beautifully simple, relying mostly on the joypad to navigate with a full-screen editor for entering URLs and filling in forms. Opera’s small screen rendering technology is used to linearise the page content while keeping background colours and images intact.
The one feature I’d love to see added is a “reload page with images” menu option. I generally browse with images turned off, and viewing a page with its images requires me to navigate to the settings screen, toggle images on, reload the page and then remember to turn images back off again afterwards.
Opera Mini doesn’t appear to support JavaScript, but despite that nearly all the sites I’ve visited have been perfectly usable. Even Gmail works, thanks to an automatic fallback to their plain-old-HTML interface. With any luck it will become part of the accepted accessibility benchmark—I know I’ll be testing sites with it in the future.
Brian Sweeting - 11th May 2006 22:47 - #
Openwave has had compressing proxy technology since the HDML browser. I used it for a pager language I developed called SAL when I was working with two way pager manufacturers around ten years ago. It's a good way to go, just not new.
Tanny O'Haley - 12th May 2006 04:55 - #
Dan Webb - 12th May 2006 08:36 - #
What's so complicated about the UI in the desktop version? It has one more button than Firefox, while Firefox has one more top level menu than Opera.
Have you tried Opera 8.5?
Usah - 12th May 2006 09:57 - #
Simon Willison - 12th May 2006 13:18 - #
Chris Hester - 12th May 2006 13:30 - #
Will Macdonald - 12th May 2006 15:59 - #
Mathieu 'P01' HENRI - 13th May 2006 18:01 - #
Simon, check out this page with Opera Mini 2.0:
http://ilyabirman.ru/misc/bgjs/
The "Click here" link does the following:
onclick="document.getElementsByTagName ('body')[0].style.background='#f00'; return false;"Notice that it actually does work, but after some "Processing...", so it looks like Opera Mini processes JavaScript on server.
P.S. For what reason on Earth "New lines are not converted to breaks"?
Ilya Birman - 15th May 2006 13:35 - #
Ryan Parman - 15th May 2006 22:00 - #
Peter Bengtsson - 16th May 2006 01:11 - #
Tom Hentsch - 16th May 2006 12:49 - #
Nina Krause - 16th May 2006 23:21 - #
Paul Browne - Technology in Plain English - 25th May 2006 14:59 - #
Dustin Diaz - 27th May 2006 05:24 - #
Ray taylor - 27th May 2006 11:24 - #
I love Opera mini!
I had problems with the old version on my Nokia 6060 so I was really glad when they released Opera mini 2.0! I just downloaded the new version and Opera worked again.
Sadly it caused me to loose all my bookmarks, but I survived. :P
Daniel Aleksandersen - 8th June 2006 14:10 - #
"Openwave has had compressing proxy technology since the HDML browser."
I am not an expert on Openwave, so please exuse me if I am wrong. But I think that the difference is that Opera Mini actually renders the page on the server, then sends the rendering information to Opera Mini. Openwave actually renders the page on the device, using the compressed source (or WML converted source?) sent by the proxy. Meaning that Openwave needs more phone power.
"How good is Opera Mini at dealing with Web 2.0 and Ajax enabled sites?"
"it looks like Opera Mini processes JavaScript on server."
Exactly right. The Opera Mini server runs the scripts, and passes the resulting page to the phone client. To run scripts after the page has loaded, the user has to do something like clicking a link or using a form input. If the page uses JavaScript events like these, then the client passes the event back to the server, and the server processes the script.
What this means is that scripts that rely on links or forms (etc) to activate them usually work just fine, but AJAX (which requires ongoing script processing) will not work. DHTML is of course limited (due to the lack of CSS positioning and related styling), but the DOM engine itself is as capable as the underlying Opera engine. Even things like stylesheet switchers can work. If you want AJAX, you will need Opera Mobile.
"Does it pass the Acid Test?"
Opera mini uses Small Screen Rendering to reformat the page. After all, it has to work on screens as small as 100px wide. The Acid 2 test is not designed to work on small screens (you need VGA to see it properly). Even if it was, the Small Screen Rendering would reformat it. So no, it cannot pass the Acid 2 test, even though the underlying engine may or may not be capable of passing.
TarquinWJ - 10th June 2006 14:20 - #
Edward Ho - 15th June 2006 00:12 - #
"Takes up more screen real estate than the built-in Blazer browser"
Press asterisk (*) on your phone, that will switch between different interface modes, including fullscreen.
- yyitzhq - 21st June 2006 18:12 - #
RaMu - 18th September 2006 10:33 - #
Alastair dunn - 1st October 2006 07:47 - #
rade - 10th November 2006 11:52 - #