Opera 14 for Android Is Out!
Yay, and — dare I say it — w00t! Opera 14 for Android is released!
Opera 14 for Android is built on top of Chromium 26, with a total overhaul of the UI in native code, making it fit well with the latest Android design guidelines. Go get the build from Google Play or point your browser to m.opera.com, and give it a spin!
A great browser for Android 2.3 and up
Currently, we support Android 2.3 and higher. That’s important, as 38.5% of Android users are still on Gingerbread — now they can get top of the range features and performance, just like users on newer Android versions!
Note that we don’t have an Opera 14 build ready for tablets yet: we’re still working on various tablet-specific UI optimizations, and this will be released later on.
A whole new engine
Opera 14 is based on Chromium 26, which does not include Blink just yet. However, as we plan to stay closely in sync with the Chromium development cycle, doing frequent updates, you can expect it in a future release. In the meantime, we’ve added/enabled some extra standardsy goodness already for you to use:
<input type=color>support: try it with this simple demo
- WebGL 3D context is enabled: you can try out our Odin demo, for instance, or why not try building something with WebGL yourself?
@supports, which allow you to do simple feature detection using CSS.
We’ve also done something cool with how we handle HTML5 audio: if you start playing e.g. this excellent song on SoundCloud, you’ll see that a pause button appears in the Android notification area. You can now switch tabs, or even open other apps while the song is playing, and easily control playback from the notification area.
Note: some things we don’t support in this first release include custom search providers and access to about://flags.
We’ve also adjusted our UA string, so as to avoid old sniffing traps: it’s similar in format to the Chrome UA string, with, for this release, OPR/14.0.1074.57453 appended at the end. Of course, you shouldn’t be looking at this at all, and instead do feature detection, so forget we mentioned it.
New UI and features
When opening Opera for Android, you’re greeted by our overhauled Speed Dial, which now combines favorite sites with bookmarks into one view. You can group bookmarks in one level-deep sets by dragging and dropping them on top of each other. A swipe away to the left (rather than hidden away in a submenu somewhere), you find your browsing History, and towards the right, there is our new Discover page, which helps you find interesting online content to jump straight into browsing — ideal to kill those 10 minutes waiting for the bus to arrive.
You can of course also query for sites from the redesigned navigation bar on top. And we’ve made some adjustments here since the beta release: in the Settings menu, you find an option to move the navigation bar to the bottom. It costs you a bit of screen real estate, but makes for a more relaxed single-handed browsing experience.
The red O button has moved to the top right of the screen (unless you put the Navigation bar at the bottom), just like in other Android applications, and it toggles a menu with advanced options such as Sharing, Find in Page, Downloads, Settings, and more.
If you miss an Exit button or want to go back more than one page in the tab’s History, long-press the back button. To save a page to read off-line, hit the + icon at the left of the address bar.
A special mention for Off-Road mode, available from the red O menu: when toggled on (also subtly indicated by a thin red line on top of the browser), pages are loaded via the Opera Mini servers, thereby reducing bandwidth and data cost. So, no more need to switch browser to get Opera Mini’s data compression features: you get it all in one package.
Keep in mind that users can set their own preference of Off-Road-specific image quality: they can increase or decrease image quality, or even opt to receive no images at all (a good option to have, since images account for more than 50% of page size). As my colleague Bruce points out: be sure to use alternative text with images, and remember — it’s not just for the visually impaired!
Automatic text wrap
By default, Opera for Android uses the same text autosizing (aka FontBoosting) mechanism that can be found in Chrome for Android. E.g. if you visit this desktop-specific Wikipedia page about artichokes, you see that some of the text is displayed bigger, making it readable without having to zoom in. However, as FontBoosting is only applied selectively and interferes with author-defined text size differences, we’ve made it possible to turn this off in Settings, and choose for automatic text wrap instead. Turning on text wrap instructs Opera for Android to wrap lines no matter how much you zoom into a page so there’s no need for horizontal scrolling.
Of course, there will be times as a developer when you’ll need to debug sites running on Opera 14 for Android. This can be done from Windows, Mac and Linux desktops — see our article about remote debugging Opera for Android.
Made to discover
Of course, there are many more details to talk about — offline pages, private tabs, browser.js — but we’ll leave those for you to discover. Enjoy, and let us know what you think!