Jump to content

FULL ROUNDUP:Browsing the Web on Windows Mobile just like on iPhone,incl. IEM6 review

Guest Menneisyys

Recommended Posts

Guest Menneisyys

After purchasing an iPhone 3G, I immediately fell in love with Safari, its Web browser. Granted, it's somewhat less capable as the best, comparable Windows Mobile (WinMo for short) titles (no Flash, no page saving, no copy/paste, no Opera Link, no explicit text size settings, no caching etc.) and, from time to time, it crashes even with the last, 2.2 firmware version, but it's still much better usable and much faster than anything on Windows Mobile.

Needless to say, seeing the immense success and popularity of iPhone's Safari, Windows Mobile software developers followed suit and, for quite some time now, have been trying to simulate the interface and easy controllability of Safari. Sure, they can't circumvent the problems caused by the hardware (namely, the resistive touchscreen, which, in cases, require a lot of pressure, unlike on the capacitive iPhone); nevertheless, the Windows Mobile developers have indeed managed to come up with some really decent alternatives.

In this roundup, I mostly explain how current Windows Mobile Web browsers are able to provide the same user experience as Safari on the iPhone (again, apart from the much inferior hardware, touchscreen-wise). There have been several shots of providing the same; see for example THIS and, most importantly, THIS article. The latter one, unfortunately, severely lacks in that it only compares Internet Explorer Mobile and Opera Mobile 9.5 - read: no SkyFire, no Iris, no NetFront, no Opera Mini. In addition, the date of the article also shows that it doesn't test the latest Explorer Mobile 6 and the latest, further enhanced builds of Opera Mobile.

Being focused on Safari-like finger-only controllability, I've also reduced the stuff that is more technical: for example, Web compliance testing, strict benchmarking and documenting even the most hidden features. Please consult my previous all-in-one article (my W3C speech) for more info and further links on all these.

I've only tested browsers capable of finger-based scrolling. This is why I've completely disregarded older, non finger-based scrolling-capable plug-ins and that I used Spb Pocket Plus with the older (but still exclusively used) Internet Explorer in order to add this kind of functionality.

Note that I provide a lot of info never before published; for example, a decent (!) comparison of the latest buzz, Internet Explorer Mobile 6 (IEM6) to the previous version, running on real(!) devices - and not just emulators. As you will see, the current IEM6 version is simply not worth bothering with - it's definitely slower and, configurability-wise (see the lack of One Column mode or the lack of the, on (W)VGA devices, highly useful Use High Resolution switch), far less capable than the previous IEM. It's just not worth flashing your device with a ROM containing IEM6 - for example, Tomal 8.5 for the HTC Universal and MoDaCo's Touch HD ROM's - currently, there [still] aren't easily-installable CAB distributions of IEM6, you need to hunt down an XDA-Devs or MoDaCo-cooked ROM coming with it; currently, it's the only way to get the browser onto your phone.

Also note that, now with high-resolution screens being increasingly used in devices like the Diamond and Diamond Pro (VGA) and the X1 and the HD (WVGA), I've found it sufficient to run the tests on VGA devices, and only some on QVGA ones (mostly for testing QVGA-only versions). Therefore, most of the screenshots and the additional hacks (for example, the VGA Jbed one) I provide are for VGA devices.

