1. it's very responsive. Much snappier than Safari; the difference is very noticeable.
2. pages download much quicker
3. zooming in and out is faster, but you only have two zoom levels. If you "pinch to zoom" it immediately zooms in all the way.
4. the home screen with 9 favorites works great
5. it's a little buggy (clicks don't always register)
6. killer feature #1: it automatically stores the entire app state, so you can open a few tabs, switch apps, go back and have everything the way you left it. This is a big deal, because Safari forgets your pages eventually, which is so frustrating when you have your travel plans in a safari tab and 3G is not exactly reliable.
7. killer feature #2: you can save pages
8. In full screen mode it makes for a pretty decent reader.
9. It doesn't suffer from "too small font" syndrome.
10. It has this "Snap to column" thing where your view automatically snaps to the column edges. This makes reading more like reading on Instapaper and less like safari.
11. It loads instantly, even when I have 3 tabs open. It's really that fast.
The only real downsides I know of so far are that it has trouble rendering more complex web pages, invades my privacy and doesn't do Javascript. Flash content simply doesn't appear (so you don't even know it should be there) and YouTube links don't link to the YouTube app. Still very impressive.
Maybe I'm overly accustomed to the "feel" of Apple's native apps, since there's just something about the app that just doesn't "feel" good to use.
The zooming-in and out is a big downside, as I often tweak in or out from what Safari gives me as a default when I double-tap.
The scrolling deceleration brakes to a halt sooner than native apps. Again, maybe I'm just being fickle, but if the physics don't match the native feel, then it just doesn't feel right.
Don't understand why they created their own form of copy/paste.
The zoomed-out small fonts are completely illegible. I can't even make out header or subheader text, or titles of articles.
Startup time, at least for me, was about 3 seconds, compared to immediately for Safari. I just have the 3G, and I'm sure it would be much faster on the 3Gs.
When going from vertical to horizontal view, the page does not resize. I have to reload the page for it to fit to the full width.
Despite the innovations that I was very excited for, it's the little things, the details, that will keep me from using this app. To me, good execution is in the details. Some of the things above, for me, are simply musts. An example would be a car that must feel good to sit in, have sharp steering control, easy-to-reach controls and a solid-feeling gearbox. Extra-cool features without this are non-starters. These are the things Safari gives me which Opera lacks.
If you double-tap in Safari on iPhone, it will snap to columns which is useful when you want to read an article on a site and avoid the sidebar ads and navigation.
Shake to undo always prompts for confirmation to undo the last action. Touching the top of the screen to scroll to the top of the page does not ask for confirmation, which is a pain when you are 3/4 of the way through a very long article.
Thus, being able to shake to undo the action of auto-scrolling to top of the screen would be a nice solution.
Agree with much of what you've said. I think opera have nailed the tab switching UI, its so much quicker to use then safari.
Couple of things I dont like
- They've implemented their own copy/paste controls. I guess this is nessesary due to the 'long click' for opening new tabs etc, but its kind of annoying.
- Not really Opera's fault but because of the new useragent, alot of sites deliver the 'normal' mobile version of their site instead of the iphone version I'm used to (usually much prettier).
For me, Opera seemed to forget tab contents after opening just 2-3 of them. It also displays a "please refresh" message instead of automatically reloading the contents.
I've also seen a bug where all the tabs turn to grey, inactive rectangles. You have to kill the app and lose all your tabs.
For an app where one of the main selling points is to cut down on the number of bytes sent, not auto reloading pages should be seen as a feature. If I need the page reloaded I can do so when I need it, and if I don't then doing so is just a waste.
I look at this as kind of amusing; my previous phone could only run Opera Mini, and the prospect of having a real web browser was one of the things which drove me to the iPhone. Mobile Safari's UI and its actual support for decently rendering pages (coupled with the privacy concerns Opera Mini's proxy system naturally raises) are so far ahead that I'm a bit surprised anyone would actually choose to use Opera Mini -- it's like I've stumbled into a bizarre parallel world where people are clamoring for the right to install and use IE6 as a replacement for Firefox or Chrome.
In my few hours of use so far Opera Mini is the clear winner in terms of page load time, caching, and battery life. This is on a 3G. I have no good answers on the privacy side.
Well put. Well people started making a fuss about Opera Mini getting approved I couldn't understand why. Safari on the iPhone is the best mobile browser out there in terms of both specification conformance and performance.
Because there is a percentage of people heating long waits... Safari is very nice but not responsive enough, and sometimes if you want just to read a news site, the user experience is just the same. Also I think that EDGE users will enjoy the fact that finally it's possible to have decent loading times of web pages.
I live in a city covered by 3G but when I from in my home town it's almost impossible to suft the web with Safari, while it was ok with Opera Mini on a Nokia N70 phone.
Opera Mini is surely not a drop in replacement for Safari Mobile, but it surely is a useful tool, much more useful than most of the other top-downloads in the Appstore.
I hardly ever use my mobile browser, so I can't speak much for which one's better - but if nothing else, I think it's good that there's now more selection and variety available.
Does anyone know how Opera makes money from this version? Surely the bandwidth and computational costs of processing, compressing and sending out webpages would exceed revenue from Google search, right?
Opera does not store any users’ private information. Opera generates statistics of the usage of Opera Mini, but these are aggregated numbers and no information can be linked to a single user.
For now: "un-zommed" content is unreadable, for instance, nytimes.com in Opera http://cl.ly/JIP vs Safari Mobile: http://cl.ly/J9i (which is also unreadable, but well, I can distinct letters)
This is a major problem. Without even being able to read the article titles, there is literally nothing you can scan to decide where you want to look, what you want to click, or even just what you want to zoom in on. I can make out the Sheraton logo though? Maybe Opera takes a cut of banner ad clicks and wants those to be the only things we can read without zooming in?
Does the Opera browser app itself not interpret javascript? Is it offloaded to the iPhone's WebKit/rendering engine? Otherwise this would seem to fly in the face of the recent change to 3.3.1.
Think of Opera Mini as an interactive image viewer. They interpret all JavaScript on the server side and sent result back to the client using OBML[1]. Or at least that's how it works on other device.
Interesting. The section on JavaScript support is not encouraging actually. Can anyone report on attempting to use a js-heavy web-app through Opera Mini, e.g. Gmail?
It's not great at AJAX. My brother has a Blackberry and mainly uses Opera, and the fact that Sporcle(.com) worked on my iPhone shocked him. Apparently Opera can't do onchange.
Gmail just gives the normal HTML mobile version, like it did in the bad old days before iPhone.
From my experience with Opera Mini in Windows Mobile (since it's still not available in App Store), Gmail just fallback to the Basic HTML mode. It's safe to assume most JavaScript-heavy web apps won't going to work at all.
The app is Opera Mini, not Opera Mobile, so no, it does not. Opera Mini is a proxy browser: all the heavy lifting, including JavaScript and most rendering, happens on one of Opera's proxy servers. The Opera Mini app receives a heavily pre-processed and compressed version of the webpage, in some custom data format. The app itself only does rendering, not processing or interpreting.
No, the Opera app does not run JavaScript itself. The app communicates to Opera's server, and it's the server that does HTTP with the website, runs the JavaScript, and compresses the HTML and sends it down to the app.
The restriction on downloading and executing code has been in the developer agreement since the beginning. It's not a recent thing.
I have to agree with most posters here. It's a nice start and I think it's a very good thing there's now a competing browser engine in the App Store. It has quite a few non-native feeling elements to it, so if they iron out the kinks and give it a bit more of an iPhone feel it'll be a good contender.
The usual Opera instant back function (no reloading of pages on clicking the back button) is killer!
It's amazing how I'm happy to trade features for speed. Also the UI is so much... like Fast Tracker :) That 2D interface that is clearly primitive but reacts like a videogame, instantaneously.
Saving pages and fast access to favorites is also very cool, but speed is the real killer feature here IMHO.
Downloaded it for the Find in Page feature and uninstalled pretty much immediately - I thought it would be serious competition for my Find In Page plugin for Safari and finally deliver this functionality in a native way.
Instead, over 60% of the screen is permanently covered by the toolbar at the top and the keypad at the bottom. No way to scroll either while in the Find in Page mode. No way to step backwards throught search results either - next button only. What were you guys thinking?! Find in Page could have been a killer feature for you over Safari, and it falls way short.
In addition, the app does not feel Cocoa Touch-like - UI elements look faked and the feel is different. Sorry, I had much higher expectations for days waiting for the release, and it just did not deliver iPhone-like experience. Better luck in the next version, I guess. BTW, love Opera on the desktop!
PS: almost forgot - PDF is not supported at all and is delegated to Safari instead!
That's the overruling statement right there for most of this App store shenanigans.., if something sucks people won't use it, and it won't be a threat.
The app is still somewhat crippled though, all links from other Apps can only be opened in Safari. So, not the same as switching a browser on your desktop or laptop. Nonetheless it seems like a step in the right direction.
I'm not sure it's surprising, I suspect Opera-mini's nature of preprocessing and compression might have helped it get approved because of the bandwidth saving promise for AT&T.
Scrolling requires repeated swipes. Links and buttons require multiple taps to activate, and some cannot be activate at all.
(stay signed in checkbox on myOpenID). Initial zoom levep is useless with unreadable text. Zoomed in level feels too zoomed in without ability to adjust.
But worst of all, the text area editor is custom--no autocorrection. This comment has takem far too long to edit.
In short, a really poorly executed app that should not have been approved, save for the crapstorm banning it would have caused.
The iPad + OS 4.0 backed up the approval process. We submitted before Opera, took about 14 days. Previously it's been about 5-7 days for new apps as Apple has been making a lot of improvements.
I'd garner that approvals for an application are drastically different then government approvals. At least stringent government requirements are there for a reason.
Not everybody has great broadband mobile connections.
Android has a very good browser with WiFi, but it is totally useless with my Edge connection. Opera on the other hand is amazingly fast with any connection I have tested.
Opera complements Safari in a sense. It's an app to browse with on the ancient networks with bad reception. Chrome might conflict too much with MobileSafari's core functionality, so it would really be a miracle if it was approved.
+ Does Google even want to compete there? Chrome on the desktop may have some strategic value beyond spreading the Google brand, but is there anything exceptional made 'the Google way' in the Android browser?
Unlikely. Opera Mini works by doing all the rendering on the server-side, and then sending the pre-rendered website to the client. It's not actually a browser, so much as an app that gets screenshots from a server-side browser.
Firefox, on the other hand, would be a real browser, running Javascript rendering and Gecko on the phone itself, which would not be allowed.
That said, I don't understand why anyone would want Firefox anyway. The iPhone's limited memory and CPU would likely make Firefox nearly unusable, while extensions would eat away at what little free space was left. Firefox isn't optimized for the mobile space, and I can't think of any features it would provide that would make it a better choice than Safari (or, on Android, the built-in WebKit browser).
The connection is only encrypted between the web site and Opera's servers, and Opera's servers and your phone. Opera's servers see all the data in its unencrypted form. From their FAQ[1]:
Is there any end-to-end security between my handset and — for example — paypal.com or my bank?
No. If you need full end-to-end encryption, you should use a full Web browser such as Opera Mobile.
Opera Mini uses a transcoder server to translate HTML/CSS/JavaScript into a more compact format. It will also shrink any images to fit the screen of your handset. This translation step makes Opera Mini fast, small, and also very cheap to use. To be able to do this translation, the Opera Mini server needs to have access to the unencrypted version of the Web page. Therefore no end-to-end encryption between the client and the remote Web server is possible.
Put it this way: they don't care about what the developers have to say about their platform or their policies and they assume that whatever minority of developers has left their platform will be replaced by an army of new ones. I mean, how many people have actually dropped their development for the iPhone/iPad? Have you noticed it?
out of my friends (who develop for the iPhone)? One or two.
Most are still staying onboard (maybe... 25 or so).
Don't forget this is the internet; like most things the disgruntled developers will be the most vocal. That doesn't necessarily make them a majority - or even a large minority.
1. it's very responsive. Much snappier than Safari; the difference is very noticeable.
2. pages download much quicker
3. zooming in and out is faster, but you only have two zoom levels. If you "pinch to zoom" it immediately zooms in all the way.
4. the home screen with 9 favorites works great
5. it's a little buggy (clicks don't always register)
6. killer feature #1: it automatically stores the entire app state, so you can open a few tabs, switch apps, go back and have everything the way you left it. This is a big deal, because Safari forgets your pages eventually, which is so frustrating when you have your travel plans in a safari tab and 3G is not exactly reliable.
7. killer feature #2: you can save pages
8. In full screen mode it makes for a pretty decent reader.
9. It doesn't suffer from "too small font" syndrome.
10. It has this "Snap to column" thing where your view automatically snaps to the column edges. This makes reading more like reading on Instapaper and less like safari.
11. It loads instantly, even when I have 3 tabs open. It's really that fast.
The only real downsides I know of so far are that it has trouble rendering more complex web pages, invades my privacy and doesn't do Javascript. Flash content simply doesn't appear (so you don't even know it should be there) and YouTube links don't link to the YouTube app. Still very impressive.