Right on cue, just after the aptly-timed teaser poster, Motorola signs on just the right dotted lines to make its i1 push-to-talk Android handset official. Let’s run through the specs quickly, shall we? A 3.1-inch HVGA (320 x 480) touchscreen, 5 megapixel camera with LED flash and 4x zoom, WiFi, and microSD expansion — no mention of the processor, so we’ll have to find out on our own later. The OS version is 1.5 and, while there’s oddly not a single mention in either the press release of fact sheet, given the official images and unofficial leaks, it’s definitely got Motoblur. The browser of choice is Opera Mini 5 with support for Flash 8, and if you’re worried about Mother Nature’s wrath, the i1 meets Military 810F standards for handling averse weather conditions. iDEN lovers can pick up the call sometime this summer on Sprint, with price yet to be named.
Update: Motorola’s just sent word that the i1 does not have Motoblur, despite the presence of the traditional green call / blue contacts buttons. That begs the question, then, of what exactly defines Motoblur here (is just the Happenings widget missing?), and what Android skin is on the i1 — the press images here are definitely not showing vanilla 1.5. We’re still awaiting a response to that, stay tuned.
Opera’s Mini 5 beta finally hit Android in the wee hours of this morning and, while writing about what it looks like is nice, we thought a little walk-through to demonstrate the impressive speed of the thing was worthwhile. So we have a short video for you below, with a comparison against the stock Android browser, plus some impressions of just how it is to use. So, click on through, won’t you?
Though its pure Java and BlackBerry counterparts had gone live late last year, Opera’s Android version of the Opera Mini 5 beta has been missing in action — until now. As far as we can tell, the new cut is a dead ringer for its cousins on other platforms, bringing all of 5′s new features including the so-called “speed dial” bookmark browser, tabbing, and an integrated password manager. We’ve had just a little bit of time to check it out so far, and our initial impression is that it’s wicked fast and renders just like you’d expect Opera Mini to, but the downside — and this is a big one for Android users on newer devices — is that it doesn’t appear to support multitouch. The new version is available for download today.
We’ve been slipped some additional information on Motorola’s imminent Android-powered i1 for iDEN networks today — actually, one correction and one interesting note. First, the correction: we’re now being told (by the same tipster as before) that it’s actually got a 5 megapixel camera on board, a nice upgrade from the 3 we’d previously been told to expect. More interestingly, though, we’re also hearing that Opera Mini has been tapped as the i1′s default browser — a move that Moto is more than welcome to make since this is a Blur-powered, non-”Google Experience” device. It’s also a possible admission that third-party Android browsers are currently outperforming Google’s own, something Microsoft has long dealt with on Windows Mobile as companies like HTC ultimately ended up bundling Opera Mobile with virtually every model they sold. So, Sprint Direct Connect and Boost Mobile customers, you getting excited about this thing or what?
Got WinMo? Don’t have a Java VM? No problem! Opera has taken the time to rewrite its Opera Mini 5 beta as a native Windows Mobile application compatible with both 5 and 6.x-based handsets, meaning you won’t need the Java compatibility that’s traditionally required to run it — compatibility that ironically makes it one of the more widely-deployed mobile browsers in the world. Though the thicker, fuller-featured Opera Mobile product is already a stalwart on WinMo that HTC bundles with the better portion of its devices, the presumed advantage with Mini is that it’s tighter, faster, and consumes considerably less data — perfect when roaming or on a low-allowance plan. Heck, why not have both? The Mini beta download is available now.
We came, we saw, and we’re still scratching our heads over what Opera is up to with its Mobile World Congress demonstration of its Opera Mini browser running on the iPhone 3GS. But before we get into that, let’s talk performance: it’s fast. Opera Mini is very, very fast on the iPhone. Loading the New York Times, for example, was about 5x faster than loading the same page in the iPhone 3GS’ stock browser. Pages loaded smoothly and were interactive just as quickly as the content began to load — not unlike the Safari browsing experience. From a functionality standpoint, Opera Mini operates exactly as it does on other, less-contentious platforms. So while double-tap to zoom is supported, pinch-to-zoom is not. The iPhone version does, however, remember the state of the browser when you exit Opera Mini. As such, you’ll find your tabs and recent pages right where they were when you last used the app.
The impressive performance gain has to do with how Opera Mini works. First, it’s not doing any rendering of the pages or code processing locally. Web pages are processed by Opera’s servers before sending just the results to the iPhone. Not only does this speed up the local processing but it also limits the amount of data sent — a potential big money saver for people browsing while data roaming (like us in Barcelona) or for those without unlimited data plans.
Unfortunately, Opera refused to let us or anyone photograph the app or take any video of it in action. We couldn’t even photograph the Opera icon in the launch bar or the wallpaper adorned with the Opera logo. Why? It looks just like Opera Mini beta on any other device so it’s not like we’re exposing any competitive intelligence. And it’s not like Opera would be violating any Apple NDA related to the SDK or the app approval process. Unfortunately, Opera was unable to give us a valid reason other than, “you just can’t.”
So why is Opera making such a fuss about this before it has even submitted to Apple for approval? We have three theories that we discussed with Igor Netto, Senior Product Manager within Opera’s Mobile group. Click through if you like conspiracies.
Here’s a guaranteed way to drum up support for an upcoming press event: claim the impossible. Opera just announced a press and partner preview of its Opera Mini browser for the iPhone at Mobile World Congress. You read that right — for the iPhone. Of course, the real intent of this stunt is to draw our incredulous attention to Opera’s Mobile and Mini browsers running on platforms where the software is actually released like Symbian, Windows Mobile, and Android. Besides, as good as the Mini browser is, it, like Mobile Safari, doesn’t support Flash. And since Apple isn’t likely to approve any browser that duplicates functionality it already provides, really, what’s the point of all this? A Cydia store release?
We came, we saw, and we’re still scratching our heads over what Opera is up to with its Mobile World Congress demonstration of its Opera Mini browser running on the iPhone 3GS. But before we get into that, let’s talk performance: it’s fast. Opera Mini is very, very fast on the iPhone. Loading the New York Times, for example, was about 5x faster than loading the same page in the iPhone 3GS’ stock browser. Pages loaded smoothly and were interactive just as quickly as the content began to load — not unlike the Safari browsing experience. From a functionality standpoint, Opera Mini operates exactly as it does on other, less-contentious platforms. So while double-tap to zoom is supported, pinch-to-zoom is not. The iPhone version does, however, remember the state of the browser when you exit Opera Mini. As such, you’ll find your tabs and recent pages right where they were when you last used the app. 