We had time to get some more hands-on with the Intel Smartphone reference design here at MWC this morning. It feels powerful! Apart from an Intel-optimised build of Opera, Gameloft have also been porting over to the Intel platform. It’s worth noting that applications that don’t use any NDK, will run on the Intel Android platform without any modification. There’s an ARM-NDK emulation layer in there too so even some apps that do use ARM NDKs will work but for the best experience, ISVs are going to have to recompile their apps to use the Intel NDK where needed.

Don’t forget that the platform includes Wi-Di support and has some image processing hardware inside. Apart from that though, it’s difficult to see a clear advantage for Intel right now, especially if ISV can’t be bothered to port their NDK-reliant apps over.

We had time to get some more hands-on with the Intel Smartphone reference design here at MWC this morning. It feels powerful! Apart from an Intel-optimised build of Opera, Gameloft have also been porting over to the Intel platform. It’s worth noting that applications that don’t use any NDK, will run on the Intel Android platform without any modification. There’s an ARM-NDK emulation layer in there too so even some apps that do use ARM NDKs will work but for the best experience, ISVs are going to have to recompile their apps to use the Intel NDK where needed.

Don’t forget that the platform includes Wi-Di support and has some image processing hardware inside. Apart from that though, it’s difficult to see a clear advantage for Intel right now, especially if ISV can’t be bothered to port their NDK-reliant apps over.

Count me as one of the people who said “It’ll never happen inch when first hearing about Opera submitting it’s Opera Mini browser, designed for the iPhone, to the Apple App Store. Despite the fact that I really wanted Opera Mini to make it through, it just seemed like there was no way, based on Apple’s previous behavior, that this browser would make it though. There are “alternative inch browsers in the App Store, however they are really just reskined versions of Safari. Opera Mini, on the other hand, is using it’s own framework and I believe it’s own rendering engine, which is why it is particularly amazing that it’s been approved for release into the App Store. Additionally, it features Opera’s ‘Turbo’ technology to speed up page loading times by compressing the data on Opera’s servers before sending it to your phone. This feature significantly improves load times when using slower connections such as 3G or especially EDGE, rather than WiFi.

While I’d love to give you some usage impressions, Opera Mini is not working for me for some strange reason. I haven’t heard this yet reported elsewhere so I’m assuming it is an isolated case, but for the record, Opera Mini is not working on my iPhone 3GS or my iPad as of this writing it hangs on the launch page and never gets passed it. If you don’t have an iPhone yourself, or are having the same issue as me, the least I can offer you is this video of how Opera Mini works on the iPhone:

As for it not running for me… that’s ok because MobileCrunch has you covered and has already run speed tests comparing Opera Mini to Safari, and with this cursory glance, it would appear that Opera Mini is indeed faster. Now if I could just get it working…

Opera 10.5 has been knocking around in Beta for a while but from today it’s available as a fully released product and ‘The fastest browser on Earth.’

“Opera 10.50 is the fastest browser we have ever produced. Under the hood, we introduced a new JavaScript engine, Carakan, and a new graphics library, Vega. What that means to you: no more waiting around for a site to load. inch

Opera also have the ‘turbo’ feature which really helps if you’re on a low-speed connection, the user interface has been tidied up and there’s the usual widgets, Opera Unite (I’m not convinced of the value of that yet) and Opera Link, A Mozilla Weave-like syncronisation tool.

I’ve done some testing on the UMID BZ as you can see below and so far I’m quite impressed. I enabled drag-scrolling using the opera:config#Scroll%20Is%20Pan URL and tested the Javascript engine using SunSpider. I’ve recorded the result in a FriendFeed thread that I encourage you too contribute to.

• UMID BZ 1.2ghz Atom Z515,FF 3.6 – 4697.2ms
• UMID BZ 1.2ghz Atom Z515, Opera 10.5 2879ms

Naturally Javascript tests results are only a part of the picture but as we move to moving more and more AJAX applications online (Google Mail with Buzz and Contacts is a prime example) it becomes clear how much of an advantage it could be.

In a quick check on memory usage there didn’t appear to be any major difference between FF 3.6 and Opera 10.5 so all in all it looks like Opera 10.5 is a sensible choice and with the ‘Turbo’ features it makes a great choice for the mobile web.

Press release: Opera.

Update 18.: It’s Opera Mobile 5 Beta. I’m testing on an Omnia Pro right now. Fast, good features. No complaints yet! Have you tested it?

It’s a question that Opera is going to answer very soon. The next generation in mobile browsing. There are few clues from Opera as to what it could be but Will Park of Into Mobile has had a preview and he says that the headline will soon make sense. The puzzle is gradually being completed (the image is being completed) as time goes on at the Opera teaser site. Right now you can see the right-edge of a device being held in two hands. The ‘alt’ text for the image is ‘Opera Next.’

Is it going to be a new Opera Mini or Mobile product and what features would take it to the next level? Opera has already pushed the boundaries with their proxy, widget and sync features so what could be next? Touch friendly UI? Flash 9.5?

Support for more operating systems (Android has been promised) would be good but that’s hardly groundbreaking. How about location-enabled browsing? will the next Opera Mobile or Opera Mini app include the Geo API? Will Park says that there are clues in the teaser page and references ‘source code.’

