|
| Which one's the best for you? |
These browsers are technically tested against each other and their features are discussed.
Overview
1. The Candidates
2. User Base
3. The Testing Hardware
4. Installed Size
5. Launch Time
6. Futuremark Peacekeeper
7. HTML5 Test
8. Interesting Note
9. Closing Statement
10. The Verdict
1. The Candidates
Chrome is Google's own mobile browser alternative to the Android's default browser. Once you sign into it, it automatically synchronises with your Chrome desktop browser (assuming you've signed into that too) and it will pull over all your bookmarks, as well as synchronizing a "Mobile Bookmarks" folder to differentiate between mobile specific links and desktop links. The convenience here is that the account you're using is your Android and G-mail account, so although other browsers provide sync options, they mostly require you to create an account under their authentication system.
 |
| Dolphin with touch menu open. |
Firefox is a popular desktop browser, and it's mobile alternative is also quite popular. I haven't personally used this one much, but both the mobile and desktop browsers have the sync option like other browsers, so it is a viable option if you already use Firefox heavily on your desktop.
Opera: Having personally been a fan of Opera as a stable tabbed desktop browser in the early 2000s, I had Opera Mini installed on one of my first bar phones, a Sony Ericsson K300, and continued to use it throughout the years on all phone and desktop platforms. Although there's not much need for the Mini version nowadays, at least I don't believe so, since Internet data and speeds aren't that much of a contemporary issue anymore for browsing the Internet, the "Opera Mobile" browser, allowing for desktop site retrieval is still quite a powerful Android alternative. And for those concerned about usage, the "Off-road" mode allows for retrieval of compressed data from Opera's web servers.
Android Browser is the default browser that arrives on all Android smartphones and it serves as a good benchmark for comparison against any browser which is downloaded as an extra to a device, because as the adage goes: If it's not broken, why fix it?
2. User Base
As of this writing on August 2013 these are the highly undetailed number of users as recorded on the Play Store.
| Browser | Installs | Reviews |
| Chrome | 100,000,000+ | 436,131 |
| Dolphin | 10,000,000+ | 1,172,315 |
| Opera | 10,000,000+ | 441,140 |
| Firefox | 10,000,000+ | 349,531 |
| Android Browser | n/a | n/a |
If anything can be derived from this, it would be that Chrome leads the race from an "opt-in" point-of-view, but the number of users on the default Android Browser is clearly the winner in terms of mobile browser statistics as shown in the below graph from StatCounter.
It's worth noting that Dolphin appears to have the most vocal of users, having a significantly higher number of opinionated users based on reviews. Is there a cause for the passion?
3. The Testing Hardware
The hardware itself is a dual core 1.2 GHz ARM Cortex A9 CPU, PowerVR SGX540 GPU, 1GB RAM, and no applications running in the background, all on a 4.3" 960x540 qHD.
4. Installed Size
 |
| Opera Browser |
| Browser | Size (MB) |
| Android Browser | 0.9 = 0*+0.9 |
| Opera | 49.70 = 18.9+30.81 |
| Dolphin | 36.45 = 19.95 +15.5 for Jetpack 9.14+10.81 =19.95 |
| Firefox | 48.47 = 25.61+22.86 |
| Chrome | 67.59 = 62.14+5.46 |
Obviously the default Android Browser wins this, given that it is preinstalled and you are unable to remove it completely (it only allows you to disable it).
But for a standalone browser, there are minimal differences between Opera, Dolphin and Firefox - so choosing between those three browsers, expecting around 20-25 MB for application data is reasonable. The only exception to size is Google's Chrome itself, which is significantly larger at over twice the installed size of the others - the only justification I can see for this is the potentially fuller browsing experience it provides, as it is derived from the same base code as the desktop Chrome browser itself. Whether or not the benefits outweigh the installed size is determined by how much you use the browser on your smartphone, and what you use it for.
5. Launch Time
I personally find this measure to be quite important. When I jump on my smartphone to check something out on the Internet regardless of browser choice, I like something that launches as quickly as possible - to allow for a seamless browsing experience without any delays. Obviously the faster the device, the less of a difference will be noticed, but not everyone has the latest and greatest hardware, so from the perspective of what I would consider 'moderate' hardware (specifications under 'Testing Hardware') I've run a test to see which one would be the most prompt in entering a usable state.
The measured time indicates the time that it takes from browser launch, when not existing in memory, to the time the keyboard appears after the URL/search bar is selected inside the browser itself - this gives a more real value, instead of when the browser is "visible" and not actually loaded. The values are averaged over 4 runs.
| Browser | Time Taken (s) |
| Android Browser | 3.16 |
| Firefox | 4.28 |
| Chrome | 4.45 |
| Opera | 5.69 |
| Dolphin w/ Jetpack | 6.63 |
Android's own built-in browser is the quickest option here - which should not be a surprise given it's simplicity and the fact it's built into the operating system. Big marks here for the stock browser in my books, I'm personally a really impatient person, so the quicker the better!
http://peacekeeper.futuremark.com/
This is basically a browser Javascript performance tester for any browser, on any device. This was tested in landscape view for maximum display. No other apps were running in the background and there were no other browser tabs in memory. I also ensured the device was charging through USB for optimal performance.
When it comes to efficiency of processing complex Javascript, Chrome does the best job performance-wise. So if you're constantly loading complex media-rich pages on pretty decent hardware (more likely on a tablet) then Chrome is the way to go.
http://html5test.com
A great website for determining the HTML5 capabilities of any browser, on any device. The specified scores are a superficial value, but a good overview, when you drill down into the details, some browser will have strengths and weaknesses where others do or don't.
From the results above, as a standalone browser Dolphin does the best job, as it can handle as much as a desktop browser can (Dolphin's 474, compared to Desktop Chrome's 463). This means that more technically advanced web sites will work on Dolphin, although good web designers will build for minimum requirements to ensure that more users and/or customers can fully utilise their site.
From the results of these tests, if you're like me and only need web browsing on the mobile for basic experiences, then all the extra bells and whistles aren't necessary, and the HTML compatibility test would not have been all that helpful - although it is good to know what mobile browser will be more likely to be compatible with the new HTML5 mobile websites being rolled out by your favourite online or bricks and mortar retailer (assuming they don't have an app).
Although favourites syncing can be helpful - in which case Google's Chrome browser would be ideal if you use Chrome on your computer, and if you use Opera on your computer... basically match your mobile browser to your desktop computer to take advantage of cloud syncing where available. But if this isn't an important factor for you, and you only browse casually on your mobile and you're happy e-mailing yourself links, then go for the best performer.
After personally having used Opera Mobile for a while, it also used to be my main PC browser, and not being satisfied with the Opera Unite sync - I moved to the Chrome Mobile/Desktop pairing. I've found the integration between desktop and mobile very smooth with Google's browser, it even comes with shared history grouped by device (including other computers you've logged in through). There is also dedicated folder for your mobile bookmarks so that you can focus on mobile bookmarks on your phone, but at the same time you're also able to access those links from your desktop too.
After moving to Dolphin mobile, not being satisfied with the sluggish performance of Chrome on my mobile, I was impressed by the unique touch menu interface as well as the apparent speed of the browser with the Jetpack add-on. After coming up against minor performance problems with multi-tabbed browsing, I was interested in finding an alternative.
I've now gone back to the default Android Browser, after running these performance tests. It wasn't fantastic and felt dated, but having turned on the 'Labs' option of 'Quick controls' which enables a touch-based menu whenever you're fingers are on the edge of the screen, I'm pretty happy - simple changes in the UI can really make a difference, and I now have more space on my phone.
1. If you want sync between your Desktop & Mobile Browsers:
Stick with the mobile equivalent of the main browser you use on your desktop for bookmark/history sync since most popular browsers allow you to create an account with them for this now, but I'd recommend Chrome for both if you don't have a preference, as it is the quickest performing mobile browser and also the most used on Android - meaning better developer support. And you'll likely already have a Google account if you're on Android.
2. If you just browse casually during commute, or only need to find information quickly:
1st: Android Browser
2nd: Firefox
3rd: Opera
If you don't need any features at all, just use the built-in Android Browser for casual web surfing. If your phone is newer, it will no longer have the older Android Browser and default to Chrome. If you want something 'lighter' and 'quicker' try out Firefox and Opera for Android, as they come in at a close second and third, respectively, where it matters: launch time and javascript processing speed.
6. Futuremark Peacekeeper
http://peacekeeper.futuremark.com/
 |
| Results of running Peacekeeper on Dolphin with Jetpack, funnily it's identified as 'Safari'. |
This is basically a browser Javascript performance tester for any browser, on any device. This was tested in landscape view for maximum display. No other apps were running in the background and there were no other browser tabs in memory. I also ensured the device was charging through USB for optimal performance.
| Browser | Peacekeeper Score |
| Chrome | 596 |
| Opera | 576 |
| Android Browser | 505 |
| Firefox | 399 |
| Dolphin w/ Jetpack | 387 |
When it comes to efficiency of processing complex Javascript, Chrome does the best job performance-wise. So if you're constantly loading complex media-rich pages on pretty decent hardware (more likely on a tablet) then Chrome is the way to go.
7. HTML5 Test
http://html5test.com
 |
| Results of running HTML5 Test on Firefox |
| Browser | HTML5 Score |
| Dolphin w/ Jetpack | 474 |
| Firefox | 440 |
| Opera | 439 |
| Chrome | 421 |
| Android Browser | 303 |
From the results above, as a standalone browser Dolphin does the best job, as it can handle as much as a desktop browser can (Dolphin's 474, compared to Desktop Chrome's 463). This means that more technically advanced web sites will work on Dolphin, although good web designers will build for minimum requirements to ensure that more users and/or customers can fully utilise their site.
As a comparison, I used the Chrome browser on my laptop as a benchmark, to get an idea of how it compares to "the real thing". I chose Google Chrome purely because it is my main "computer" browser.
Peacekeeper 1618
HTML5TEST 463
You may have noticed that the HTML5 Test gave a score of 463 to Desktop Chrome vs 474 for Dolphin Mobile with Jetpack. The main differences that were working to Dolphin's advantage here are: +15 points Dolphin support for Microdata, which is apparently used in the background for search engines and the like - it doesn't seem like a massive advantage. There are a few other differences too that balance things out, the only main one I noticed was that Dolphin doesn't support the Web Audio API, and it supports the MP3 format.
Peacekeeper 1618
HTML5TEST 463
You may have noticed that the HTML5 Test gave a score of 463 to Desktop Chrome vs 474 for Dolphin Mobile with Jetpack. The main differences that were working to Dolphin's advantage here are: +15 points Dolphin support for Microdata, which is apparently used in the background for search engines and the like - it doesn't seem like a massive advantage. There are a few other differences too that balance things out, the only main one I noticed was that Dolphin doesn't support the Web Audio API, and it supports the MP3 format.
9. Closing Statement
From the results of these tests, if you're like me and only need web browsing on the mobile for basic experiences, then all the extra bells and whistles aren't necessary, and the HTML compatibility test would not have been all that helpful - although it is good to know what mobile browser will be more likely to be compatible with the new HTML5 mobile websites being rolled out by your favourite online or bricks and mortar retailer (assuming they don't have an app).
 |
| Android Browser with 'Quick Controls' |
After personally having used Opera Mobile for a while, it also used to be my main PC browser, and not being satisfied with the Opera Unite sync - I moved to the Chrome Mobile/Desktop pairing. I've found the integration between desktop and mobile very smooth with Google's browser, it even comes with shared history grouped by device (including other computers you've logged in through). There is also dedicated folder for your mobile bookmarks so that you can focus on mobile bookmarks on your phone, but at the same time you're also able to access those links from your desktop too.
After moving to Dolphin mobile, not being satisfied with the sluggish performance of Chrome on my mobile, I was impressed by the unique touch menu interface as well as the apparent speed of the browser with the Jetpack add-on. After coming up against minor performance problems with multi-tabbed browsing, I was interested in finding an alternative.
I've now gone back to the default Android Browser, after running these performance tests. It wasn't fantastic and felt dated, but having turned on the 'Labs' option of 'Quick controls' which enables a touch-based menu whenever you're fingers are on the edge of the screen, I'm pretty happy - simple changes in the UI can really make a difference, and I now have more space on my phone.
10. The Verdict
1. If you want sync between your Desktop & Mobile Browsers:
Stick with the mobile equivalent of the main browser you use on your desktop for bookmark/history sync since most popular browsers allow you to create an account with them for this now, but I'd recommend Chrome for both if you don't have a preference, as it is the quickest performing mobile browser and also the most used on Android - meaning better developer support. And you'll likely already have a Google account if you're on Android.
2. If you just browse casually during commute, or only need to find information quickly:
1st: Android Browser
2nd: Firefox
3rd: Opera
If you don't need any features at all, just use the built-in Android Browser for casual web surfing. If your phone is newer, it will no longer have the older Android Browser and default to Chrome. If you want something 'lighter' and 'quicker' try out Firefox and Opera for Android, as they come in at a close second and third, respectively, where it matters: launch time and javascript processing speed.