Note that I paid special attention to elaborating on how the reviewed Web browsers are able to use large® fonts so that you'll be able to use them while, for example, commuting to/from work. (Actually, it was, at first, because of this that I started testing browsers in this regard. I generally love riding the bike in the gym. I want to remain thin and biking is the best way to do this. It, however, can become very tedious, particularly if you ride three hours without any pause so that you can always keep your pulse over 120. Watching a movie from one of my 15" UXGA ThinkPads is one way of killing the time during this; another is browsing the Web on my PDA's and smartphones. This, however, requires you to use comparatively large characters as you're constantly moving and keep the device in your hand.) In this regard, the VGA screenshots I present and the approach I take (let's find out whether the browser is able to render the test pages with sufficiently large characters) can be perfectly applied to QVGA devices. After all, it's only when rendering text with small character sizes ("requiring a magnifying glass") that there's significant difference between low-res (QVGA) and hi-res (VGA or WVGA) screens; with large character sizes used, the difference pretty much diminishes. (Apart from the characters' being much prettier and less blocky / pixelizated, of course.)

Mozilla's Mozilla / Firefox port still has no Windows Mobile version. Finally, note that while Makayama's Touch Browser does support iPhone-like scrolling, I just don't see any point in actually paying for it. In the tests of the latest, 1.16 version on my HP iPAQ 210, it proved to be vastly inferior to the IEM + Spb Pocket Plus 4 combo. The latter scrolls pages orders of magnitude faster and nicer. There is just no comparison between the speed of the two browsers. Speed issues aside, the current, 1.16 version still isn't much better than the initial version I've reviewed HERE (albeit some of my biggest, interface-related, complains have indeed been fixed; for example, a QWERTY keyboard has been added.)

1.1 Opera Mobile 9.5

Let's start with Opera Mobile, which is, especially with its latest version (so far, only released for the Samsung Omnia, but already ripped by the XDA-Developers folks and released as an easily-installable CAB file), offers everything a decent Safari-alike should - and more. With Opera Mobile, the only difference in browsing the Web will only be your having to actually hold down the touchscreen for it to work.

Currently, there several versions of Opera Mobile. Of them, I’ve reviewed the (currently) official and, compared to the Omnia version, old (Oct. 2008) version 9.51b2 available for download HERE and the much more recommended, latest, unofficial Samsung Omnia version available HERE (direct links to download HERE and HERE. Note that there’s a combined VGA + QVGA + Flash Lite 3.1 version HERE; it has all the three CAB’s in one RAR file). The latter is the way to go if you have a QVGA Pocket PC or want to see embedded, Flash Lite 3.1-compliant videos (currently, YouTube, Google Video, blip.tv and PornoTube - nothing else; please see THIS for more info). If you, on the other hand, have a VGA model, you absolutely don't want built-in support for the above-mentioned video services or don't need the freedom of the zooming the new version offers (most of the time, you'll find the old, official version in this regard just OK), you may want to stick to the official version.

Note that there’re a lot of (slightly) older “unofficial” Opera Mobile builds. Some are, in some respects, better than the Omni release reviewed in this roundup; for example, some support being installed to a memory card, while the Omni version doesn’t. I haven’t included these older builds in the article to keep its size down.

Speaking of “unofficial” “rips”, also the question of legality should be mentioned. While, strictly, it’s not really legal to rip a browser off a ROM (and installing it on a device), as Opera, currently, doesn’t offer any kind of a downloadable and purchasable, stable and final version of Opera Mobile, I think that, for the time being, you can freely install these XDA-Devs rips on your phone. However, when a commercial (and superior) version of Opera Mobile is released, you will want to upgrade to it. Not only because you it’s everyone’s interest to support the, currently, best multiplatform browser developer that produces browsers that are really pleasant to work with on both desktop PC’s and mobile phones / PDA’s so that they can continue improving their products, but also because the final version will surely have Opera Link.

Support for Opera Link, unfortunately, is severely missing from the currently available 9.x Opera Mobile builds. I’ve played a bit with overwriting \Application Data\Opera9\opera6.adr with the desktop Opera’s \Documents and Settings\username\Application Data\Opera\Opera\profile\opera6.adr, but in vain: it didn’t work. (The reason for this may have been my bookmark file containing some 3000 bookmarks.) I’ll go on with hacking the file to see whether there’s an easy way of doing so. If I succeed, it’ll mean you’ll be able to easily replicate your desktop Opera favorites on your WinMo phone (and vice versa), which will, to some extent, fix the lack of Opera Link.

1.1.1 Problems on VGA devices

Note that the CAB above is strictly meant for QVGA devices; if you want to install Opera Mobile on VGA devices, you'll need THIS file instead. It fixes all the issues of the original version: provides a VGA skin (directly available HERE, should you want to deploy it on the original, QVGA version), which, in addition to providing large icons, also doubles the size of the on-screen zoom arrow and, finally, increases the zoom magnification to 200%.

You may want to know what the latter means (even if you no longer need it - the VGA CAB comes with the hack applied) - after all, Opera Mobile has excellent (!) configuration and tweaking capabilities worth knowing of (some of them are listed HERE - and, of course, my chart.) With the QVGA version, automatic (the one with double-taps) zoom-in seems to calculate the right zoom level based on QVGA horizontal sizes; that is, the zoomed-in state will contain at most half the size of the actual, zoomed-in contents as can be seen in the following screenshots:



The same screenshot taken showing the exact same screenshot on a QVGA model (also showing the newly-introduced, albeit, for quick positioning, useless minimap in the upper left corner):


This means you, unless you do the hack I'll describe soon, almost always want to prefer using manual zoom to correctly zoom into the text. To avoid having to do this, just enter "opera:config" in the address bar:


Then, select Adaptive Zoom (it's on the top) and scroll down to Maximum zoom. Change 100 to 200:


After this, automatic (!) zooming will work just fine.

Important: this version (both the QVGA one with the additional tweaks explained above and the VGA one) uses pixel doubling with images (and videos). This, to my knowledge, can't be fixed. Nevertheless, it, otherwise, works just fine on VGA models.

1.2 SkyFire

The second, particularly for QVGA users, most recommended browser is SkyFire, which works in exactly the same way as the pretty much useless, incapable and, since then, cancelled DeepFish did: everything is done on the central server(s) of the developer. The server only transfers (QVGA-resolution) images to the client. In this regard, it's less data use- and CPU-efficient, than Opera Mini, the other (current and recommended) solution using the central server approach. Yes, it constantly uses your data connection and CPU; which means both (at times, dramatically) decreased battery life and increased data usage. Keep this in mind if you plan to use it over a non-unlimited cellular connection. Furthermore, if you have a VGA device, you may want to look for something else if you can't put up with the low-resolution, pixel doubled text and graphics.

It has a lot of goodies. For example, it has one of the best zoom-in algorithms: it has never failed to zoom into text. With all (!) of the other browsers, there have been problems doing this with some sites or forums - even the latest, b15233 version of Opera failed at this sometimes, necessitating some kind of a manual zoom-in, let alone the others.

Furthermore, it supports playing Flash, Java applets, Ajax and everything else Firefox / Mozilla on the desktop Windows supports. This means it's capable of playing back YouTube etc. videos - and not only them, but virtually everything: as it uses the "real" Flash behind the scenes, it has no problems playing back Flash 9 contents either - that is, the video services Flash Lite 3.1, used together with Opera Mobile b15233, is incompatible with.

Note that it does have some disadvantages at playing back YouTube (Google etc.) Video compared to the Flash Lite 3.1 + Opera Mobile b15233 combo. Granted, it's far better in that

1, it uses far less CPU at rendering videos than Opera Mobile: about 40-50% on my 624 MHz HP iPAQ 210, while Opera Mobile is around 90%.

2, initially loading a page containing several compatible videos doesn't result in a major performance hit. Just try to load a TouchArcade page containing more than two or three videos in Opera Mobile and you'll see what I mean. Opera spends minutes loading it; SkyFire, on the other hand, only spends some seconds. Quite big a difference! (Note that the same stands for the Opera Mobile & Flash Lite vs. iPhone Safari relationship – the latter loads pages having a lot of directly embedded YouTube videos - like TouchArcade – in some seconds only. Yes, at times, not having true Flash Lite, “only” YouTube support pays off.)

3, video playback works just great on slow Pocket PC's; for example, ones based on 195 MHz TI OMAP CPU's like the HTC Wizard. The Opera Mobile + Flash Lite 3.1 is plain incapable of playing back any videos on this kind of a CPU without major stuttering and pauses.

However, particularly in not supported countries, the speed of the video playback will be much lower - between 4-5 fps (frame per second) and there will be times there won’t be any sound at all (and, if there is, it’ll be of worse quality than with direct, non-streaming playback like that of Flash Lite). While, on faster WinMo devices, Flash Lite 3.1 has no problems in playing them back at full speed - that is, 25-30 fps.

Fortunately, now SkyFire is accessible from all around the world – in the first few year of service, you could only register to it from the US and Canada.

1.3 Opera Mini 4.2.13337

Opera Mini, along with all Jbed versions (the MIDlet manager - that is, the execution environment - I recommend the most to be used with Opera Mini), offers a lot of goodies; for example, finger-based scrolling. It surely isn't as nice as Safari or Opera Mobile (there're no "rubberband", that is, inertia effects); however, the traditional strengths of Opera Mini (for example, the very low data traffic essential if you're on a limited cellular data subscription and Opera Link, which, unfortunately, is still not supported in the latest Opera Mobile versions) can easily make this browser the browser of choice.

For VGA users, I especially recommend the VGA-hacked Jbed 5.1 version; please see THIS for more info. For QVGA users, you can safely stick with older versions of Jbed.

Opera Mini behaved pretty nice in my tests - it zoomed into text very well and reflown the columns intelligently. No problems in here - much as it's "only" a Java MIDlet, it's still a very decent browser, particularly if you want to make use of its excellent (!) Opera Link and multitab capabilities.

Finally, note that, after my W3C speech, I've published a full tutorial on making Opera Mini your default system browser.

1.4 Iris 1.0.16 (1.1.0 b3)

This browser was another nice surprise - no wonder for example the MSMobiles folks liked it very much. While it's still lacking a bit here and there (the most important of them being the lack of keeping the previously zoomed-to screen contents horizontally aligned when finger-scrolling vertically), it can already be rightfully compared to the other browsers available on Windows Mobile. I, however, would still stick with Opera Mobile, SkyFire or Opera Mini (depending on your needs) instead - they're (still) superior.

1.5 Pre-6 Internet Explorer Mobile (IEM) with Spb Pocket Plus 4.0.2

Unfotunately, the "old" (but still the only built-in IEM version shipped with even the latest devices) Internet Explorer Mobile (IEM) is far inferior to anything else, even with the really decent, 4-series Spb Pocket Plus plug-in to allow for multitabbing and iPhone-like scrolling.

The biggest problem with this browser, along with the heavily outdated HTML / scripting engine, is the inability to dynamically zoom in/out to/from the page: to switch between reading some text (with sufficiently large and readable characters) in the zoomed-in state and the page overview. All the other browsers are capable of this via single or double taps on the selected (textual) area. (Yes, even Opera Mini - it's just that you can't use the same screentap(s) to switch back to zoomed-out, page overview mode but have to use the hardware Action button [if available] or a menu command to do so.)

Add the poor testpage rendering results to this (many times, you will need to switch to One Column mode very often to be able to make use of the entire screen estate), the comparatively slow page loading speed and you'll see why I don't recommend this browser at all.

1.6 Internet Explorer Mobile 6 (IEM6)

Unfortunately, the current version of IEM6 has turned out to be a real disaster. While it supports goodies like dynamic zooming (with screen taps) and built-in, rubberband-like finger scrolling, it is very slow (actually, much-much slower than even the previous, pre-6 IEM version(s)), its zoom-in capabilities are really bad (doesn't take advantage of the entire screen and, in addition, it uses really small characters, which can't be fixed) and, what is more, you can't even use the One Column mode to make it render properly.

All in all, stay away. This browser is pretty bad and, currently, not worth installing (which, currently, involves flashing an entire XDA-Devs or MoDaCo “cooked” ROM). Hope Microsoft does fix these issues before releasing a "real" version for OEM's to be included in their ROM's. Again, note that the current version of IEM6 most probably doesn’t represent the final version Microsoft releases some time. I’m absolutely sure they’ll for example include for example the “Use High Resolution” checkbox, which will make it possible to make it render large® fonts. That is, my “trashing” the current IEM6 doesn’t mean the final, official version will be this bad at all. The current version is definitely an early alpha.

1.7 NetFront (NF) 3.5.009 b729

NF has recently received screen dragging support. Unfortunately, it can barely be used as, as soon as you start to drag the screen, in most cases, the context menu is displayed. The situation is way worse than with other browsers also having a context menu (Opera Mobile etc.).

It has other problems too: compared to the, in this regard, best browsers (Opera Mobile / Mini, SkyFire and, of course, the really fast iPhone Safari), it is slow to load pages. Even screen orientation or view mode changes require (lengthy) page reloads, unlike with most other browsers (except for Opera Mini and SkyFire, which also reloads pages if you dynamically change your screen orientation).

All in all, I cannot recommend NetFront at all. There is simply no point in preferring it to the three most recommended browsers: Opera Mobile, SkyFire and Opera Mini.

2. The feature / comparison chart

It's available HERE. Make sure you open it in a maximized (F11 in all the three major Web browsers under Windows) Web browser window. Also use zoom in/out (Ctrl+mouse wheel on all the browsers; if you don't have a wheel, Shift + and - in Opera; Ctrl + and Ctrl - in both Mozilla / Firefox and IE) to avoid having to scroll the chart horizontally.

Explanation (and additional comments) of the chart:

2.1 Real-world rendering tests

The first part of the chart elaborates on rendering some forum engines, also with some that caused iPhone Safari some problems. Note that I've tested (and published) the results in both orientations because, at times, you'll want to prefer browsing in Portrait mode simply because most phones are easier to hold that way, particularly while walking / doing some physical exercise - or, if you have a phone / PDA with a screen that has issues like that of the Dell Axim x50v / x51v. I used the letter "L" to denote landscape and "P" the portrait orientation.

A very important note: I’ve evaluated the browsers based on their ability to render text with large, well-readable-even-when-commuting-or-walking characters (or, with character sizes that are well readable on 2.8” VGA or 3” WVGA screens like those of the HTC Diamond, HTC Diamond Pro or the S-E X1), NOT based on the overall rendering quality of the engine. That is, I’ve only given “Poor” to browsers that could render textual content with small characters, regardless of the overall quality and standards compliance of the engine.

This is why IEM6, which is plain incapable of rendering text with acceptable-sized, in general, got very bad marks. Nevertheless, the IEM6 engine isn’t THAT bad – it’s pretty much on par with, say, NetFront. That is, based on the “Poor” and “Unacceptable” marks I’ve given IEM6 in most cases, don’t think it is THAT bad. It’s currently bad for reading in circumstances where you do need considerably larger characters. If you have a (W)VGA phone (like the HP iPAQ 210, hx4700, the HTC Touch HD or the Athena with the 5” screen) with a large (at least 3.8”) screen AND you aren’t moving, you may find IEM6’s rendering quality just fine. (It’s another question IEM6, being just an alpha version, severely fails in many other areas: speed, capabilities etc.)

The first link takes you to a pretty problematic site with code not compatible with the zoom-in engine of any of the Web browsers (except for Mozilla / Firefox, which has no problems with zooming them in) - which is a major problem on higher-resolution, but not very large screen like the UXGA 15" or WUXGA 15.6" screens of high-end ThinkPad models. I've paid special attention to checking out how the browsers render the number of the post (it's in the upper right corner of every individual entry). As you can see (of the three most recommended browsers), Opera Mobile is the best to retain this - at least in Landscape mode, using automatic (non-manual) zoom and large char. Unfortunately, only the first part of this number is visible in Opera Mini (and only in Landscape), unless you switch to the more restrictive (albeit a bit more bandwidth-friendly) Mobile View mode (either the “Mobile View” context menu or in Settings) – then, it’ll show these numbers without problems. SkyFire fares the worst in this regard: it not only hides the number of the post, but also (in Landscape, part of) the date.

Other than these, I haven't found other problems related to zooming-in in order to display large characters (where it was at all possible - for example, the maximal size I could get was still very tiny with IEM6 and it was only by switching to the very restrictive One Column mode that I could get readably large chars with Iris.)

(Incidentally, you can easily make these forum pages work in the desktop Opera by just removing all occurrences of

[and the accompanying
] from the source. Nevertheless, the Opera / Microsoft folks could really look into this problem to make the non-Mozilla/Firefox folks' life easier that long for the ability to freely zoom in.)

The second link takes you to the Pocket PC Thoughts frontpage. I've chosen this page to one of the standard test pages because iPhone Safari severely fails at rendering the contents of this, otherwise, when it comes to the HTML source, very simple page: it uses relatively small characters you may not be able to read (particularly not while moving). In this regard, all of the Windows Mobile browsers behaved orders of magnitude better - except for, again, IEM6, which behaved far worse than anything else.

The third link points to a Thinkpads.com thread, where one of the posts contain a very long thread. iPhone's Safari fails at rendering these kinds of HTML pages without any advanced markup. Needless to say, zooming in (with pinching the screen) doesn't help either - Safari isn't as sophisticated as Opera Mobile, where the latest build already supports reflowing the text at any (manual) zoom level - not just automatic ones. IEM6, as usual, sucks really bad; with Iris, you again have to switch to the One Column mode, but even then the charsize may still turn out to be too low. Speaking of the most recommended three browsers, Opera Mini and SkyFire had no problems with fully taking advantage of the available screen estate (note that, in SkyFire, you can hide the address bar as is also explained in the "Full screen" row). Opera Mobile, in Landscape mode and using Large characters, only used the two-third of the screen on the left (and left the rest unused); this is why I only gave it a "Fair". Again, only using dynamic, automatic zooming; I haven't tested the text reflowing capabilities of b15233, used together by manual zoom fine-tuning, with this particular case. You might want to give it a try to see whether, then, you can use the entire screen estate or not - I bet you will.

The fourth link shows how the DPReview main page is rendered by default. As can you see, you will most probably want to use manual fine-tuned zooming with Opera Mobile so that the text fully fills in the entire screen estate. Alternatively, if you use the latest, b15233 build with the VGA hacks I've explained (or, straight the VGA version), you won't have problems with the zoom - the screenshots here have been made with the official, earlier 9.51b2 and not the latest b15233.

The fifth link takes you to the DPReview forum. The recommended browsers have no problems rendering this, not even with large characters. Iris, again, needs to be switched to the restrictive Column Mode and IEM6 uses uselessly small characters.

2.2 Scrolling-related tests

In the first test, Scrolling speed, I've elaborated on how quickly you can scroll and how much time it takes to display the text you've just scrolled to. The best and fastest browser is, in this regard, Safari; Opera Mobile and NetFront aren't much worse, though.

The second one, "Real rubberband and inertia", elaborates on whether the tested browser is able to measure the speed of your finger when the latter leaves the screen, and if the speed is above a certain threshold, the screen will continue to ‘roll' in the last direction of your finger when it lost contact with the screen. This is one of the best features of iPhone's user interface, and, of course, Safari. As you can see, of the three most recommended titles, neither Opera Mini nor SkyFire support this. Hope this will be later implemented.

"Does it try to keep the same horizontal position while scrolling?" lists whether a slight horizontal displacement while you quickly scroll up or down results in the screen content dragged to the left / right, which, then, may result in having to re-position the text column you were previously reading. As can clearly be seen, the two Operas (and, of course, Safari) are the least sensitive to this kind of error.

"Minimap? Quick positioning possible on it?" shows whether there's any kind of a minimap on the screen and whether it can be directly used to quickly change your zoomed-in position. In this regard, Iris is by far the best. Note that it's only the QVGA version of Opera Mobile b15233 that supports minimap (but, unfortunately, no quick positioning); the VGA version doesn't have this any more. However, you can add this back with some manual hacking, should the need arise.

Other scrolling issues: here, I listed the problems you may face during scrolling the web pages. NetFront has the biggest problems of all with displaying the context menu almost as soon as you start dragging. This makes NetFront almost useless for this kind of usage.

Manual (free) zooming?: in addition to the well-known automatic zoom (which has been elaborated on in the first section), some browsers also support freely zooming into any area of the screen. You may already seen this on the iPhone, where the two-finger "pinching" of the screen does exactly this - in not only Safari, but also a lot of other apps as well. Of the other solutions, Opera Mobile b15233's is by far the best because it allows you to use any zoom level: it'll always make sure the text is correctly re-flown in the given level. Unfortunately, this kind of functionality is really missing from Safari. Yes, this is one of the areas where Opera Mobile is way better than its iPhone alternative.

2.3 Input

This group examines the various input capabilities of the browsers.

Finger-friendly drop-down lists: if you've ever used Safari, you may have already noticed it has very nice and finger-friendly drop-down selector lists:


Here, I explained (and shown) how finger-friendly Windows Mobile browsers are. Unfortunately, none of them excel; probably the best are the two Opera browsers, but they're still a far cry away from iPhone's Safari. Note that if you have a D-pad, you can use the up/down arrows to move the selection and the Action button to select the current one, which, to a certain degree, provides a solution to this problem. Too bad some WinMo phones (for example, the Touch HD) don't even have a D-pad…

How does it work together with third party full screen keyboards?: as the built-in on-screen keyboard in Windows Mobile is almost impossible to use (even after switching to Large size in Settings / Input / Large Keys) with fingers, you may want to take a look at alternative, considerably bigger (or even full-screen ones) on-screen keyboards to allow for finger-based, stylus-less input. I've, in this regard, tested Spb's Full Screen Keyboard. It turned out to be working wonderfully with all browsers, the only exception being Opera Mobile 9.51b2, which always switched back to the standard keyboard on my iPAQ 210. Fortunately, I haven't run into the same problem with version b15233 any more.

2.4 Misc

This category, as you may have guessed, lists all the miscellaneous tests I didn't want to put in other categories.

Copy / paste: iPhone's Safari is heavily lacking copy/paste capabilities. In this regard, most WinMo web browsers are clearly better. Unfortunately, two (SkyFire and Opera Mini) of the three most recommended apps fail at this: they don't support copy/paste at all. (With Opera Mini, of course, you can still save the current page and, then, find and copy the given text from a simple text viewer like Total Commander.) As usual, with the other browsers, I've explained how you can switch to the text selection mode, as the default "screen dragging" mode, in general, needs to be disabled first.

Other goodies: I've listed some additional features I didn't want to create a separate row for: finding text in the current document (Iris, Opera Mini & Mobile, NetFront), Opera Link support etc. Unfortunately, SkyFire doesn't support finding in page - the only goodie it supports is image saving (also available with all the other browsers). Note that I haven’t listed all features of Opera Mobile: in addition to what the chart contains, it also supports sending image/links via MMS, SMS and E-mail. It even has a download manager that can even pause/resume a download – as has also been explained in my two-year-old article on downloading with Windows Mobile Web browsers.

DPReview top left menus: DPReview.com has a menu in the top left area none of the WinMo browsers can invoke subcategores of - unlike Safari. (An exception is Opera Mobile if you navigate over the main menu items with the D-pad - then, they don't get selected; still, their submenus are displayed, where you can already select anything. This means Touch HD users will need to use the custom onscreen keyboard displaying a virtual D-pad to fix this problem - not the cleanest solution...)

Page saving: the two Operas, Iris, NetFront and PIE, thanks to Spb Pocket Plus, are capable of saving the current page into the local file system. Unfortunately, the pretty barebone (but, still, excellent) Safari doesn't - neither does IEM6 (not that I'd recommend it to anyone) or SkyFire.

CPU usage: I've also benchmarked the CPU (and, consequently, the battery) usage of the tested apps (except for that of iPhone, as I don't know of anything like Windows Mobile's acbTaskMan for the iPhone. I may need to write it myself? After all, Unix does support getting the CPU usage of a given process.) NetFront has turned out to be buggy if and only if it's in the background. SkyFire has a continuous CPU usage: 40% while not doing anything (on the 624 MHz iPAQ 210). This may be quite much a stumbling block for many requiring as good a battery life as possible.

Dynamic zoom, only zooming into a given column: here, I elaborated on whether the browser supports the dynamic two-tap zooming in/out pioneered by Safari. The three most recommended titles work just great in this respect. Unfortunately, IEM6 has nothing comparable.

Clicks vs zooming: here, I explained how easy it is to click / activate links. With some browsers (for example, Iris), it's a bit harder to do this on most Windows Mobile phones, unlike you're using the D-pad and the action button to do this. Sometimes, you need to re-tap the same link some three or four times in order to activate it. This isn't an issue on the iPhone, where links do get activated at once.

Makes use of VGA?: as you can see, SkyFire will always use the 320*240 (QVGA) resolution to converse bandwidth, reduce the load on their servers and speed up screen rendering. This, unfortunately, results in a not-that-spectacular rendering quality on VGA screens. Opera Mobile's current Omnia b15233 rip, having come from a QVGA device, is VGA-unaware and, therefore, displays images (and, via Flash Lite 3.1, compatible videos) pixel-doubled, resulting in low-resolution images.

Quick(!) navigation to beginning of page: in cases, it might be very important to be able to navigate to the beginning of the page without having to waste some 10-20-30 seconds to continuously scroll everything up like mad. In this case, I've explained whether the browsers have a way of quickly doing this. As most current WinMo browsers (except for PIE, IEM6 and the non-native Opera Mini) no longer have a verticalscrollbar, this, in cases, may turn out to be very tedious. Of course, you can still avoid having to scroll all the way up by just reloading the page.

…end of page: unfortunately, getting to the bottom of a page can be even more tricky if a browser doesn't have a draggable scrollbar or hardware button / key shortcuts as simple page reloading won't help in this case. This can be a real pain in the butt if you want to quickly visit discussion threads where the (new) posts you'd like to see are at the bottom of the page.

A quick note: while the iPhone Safari supports quickly going to the top of the page, there's no support of doing the opposite, unfortunately.

Multitab/page: here, I explained whether the browser supports opening more than one tabs (windows) and, if it does, whether you can force the current link to be opened in that tab. The latter is really missing from the iPhone Safari. The fact that Safari always reloads the previous page when you tap the Back icon makes things even worse. Fortunately, it's still the fastest browser to download and render pages, even when compared to Pocket PC's that have an 1.5 times faster CPU, but still...

As you can see, of the WM web browsers that do support mutitabs (unfortunately, SkyFire isn't one of them; nevertheless, it's also very fast to reload previous pages as it just sends over the image of the current viewport to the phone, not that of the entire page), Opera Mobile lets the user to select whether the link should be opened in a new tab. Note that, by default, Opera Mobile only allows for 3 tabs; this, fortunately, can really easily be raised. Opera Mini should be also mentioned: it automatically opens the link in a new tab and only after opening 30 links (new tabs) does it start closing the previous ones.

Making use of memory : especially on memory-restricted devices (for example, most Windows Mobile devices only having 64Mbytes of RAM and running WM5 or later) and with browsers supporting multitabs can the memory consumption be of high importance.

Fortunately, the best (and most recommended) browsers (the two Operas and SkyFire) all have pretty low memory requirements, even with (with the first two) tons of tabs (web pages) open. Not so with Safari: in addition to it always reloading pages when you press Back, if you load a page in another tab, the Web page on the old one will be reloaded except when the page you loaded in the new tab was a small one.

Stability: as you may have heard, Safari's stability isn't the best: it often crashes, particularly upon loading large pages (for example, the comments at the old [before the recent switch] iPhone Dev-Team Blog). Yes, this is indeed the case, even with the latest, 2.2 firmware. Fortunately, it remembers (and quickly and automatically reloads after restarting it) the last page you were on - or the one before, so, this issue isn't that bad.

In general, I've found the stability of all the tested WinMo browsers significantly better than that of the Safari. Another thumbs up for using Windows Mobile for Web browsing. (Now, I can only hope there were WinMo phones with capacitive touchscreens not requiring any kind of physical force when scrolling or doing stuff!)

Flash support?: as has also been explained in my earlier articles (particularly the one on the Flash Lite 3.1 hack and in my Flash bible), you need Flash or Flash Lite support to play back (most) Web videos, play games etc. Safari, again, is really bad at this: all it offers is playing back most YouTube videos but doesn't support Google Video (and the other, less relevant ones like blip.tv and PornoTube) at all. (Note that not even its YouTube support is as full as that of Flash Lite 3.1. For example,

video can't be played back in Safari. Furthermore, it doesn't play back stereo videos in stereo like
either, which is played back without problems by Flash Lite 3.1).

As you can clearly see, the current, hacked Flash Lite 3.1 is only compatible with the latest (b15233) Opera Mobile version (but not the official 9.51b2) - and not on all devices. (It worked OK on my HTC Wizard and HP iPAQ 210 but not my HTC Universal with Tomal 8.5.) SkyFire supports even the latest, desktop Flash (as it's running on the central server) and PIE only supports the old and pretty much useless, full Adobe 6/7 plug-ins (and the even more useless Flash Lite 2). NetFront, unfortunately, isn't a tad better either because of its sub-par Flash engine, which is even worse than the native Pocket PC Adobe 7 support.

Full screen?: finally, I elaborate on whether the browsers can use the entire (full) screen estate. Most of them can; the two exceptions being Iris (which will always display the bottom bar) and iPhone's Safari.

3. Verdict – will I switch back to WinMo from iPhone Safari?

As has already been mentioned, the three most recommended Windows Mobile browsers (Opera Mobile, Mini and SkyFire), generally, are more featureful, stable (no crashes) and compatible (see for example the PPCT or the ThinkPads test cases) than iPhone Safari. The latter, however, is definitely faster at both loading and scrolling pages than any of these browsers (unless you want to do some special kind of scrolling; for example, going straight to the end of a page, which is very easy in Opera Mini.) If you can live with WinMo browsers loading your pages slower, you may want to prefer them to the iPhone.

This was strictly about the software part. As far as the hardware is concerned (and my switching back to WinMo to browse the Web), the advantage of the capacitive touchscreen of the iPhone pretty much negates the software superiority of particularly Opera Mobile. It’s just far easier to scroll and control the iPhone Safari than any of the browsers on any(!) of my Pocket PC’s and Pocket PC phones. (I’ve, in this regard, tested the following Pocket PC’s with Opera Mobile 9.5: Dell Axim x51v, HTC Wizard and HP iPAQ hx4700 (all three with a high-quality, expensive [brando] screen protector) and HP iPAQ 210 and the HTC Universal (both without a screen protector) so that I can have a picture of how each of these models, with varying force needed to make screen taps / drags registered, fare. (Yes, I did test at least Opera Mobile 9.5 on five different WinMo models and the rest of the browsers on at least one [mostly the iPAQ 210, except for IEM6, which, currently, is only available in flashable ROM images and not as freey installable CAB files] of them) It was painfully harder to scroll around a page on all(!) of them. While I have a screen protector on my iPhone 3G as well, even with it, it’s way easier to scroll around. In this regard, the Safari (that is, browsing the Web on the iPhone and not any of the current WinMo models) is simply unbeatable. (Note that I use the screen protectors that come with the Switcheasy Rebel cases; according to THIS thread, they’re Pure Reflects. They make screen taps just a little bit harder to register and make the surface a bit less slippery, meaning it’s a little bit harder to drag the screen with the screen protector on. Nevertheless, the touchscreen interface still remains orders of magnitude easier to use than any of resistive WinMo models I’ve ever tested or had.)

All in all, while I’d prefer using Opera Mobile on Windows Mobile because it’s more powerful and stable, the fact that scrolling around pages is way harder than on the iPhone, I’ll stick with the latter. I’m afraid I’ll only change my mind if and when Windows Mobile hardware manufacturers, at last, come up with real capacitive screens, as easy-to-use (even through screen protectors) than those of iPhones. Hope the Microsoft folks are listening…

If you "only" have a Windows Mobile device and, consequently, must select from the browsers available for the platform (and can't go for the iPhone instead), selecting the right one should be based on your personal preferences. In my opinion, Opera Mobile (particularly when backed up with Flash Lite 3.1) is the best. However, if you absolutely must have a browser that either supports Opera Link (Opera Mobile, currently, doesn’t) or have the lowest available data usage figures, go with Opera Mini. It’s not as spectacular as its big brother (there’s, for example, no copy/paste or “inertia” support) but still does what it’s meant to – and it’s free.

SkyFire is, on the other hand, a perfect choice if you have a QVGA device (or a VGA one, but the QVGA-resolution text / image rendering isn’t a problem), have an unlimited Internet subscription (its data usage is far higher than that of even Opera Mobile, let alone Opera Mini) and the much higher CPU usage (and, consequently, battery consumption) aren't an issue.

UPDATE (01/05/2009 3:33 AM CET): I’ve cleaned up the article a little; for example, added a Verdict section. I've also very thoroughly explained the evaluation of the tested browsers largely reflects on how they're able to render text with large® characters, NOT the overall rendering fidelity / quality. After all, one of the main aims of this article is explaining which of these browsers can be used when you simply can't use small characters on a VGA screen because you're either moving, the screen physically is just too small (2.8...3") or you have bad eyesight. I’ve also added some explanation of why the current, “hacked” IEM6 version (hopefully) isn’t a representative of the final one Microsoft will release some day. (They have a lot of time bugfixing it and they too surely realize IEM6 is plain useless in many usage scenarios like the one requiring large® characters.)

There’s a frontpage of the article at WM Power User.

Link to comment
Share on other sites

Guest Menneisyys

UPDATE (01/05/2009 3:33 AM CET): I’ve cleaned up the article a little; for example, added a Verdict section. I've also very thoroughly explained the evaluation of the tested browsers largely reflects on how they're able to render text with large® characters, NOT the overall rendering fidelity / quality. After all, one of the main aims of this article is explaining which of these browsers can be used when you simply can't use small characters on a VGA screen because you're either moving, the screen physically is just too small (2.8...3") or you have bad eyesight. I’ve also added some explanation of why the current, “hacked” IEM6 version (hopefully) isn’t a representative of the final one Microsoft will release some day. (They have a lot of time bugfixing it and they too surely realize IEM6 is plain useless in many usage scenarios like the one requiring large® characters.)

There’s a frontpage of the article at WM Power User.

Link to comment
Share on other sites

  • 1 month later...
  • 4 months later...
Guest Menneisyys

Following is my just-published roundup of current Web browsers under iPhone OS 3.0 with WM-related remarks as well. A goldmine for Windows Mobile browser developers – it’s always worth knowing what browsers on other mobile platforms are capable of, what features Windows Mobile lacks etc.

The One and only Real iPhone Web Browser Roundup

While the iPhone’s built-in Web browser, Safari, is a pleasure to use, it still has some missing functionality. Some of these:

- Full screen mode (browsing the Web without the upper and lower status and command bars taking up any screen estate)

- Orientation locking (to avoid Safari changing orientation when you move or turn your phone)

- An easier way to switch between open pages (now, it requires sometimes several taps / swipes to switch to another opened Web page)

- Background Web page loading (to avoid having to wait for a new page to be opened while going on reading the current one)

- Allowing for more pages to be open without having to continuously reload them (albeit Safari in the latest, just-released iPhone OS 3.0 certainly helped this)

- Configurable Web search engines

- To be able to quickly scroll to not only the top, but also the bottom of the page (for example to check out the latest posts in forums, blogs)

- Providing "faked" User-Agents to make Web servers think you’re accessing them from desktop browsers, and not an iPhone-based one

- Viewing page source

- Disabling image loading in order to speed up page loading times and drive down data use

Enter third-party Web browsers, which allow for the above. Let’s take a closer look at them – particularly because the existing, pre-OS3 roundups are heavily outdated – some of them have been published as early as this January – and no longer contain useful information.

First and foremost, as in my previous Web browser bibles for mostly Windows Mobile (see for example THIS), you’ll find most of the information you’ll need to know in the comparison & feature chart available HERE. It’s quite a huge one, so, it’s worth either printing it (in landscape mode) or viewing it on a desktop computer with as huge a screen as possible. After a quick introduction and evaluation of the reviewed browser, I devoted quite a lot of time to explaining what each row in the chart means and how the reviewed browsers behave in that respect. It’s in there that you’ll find a lot of additional information and tips.

First and foremost, there aren’t browsers for the iPhone not depending on the Safari / WebKit engine. What does this mean? There’re some fundamental restrictions (still, as of OS 3.0) plaguing Safari and, accordingly, all browsers based on it. The most important being the lack of text reflowing capabilities allowing for nicely reflow the text when you zoom into a page with pinching. Some other browsers (for example, later Opera Mobile 9.5+ versions) on other mobile platforms (in this case, Windows Mobile) do offer this functionality. This, unfortunately, also means there will still be some Web pages or forums almost impossible to read with Safari. Some of the examples are listed HERE (see "2.1 Real-world rendering tests"), in my article on how Safari compares to Windows Mobile Web browsers (and the multiplatform Opera Mini); for example, THIS Thinkpads.com thread.

Similarly, there isn’t full Flash (Lite) support either, something already existing on Symbian S60 (Flash Lite coming bundled / pre-installed with the Web browser) and Windows Mobile (a "hacked" version of Flash Lite 3 can be installed in some later Opera Mobile versions). This also means no online YouTube-alike works with iPhone OS 3 – not even the ones that do work with the Flash Lite 3-enabled Windows Mobile or S60.


The built-in Web browser in the iPhone is still the most recommended one unless you have some special needs, which I’ll explain later. For example, unless you’re absolutely fed up with

- the always-visible top and bottom bars taking up some (but not much, contrary to what some developers state) screen estate or the

- inability to easily open and load pages in the background or the

- limited number of pages you can store in-memory (as opposed to some other and, in this respect, better browsers) or the

- inability to just download files (of types handled by the iPhone) into the file system – it will only pass the online files to the respective handler application in streaming mode, which, in most cases, won’t allow for saving.

These aren’t the only problems with Safari – when going over the feature chart, I’ll explain more of its shortcomings.

Nevertheless, if you can live with the problems of the browser, I recommend it the most as there simply isn’t a worthy contender to it. It’s only very rarely that you will want to switch to an alternative browser to, for example, quickly download some files into the file system of your iPhone so that they can later be read / played back / sent to another computer / Internet-enabled phone without having to download them again or you really need to keep as many tabs open as possible.

Note that there’re a number of welcome fixes and additions in iPhone OS 3.0. First, it’s definitely better when it comes to handling memory (but in no way as good as some of the alternative browsers). It also allows for opening links in a new tab (if you don’t just quickly tap a link, but tap-and-hold for about 1 second) – something that has been sorely missing from earlier versions. Nevertheless, it still lacks some essential features like full screen mode or background page loading.

Now, let’s take a look at the alternative browsers produced by independent developers. Again, note that I only provide a quick evaluation / introduction here; it’s in the feature chart that I elaborate on all the features, advantages and disadvantages of each browser and compare them to the alternatives.

iCab Mobile 1.5

Feature-wise, it’d probably be the best browser of the bunch if it was more stable. Too bad it frequently crashed on both my testing environments (iPhone 3G with 2.1.1 jailbroken and 3.0 non-jailbroken), which makes it pretty much useless because of the constant restarts.


It allows for tweaking a lot of its parameters as can also be seen in the following two screenshots, taken from the first and the second half of the Settings dialog:



A screenshot of the Bookmarks dialog. As you can see, it’s also one of the very few browsers to support folders:


It’s also one of the very few browsers to allow for opening a page in a background page:


Air Browser 1.1

While this browser has some unique goodies (quick scroll up and, particularly, down to top/bottom-most; find in page), the exceptionally bad memory handling and the lack of real full screen makes it far less desirable than OS3’s Safari or some other 3rd party browsers. A screenshot also showing the only menu it has:


Also note that the menu has "Find in page" – too bad most other browsers (except for Safari, which allows for running scriptlets implementing this) lack this essential feature.

It’s one of the very few multitabbed browsers to have a list of the tab immensely helping finding the one you want (instead of swiping through pages until you find the one you want, sometimes with multiple swipes, as is in Safari):


Also note the two arrows at the bottom middle – they allow for quickly moving to the previous / next page.

VanillaSurf 1.2

This browser isn’t bad; what I miss the most is background page opening capabilities and quick top / bottom scrolling. As it has never crashed on me, probably the most recommended browser if you do want both full screen and multipage support – for $1 only.


Too bad it uses Safari’s approach for selecting the page you want, and not a much denser, one-page list for much quicker selection:


It has no background loading capabilities either – and the lack of support for quickly scrolling to the top / bottom of the page is really annoying.

Its settings dialogs are as follows (as you can see, it’s packed with a lot of goodies):



CaizerWeb 1.0.2

The very ugly scrolling / dragging makes this title (which, otherwise, would be pretty nice) in no way recommended


Journey Web Browser 1.0

Pretty good and capable Web browser; too bad the scrolling speed / stuttering can be a real pain in the back. Therefore, not recommended.


BigBrowser+ 1.1

If you MUST store the downloaded files on your phone and make them accessible to an external computer, you’ll want to turn to this app.


File downloading in progress. Unfortunately, background downloading isn’t supported


As with all the other browsers, unsupported files (ZIP, WMV etc) can’t be downloaded.


Built-in file viewer; at the bottom, you can see the address you need to connect to from an external browser to be able to access / download your files / pages.

fgBrowser 2.5

It would be nice if and only if it supported multiple documents.

Main menu view:


Favorite / history view; as can be seen, it supports ordering history items really nicely:


iBrowseTwo 1.1.0

Really-really incapable: not even landscape is supported. Don’t bother.


The only menu it has (address input):


Mini Browser 1.0

Don’t bother.


(with the main menu maximized)


(and with it minimized)

QuickSurf 1.2

Really nothing to write home about – except for it not loading / displaying images (which is also supported by some other browsers – but, of course, not Safari):


Multi-Full Browser 1.1.0

Another very weak title.


(four pages at the same time)


(and after switching to two)

A more thorough comparison and explanation of the chart

Now, let’s take a closer look at the chart. Note that in order to make the most out of this section, you’ll want to open the chart in a separate tab / window so that you can avoid scrolling.

Landscape support?: The first row of the group explains whether a given browser supports switching into landscape orientation at all. As you can see, not all do; for example, (the, otherwise, not recommended) iBrowseTwo (at least in its current, 1.1.0 version) and the absolutely rubbish Mango Browser are incapable of Landscape. The non-recommended "Wide Web with Twitter" doesn’t depend on automatic orientation change (unlike the other, Landscape-capable browsers) – you must manually switch orientation.

Lock orientation?: several third-party browsers support locking the (current) orientation. While Safari does allow reading Web pages in bed in landscape orientation while you’re on your side (if you make sure the side with the speaker is down, and not the other one – that is, the side with the Home button),

1. some browsers allow for dynamically changing orientation in all the four directions (not just three, as is the case of Safari and practically enabling in-bed, on-side reading without any orientation locking). This also means you can’t use them in situations like the above (you’d want to browse the web while you’re lying on your side).

2. You’re doing some physical exercise (running, bicycling in a gym etc), or just can’t continuously browse; for example, you’re talking to someone or walking the street and, consequently, you often put your phone in your pocket for a moment. To avoid the constant switching between the portrait and landscape orientations (and the waiting a bit for the orientation to restore when you take your iPhone back to your hands), you might want to disable automatic orientation change.

In both these cases, locking the orientation can be of immense help.

Tab / multidocument support: It’s very important, particularly over slow(ish) and/or expensive connections or on slow(er) devices, that you can keep as many web pages open as possible.

For example, when you encounter a link you’d like to follow on a Web page, when you return from it, Safari reloads the previous (original) page, which may take quite a lot of time (and data use). In this case, it’s preferable to open the link on a new tab (of which the Safari has 8) and, by forcing it to load the page in the new tab, don’t let the iPhone "forget" the original page.

There are two major groups of 3rd party browsers: ones that allow for multipage / multitab work, and ones that don’t. Unless you really don’t want to use multitabs (because the additional time / data usage doesn’t annoy you), you’ll want to go for browsers belonging to the former group. You, in addition, will want to learn how to use these features as efficiently as possible to minimize page switching and wait-until-page-is-loaded time. As usual, there’s a "+" sign with browsers supporting multiple tabs (windows) open at a time and a "-" sign with ones that don’t.

How many taps to switch between tabs?: if you do use multiple tabs, it might be very important to be able to switch between them as easily and quickly as possible. On tabbing-enabled desktop Web browsers, for example, all you need to do is either pressing Crtrl-Tab or just clicking the tab in the upper command bar of the screen. Of course, on the iPhone, there’re no keyboard shortcuts and, because of the limited screen estate, there aren’t visible tab thumbnails either. That is, you will always need to issue sometimes multiple screentaps to switch between tabs (open documents).

Some browsers, while (to conserve screen estate; that is, not to take up 20-30 additional vertical pixels to display the list of tabs) they don’t display the title of each tag, provide one or two arrows to quickly switch between tabs. These allow for one-tap switching between consecutive(!) tabs. Some others have gestures (for example, double swipes to the left / right as in Journey Web Browser 1.0) to do the page switching. Others allow for a quick list of tab titles upon tapping an icon. These, therefore, allow for switching pages with two taps. Finally, the built-in Safari (and several third-party browsers) only allow for page switching requiring much more taps and swipes. An example: if you have six tabs open and you’d like to open a seventh from tab one (the leftmost one in the tablist), you’ll need to swipe the tablist right several times to get back to the old tab. This isn’t at all elegant or easy – the approach taken by the "tab title list on one screen"-enabled browsers is certainly superior.

An example of an, in this regard, vastly superior browser, Air Browser:


As you can see, it both has a quick tab title list (one tap to activate any tab) and two dedicated arrows for switching to the previous / next tabs.

Open links in background tabs (no need to switch back to continue reading the current page while the other is still loading): currently, as of iPhone OS 3.0, you can only open links in new tabs when you long-tap (about one second) a link:


(Note that this is only available in OS 3, not in previous versions!)

That is, there’s no way to instruct Safari to open the link in a new, so-called background tab, which would allow for staying in the current document (going on reading it) and only switching to the new page when you’re absolutely sure it has fully been loaded. This way you can save a LOT of time if you take into account that pages, in general, require several seconds to load / render. For example, I always (try to) switch back to the original page when doing this – which, in Safari, requires a LOT of screentaps.

More advanced browsers like iCab Mobile have a link tap context menu item "Open in background tab". If you tap them instead of "Open link normally / in this tab / in a new tab", you both preserve the current document (no need to reload it when you return to it AND you can continue reading it while loading the new page in the background) and don’t lose time waiting for the new page to load (staring at the empty or partially rendered screen) or switch back to the current one:


Unfortunately, very few other browsers support them same. Mostly because of this feature, iCab Mobile, which has a lot of other goodies, would be one of my most recommended browsers if it didn’t crash so frequently.

Default "open to" definable?:

In some browsers, should be there no way of deciding for each (tapped) link where they should open, you can define where, by default, they should open their content to. For example, VanillaSurf 1.2 lets define in Settings:


So does iCabMobile:


If you set this, you don’t need to select all the time whether to open the new page to the current or a new tab.

Memory use: does it keep all opened pages in memory; test suite results : in order to make real advantage of multitabs, you also need a browser with good memory handling.

If you’ve ever used multiple tabs in pre-OS3 Safari, you know why: in previous operating system versions, Safari notoriously killed the contents of opened tabs if the new one was larger than a specific threshold. (With the Safari in OS 3.0, this problem is still existing but seems to be far less pronounced – nevertheless, some 3rd party browsers still fare much better in this respect.)

In order to make the test as strict and reproducible as possible, I’ve used my old Web page I’ve purposefully made for memory usage and page load time measurements for my previous Web browser reviews and roundups.

This Web page is almost 600 kbytes long. I’ve created multiple copies of it to avoid "caching" and browsers’ only using one memory representation for all tabs instead of one for each tab; just change index.html to index2.html, index3.html … index6.html to access them.

In order to find out how many tabs can coexist, I’ve opened as many instances of these Web pages in different tabs and, after fully loading each tab, I’ve iterated over the previous ones to see whether they still have the Web page, or, do they start reloading pages. As you can see, in this respect, by far the worst (multitab-enabled) browser is Air Browser 1.1; all the other was able to keep much more pages in memory. Unfortunately, the new, OS3.0 Safari is in the lower half of the bunch (with only four pages), while some of the alternatives (most importantly, VanillaSurf) had no problems keeping eight pages in memory.

At the same time, I was also able to find out how many pages are needed to "crash" a given browser. Unfortunately, several, otherwise high-quality browsers (iCab Mobile 1.5, CaizerWeb 1.0.2 and Journey Web Browser 1.0) crash when you "overburden" them with too many tabs / mmory-consuming Web pages open.

No, don’t think, based on the test page’s length (600 kbyte) and consequent memory needs (which is, according to my measurements on the Windows Mobile platform, can range from 2 to 16 Mbytes – that is, much larger than the original HTML page itself), you can safely use these three browsers to browse only few, smaller Webpages concurrently. The figures I’ve provided only show when the browser crashed in a well-controlled environment with known Web pages. Upon casual browsing far smaller(!) pages, I’ve encountered frequent crashes too (far more frequent ones than Safari crashing – it still does! – under OS3), pretty easily ruling out these three browsers. On the other hand, VanillaSurf 1.2 has never ever crashed on me. Too bad it lacks some essential features…

Test page loading time: along with the memory usage tests (loading the large test suite), I’ve also benchmarked it loading the page in the first and, then, second, third etc. tabs. I’ve found out that loading the page in the first tab takes far more time than in the consequent ones; for example, with iCab Mobile, 18 seconds for the first page and between 7 and 8 seconds for subsequent ones (hence the 18/ 7…8 listed in this row). This must have been caused by the test pages, while physically different (and, therefore, loaded separately), sharing the same image resources. That is, the latter didn’t needed to be fetched again.

As you can see, interestingly, Safari has turned out to be the worst-performer of the (multitabbed) bunch. This means the related promotions (see for example BigBrowser+’s iTunes page and ad) are indeed true: if a developer states his or her browser can load pages faster than Safari, then, he’s indeed right.

Can you select where to open it in some kind of a runtime context menu?: when discussing Default "open to" definable? above, I’ve already explained some browsers (including Safari starting with OS3 – but not before) allow the user decide where a tapped link should be opened.

The ways of activating this context menu is different. For example, with Safari, a single, short tap opens the page in the current tab (unless the link forces the browser to open it in a new one), while a long (about one second) tap brings up a context menu where you can select whether you want to open the page in the current tab or a new one – or, alternatively, whether you want to copy the link address.

On the contrary, in iCab Mobile 1.5, you need to use short-taps (and not long ones!) to activate the full context menu of the browser (as long as you’ve set "Ask" for the default link target in Settings). If, on the other hand, you tap the links continuouy for at least one second, you’ll be presented Safari’s own menu, without the option to open the page in a new tab.

Titles of all tabs easily accessible?: I’ve shown how Air Browser 1.1 makes it easier to select the tab to switch to (as opposed to the several-taps-and-swipes-needed Safari approach). In this row, I elaborate on how the browsers behave in this respect – that is, do they have easily accessible and selectable lists of tabs.

As you can see, Air Browser 1.1, iCab Mobile 1.5 and CaizerWeb 1.0.2 are the best in this respect. VanillaSurf 1.2, the most recommended browser (because of its stability, not because of its feature set, in which it is definitely worse than some of the other browsers!), unfortunately, uses the same slow and awkward interface as Safari.

Max. number of tabs: here, I’ve listed how many tabs the browser have. As can be seen, (multitab-enabled) browsers generally support several tabs; the two exceptions being (the, otherwise, in no way recommended) iBrowseTwo 1.1.0 and Multi-Full Browser 1.1.0.

The Search group elaborates on local / global searching support. Its first row, Find in page? If not, compatible with my scriptlet?, tells you whether you can have the same functionality as Ctrl-F in esktop browsers. It might be very important to find a certain word on a huge Web page. Find in page, when implemented, allows for this.

Unfortunately, few browsers have this functionality – the biggest names (for example, VanillaSurf and Safair itself – while iCab Mobile does support it) don’t.

Every cloud has a silver lining, though – with Safari, you can enable this functionality with so-called "scriptlets". Please see THIS for more info and how they should be used.

Built-in Web search engine support?: in Safari, there’s a text input field to the right of the address input bar, which provides you with an easy way to quickly issue Google (or, if you reconfigure it in the system-level Settings, Yahoo) searches without having to go to Google (Yahoo)’s homepage first. Here, I’ve listed whether the browsers do the same.

Favorites: Access Safari favorites?: The new, Favorites group explains how the browsers handle favorites. Some don’t even have any favorite support (you will want to avoid these altogether), some are pretty advanced.

The first row in this group, Access Safari favorites?, explains whether the browser is able to operate on Safari’s own favorites (none of them are, except for, of course, Safari itself). In this row, I’ve also explained some of the niceties; for example, iCab Mobile’s excellent capabilities (export / import and reading the system-level Contacts database).

Bookmark name editable?: you, at times, may want to store a favorite with a modified name (not bearing the title of the page). Here, I explained which of the browsers are capable of this.

URL editable: you may also want to edit URL’s themselves. At first, this doesn’t seem very important. However, if you take Javascript scriptlets into account (see the link in Find in page? If not, compatible with my scriptlet? above for more info), this may become REALLY important.

Favorite folders?: examines whether you can define subfolders. Note that some of the browser that, otherwise, allow for subfolders, only allow them in the depth of one – I’ve also elaborated on this in the chart.

Support for reorganization?: when you have too many items, you might want to reorganize them – for example, bring the most used ones (along with, if you do use them, "find in page", "bottom of the page" etc. scriptlets) to the top so that you can quickly access them without having to scroll down a lot.

In addition to Safari, of the higher-quality titles, iCab Mobile 1.5, CaizerWeb 1.0.2 and Journey Web Browser 1.0 support this kind of functionality. Reorganization is done in exactly the same way in all these browsers: you tap-and-hold the icon (the three horizontal lines stacked) on the right of the favorite and, then, drag the record to its new position.

History? : This group lists whether there’s support for history (user-input addresses) and whether the stored data is actively used when you enter something starting with the same of containing some substring (URL autocomplete based on history?) and you can delete the history data (Clear history?), should you not want people see what pages you’ve visited.

Scrolling : Scrolling smoothness?: the Scrolling group elaborates on issues with scrolling. The first row in this group, "Scrolling smoothness?", elaborates on whether scrolling is smooth.

Unfortunately, all third-party browsers are definitely worse than Safari in that the scrolling, to some degree, stutters on them. The difference can be very small (as is the case of iCab Mobile 1.5 and VanillaSurf 1.2). Some (otherwise, high-quality) browsers, unfortunately, exhibit pretty bad scrolling stuttering; the most important examples of them are CaizerWeb 1.0.2 and Journey Web Browser 1.0. You’ll want to avoid them entirely if you find this problem really annoying.

Quick scrolling to top / bottom of document?: on the iPhone (as opposed to some other, touchscreen-enabled platforms like Windows Mobile Professional / Classic), there’re no draggable scrollbars to quickly scroll up / down to the top / bottom of the page (or, for that matter, anywhere inside the page). If you know Opera Mini on compatible platforms, you may also remember that it also offers quick scrolling to the top / bottom on non-touchscreen platforms too with repeated pressings of #3.

With Safari (and some other 3rd party Web browsers), you can quickly and easily browse to the top of the page by simply single-tapping the top of the screen. The opposite of this (quick scrolling to the bottom), however, is only implemented in very few browsers – and, unfortunately, Safari isn’t one of them.

Again, my scriptlets to the rescue! As is explained in the (first) UPDATE section of THIS article, you can easily create a scriptlet, which, when activated, quickly scrolls down to the bottom of the page.

Cookies: Clear cookies?: some browsers allow for clearing cookies, should you be afraid of privacy issues.

Fine-tuning acceptance?: In addition, Safari allows for fine-tuning (in the system-level Settings menu) them.

Misc.: Interrupting page loading?: the first row of the Misc. (miscellaneous) group concentrates on whether you can interrupting (stop) loading a page. Say you only need the text of a page and, when it’s already rendered, you want to stop loading the in-line images. If the browser doesn’t support this, you’re shot.

Full screen?: the built-in Safari doesn’t support full screen mode (not even in OS 3.0). This is the problem that made most 3rd party browser developers embark on developing their own browsers.

In this row, I elaborate on whether the full screen mode (if supported) is really full screen mode (where you can exit from either shaking the phone or, as with fgBrowser, some special three- or two-finger gestures) or one where you’re still shown icons to exit the full screen mode. Of course, you may want to prefer browsers that offer true full srcreen mode. As you can see, again, iCab Mobile is the best in this respect – it doesn’t display any icons and entirely operates based on shaking.

Remembers last visited page(s) upon relaunching?: some Web browsers automatically reload the last page (or, when in multitabbed mode, even pages – as is the case with VanillaSurf 1.2) when you relaunch them.

Interaction with Safari (passing a link to / receiving a link from): in cases, you may want to pass the address of a given page to Safari so that you can continue browsing the Web in that browser. (The opposite is true in very few cases.) Note that, now with OS3’s supporting copy/paste operations, this isn’t that important a functionality any more.

User-Agent faking?: in some cases, you may want to "fake" your User-Agent HTTP request header telling the Web server you’re browsing pages from you’re from another Web browser, not Safari on the iPhone. Very few Web browsers support this.

Nevertheless, if you really need this functionality with, say, Safari, you can use third-party some sites effectively changing your User-Agent – which is also a widely used practice of Opera Mini users.

File download?: in Safari (and most 3rd party browsers), when you tap a link pointing to for example a PDF, DOC, MP3, MP4 or other file otherwise supported by iPhone (that is, the phone can play it back or render its contents), it will invoke the application assigned to the particular file type straight away – without storing the files in the file system so that you can, later, play it back without having to download it again.

Of the tested browsers, only one (BigBrowser+ 1.1) is able to not only "Open" (see the above-explained, default functionality), but also "Save" these files into the file system. (This browser, otherwise, is pretty basic; I only recommend it for file saving.)

View source?: only one browser (Journey Web Browser 1.0 ) makes it possible to view the source of a Web page.

Copy-paste?: back in the pre-OS3 pages, probably the most important feature missing from the operating system was copy/paste. This was of special interest in the Web browser, as it’s mostly there that you may encounter text you’d like to quickly paste into your notes or mail.

Before OS3’s radical changes, you only had two ways of fixing this: first, mailing the address of the current Web page (this is supported by almost all browsers, including Safari), or, going for the very expensive ($6) and, comparatively, weak Magic Browser (iBlueAngel) – the only Web browser to have reduced (it’s only able to copy full blocks of texts and to mails and the address bar only) copy/paste support. If you were lucky enough, with some kinds of content, you could use third-party scriptlets: for example, if you needed copy/paste functionality to convert non-HTML links to HTML ones (so that they become activatable and can be followed) with, for example, the Linkify scriptlet HERE.

Can image loading be disabled?: particularly when you’re on a slower connection or you need to reduce your data usage (images can eat up pretty much data), you may go straight for a client that supports disabling images. The majority of third-party browsers do so; unfortunately, Safari doesn’t.

Offline browsing?: there’s one browser that allows for automatically reading back the pages that were open last time you have exit: VanillaSurf.

Note that the two browsers that allow for Web page saving (BigBrowser+ 1.1 and Magic Browser (iBlueAngel) 2.5) also allow for this – to some degree: they don’t save images.

Save web pages?: See the above explanations about saving a Web page so that it becomes offline.

Auto forms fill-in?: another welcome addition in the OS3 Safari is the form autofill. In order to have an idea of other mobile browsers’ supporting the same, I need to point out that none of the Windows Mobile Web browsers have the same (except for, probably, SkyFire, which I haven’t tested in this regard so far), and the same stands for the BlackBerry and Symbian S60.

https support? (ebay test): some Web browser developers state there’s no HTTPS (Secure HTTP) support in some browsers. This is why I’ve run a HTTPS test too with eBay (and, at the same time, I was able to test whether cookies are retained over browser restarts). All the browsers that I’ve tested in this regard turned out to be supporting HTTPS.

Input keyboard: the one with ".com"?: one browser (Magic Browser (iBlueAngel) 2.5) present the user an on-screen keyboard not specially tailored for entering Web addresses; for example, it lacks the .com button.

Ad filtering?: some browsers support ad filtering. The most important of them is iCab Mobile 1.5, which allow for even manual editing of filters – excellent!

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in

Sign In Now
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.