Personally I think we’re looking at Opera Unite for Mobile based on what I read at GigaOM last week.

If Opera reveal one piece of the puzzle per day, we’re looking at a completed picture on Monday 28th September.

This post is based on some notes I made in 2008. Following the release of the Opera 10 ‘Turbo’ preview client and the announcement of Opera Mobile 9.7 with ‘Turbo’ (Proxy) option I thought it would make sense to publish the notes.

Opera 10 preview with ‘Turbo’ Option

Disadvantages of Proxy-based browsers

• Scalability. Size of server farm. Global distribution?
• Business model – Pay-for browser or will the operator ‘tweak’ advertising? Carrier controlled server farm? Free value-added service by carriers?
• Security. SSL terminates at proxy?
• Privacy. Data mining and sale of data. Police access to browsing records.
• High latency
• Accuracy can’t be guaranteed
• Single point of failure
• Net neutrality You lose geo targeted advertising and content.
• Geographic focused content (geo-restricted content could leak E.g. Hulu. Geo targeting fails)
• Plugins (in-line WMV, flash 10 etc)

Advantages of Proxy browsers

• Far more efficient bandwidth utilisation
• Reduced time to display full content (on lower bandwidths)
• Lower client processor requirement (battery life saving)
• Content reorganisation for the target screen.
• Easy to implements system-wide safe browsing controls. (Can also be regarded as a walled-garden and marked as a ‘disadvantage’)

Legal question. Are proxy services republishing content with modification? How can content owners be sure their content (including ads) is presented as they wanted it? Can they prevent proxy services from using their content?

List of proxy browsers.

• Opera Mini (java-based browser for most phones)
• Opera 10 ‘Turbo’ preview
• Skyfire (for mobile phones)
• BlackBerry Browser (option)

I’m a fan of both proxy and client-based browsers and as such, a browser like Opera 10 with the ‘Turbo’ option really interests me. It would save data when I’m roaming or on a limited data plan and would speed up the display of information when in low bandwidth or on low-cpu situations. For the smartphone or MIDs based on ARM, the Opera Mobile solution with ‘Turbo’ (option again) seems to be perfect too. I also like the idea of an intro-level unlimited browsing service that can be tacked on to a users cellphone account for little-to-no cost thus introducing people to the advantages of having the Internet in your pocket. As a content producer i’m a bit worried that my geo-targeting will suffer but if it introduces people to the idea of Internet on the go, I’m more than happy.

I love the community we have here.  Just 60 minutes after posting about Opera Mobile 9.7 and mentioning that it would be interesting to have a desktop version with Turbo, Hrundik drops a comment in to say “Opera Turbo preview for desktop is already available.”

And sure enough, there it is in Opera Labs for Windows, Mac and Linux.

ultra mobile PC users, this is something you have to have in your toolkit. Turbo Mode is going to save you bandwidth (if you’re on a restricted data plan) and speed up your browsing (if you’re on a slower connection.) I think it’s also going to reduce the CPU usage on rendering pages as the ‘Turbo’ servers do most of the work.

I’m off to do some testing. If you’ve already discovered Turbo-enabled Opera 10 preview, let us know how your testing went.

The Opera 9.6 SDK, released last year, included a little feature that a lot of people missed…

Also worth mentioning here is that Opera have announced the 9.6 SDK which supports some cool new stuff including the ability to use OpenGL accelerated zoom and pan and, here’s something unique, OBML support which allows the browser to display Opera compressed content just as is used on the Opera Mini browser. This is superb for travellers that want to cut their roaming data costs because it saves up to 90% of bandwidth and is fast in low-bandwidth scenarios. I’m looking forward to seeing this on a MID as it will be a great feature to have available. [Source]

Update:

Opera Turbo is NOT the same as OBML. Thanks to a few comments and few links and some research. It’s basically still HTML client-side rendering but using image compression, script delaying and flash blocking.
More info here: http://my.opera.com/desktopteam/blog/opera-turbo-labs-release?startidx=150

In Feb, Opera branded the function as ‘Opera Turbo’ [article] and finally, today, Opera have announced that Opera Mobile, that’s the version built for smartphone platforms, has reached version 9.7 and will include this ‘turbo’ technology making it, as far as I know, the first browser to be able to handle both client-side and proxy-based rendering.

Of course, this is perfect for mobile users as their bandwidth costs and availability can change rapidly so instead of having to switch to a different browser, you can turn on the ‘Turbo’ feature and carry on.

The announcement also highlights the use of the Presto 2.2 rendering engine and support for Flash.

There’s a demo video available on the Opera website.

Quite how long this will take to reach a phone is unknown as even version 9.5 is only available, in tailored format, on a handful of smartphones. 9.5 as a user download is still in Beta and there’s not even a sniff of a 9.6. We can only assume that this is an announcement for carriers and OEMs for the 2010 time frame.

I wonder if they’ll make a desktop version with this ‘turbo’ feature?

Opera announces the new Opera Mobile 9.7 at CTIA Wireless 2009 a server-accelerated full Web experience for smartphones and mobile devices.