Menneisyys
05-20-2008, 08:51 PM
As yet, I haven’t had the chance to give SkyFire, the latest Web browser a thorough try. Fortunately, I’ve recently got an account and could, at last, test it.
SkyFire is a client/server Web browser for both Windows Mobile platforms: touchscreen-enabled Pocket PC’s (in WM6+ parlance, Windows Mobile Classic and Pro devices) and touchscreen-less MS Smartphones (Windows Mobile Standard). It utilizes image-based transfer, just like the (cancelled) DeepFish and some non-Windows Mobile-based solutions like PocketSurfer 2 (http://www.pocketpcmag.com/cms/blogs/3/mwc_web_browsing_webkit_thunderhawk_news).
Please note that this is NOT an in-depth review but a comparison to the other browsers out there. It’s immensely more useful for both end users (so that you can decide whether it’s at all worth getting an account or just wait for later versions) and the developers themselves. This also means you’ll want to read my past Web browsing-related articles to understand everything in this article as, at times, I’ll switch to „geek speech”. Start with my W3C presentation (http://www.pocketpcmag.com/cms/index.php?q=blogs/3/2625) and follow the links back to, say, the Web Browsing Bibles. Also, search for „SkyFire” on my blog to find my earlier SkyFire-based posts – I’ve linked to several forum threads discussing the browser. In addition, In addition, I also recommend BrightHand's generic overview (http://www.brighthand.com/default.asp?newsID=13761) of the app - it offers a gentle introduction to SkyFire's capabilities, while, as has already been stated, my article is strictly a comparative, technical "geek speech" review targeted at more experienced Web users.
Note that the tests have been run on the latest 0.6.0.4503 version.
http://www.winmobiletech.com/052008SkyFire/SkyfireMain.png
A screenshot of the main menu (http://www.winmobiletech.com/052008SkyFire/SkyfireSettings.png); the Settings menu (as you can see, there aren’t much to set) is shown HERE (http://www.winmobiletech.com/052008SkyFire/SkyfireSettings2.png).
Pros
- It uses the Firefox 2.x engine, which is clearly better than Internet Explorer, even as of version 8. That is, it’s just much more standards-compliant than IE-based client/server mobile browsers like PocketSurfer 2
- It works flawlessly over any kind of Internet connection; not just U.S. mobile phone operators (unlike what the SkyFire folks state – and the popular belief). The latter is only needed for registering for the first time. Fortunately, after moving to another country and even swapping your SIM card / switching to another device (from a, say, CDMA(2000) to a GSM/WCDMA one) , you can go on using your account: for re-activation on another phone, you won’t need to have an active U.S. phone number any more.
- web standard compliance-wise, pretty good, including even Ajax
- high-quality and high-compliance Flash and Java support (strictly in client/server model; sound emulation may not work on some models)
- URL history (as with most other browsers, though) (http://www.winmobiletech.com/052008SkyFire/browsinghistory.png)
- Acceptable forward caching of approximately the following page (better than DeepFish used to be or that of PocketSurfer 2)
- The SmartFit mode works pretty OK and intelligently; I haven’t ever run into a situation when it didn’t failed to eliminate the need for horizontal scrolling. In this regard, it should be compared to Opera Mini 4+’s equally advanced text reformatting / reflowing algorithm in non-mobile view, (on non-high-res devices) zoomed in mode.
- In zoomed in mode, the cursor keys can be used for touchscreen-less link selection (and for scrolling in the four directions); in zoomed out mode, you can use it for scrolling the zoom-in window. That is, you don’t necessarily need to use your Pocket PC in two-hand mode – as is, of course, the case with the MS Smartphone (Windows Mobile 6 Standard) client.
- Compared to DeepFish: immensely better and faster. The only advantage of DeepFish was the support for hi-res on hi-res devices.
Cons:
- huge CPU usage when maximized (58% on a 624 MHz Xscale PXA270) independent of page contents (http://www.winmobiletech.com/052008SkyFire/HalfScreenAndCPUUsage.png) (that is, it'll happen even with no Flash / animation taking place). When minimized, no CPU usage.
- no support for multiple tabs (documents), unlike in most comparable browsers. This means you’ll need to always reload a page, should you want to return to it and can’t just switch quickly (back) to other/older pages.
- no hi-res (for example, VGA) support – not only as far as the low-res contents is concerned, but also when rendering input fields; then, its coordinates will be effectively halved on a high-resolution screen (http://www.winmobiletech.com/052008SkyFire/VGAtexInputFields.png). Fortunately, this doesn’t cause much problems with most pages.
- zoomed-out state provides pretty bad resolution / intelligibility (example HERE (http://www.winmobiletech.com/052008SkyFire/ZoomedOutScreenResNotVeryGood.png); incidentally, it also shows a message window showing a „connection lost” dialog)
- if you switch to another program and, then, back (with, say, an overridden app button), there are chances only half the screen will be used. A HTC Universal screenshot is HERE (http://www.winmobiletech.com/052008SkyFire/HalfScreenAndCPUUsage.png)
- much as there’re (non-standard) scrollbars on the right / bottom edge of the screen (example HERE (http://www.winmobiletech.com/052008SkyFire/Scrollbars.png)), they can’t be used to quickly position in the docs (the same problem as with Touch Browser)
- no page / link / image saving - of, for that matter, any kind of link / image context menus
- not any kind of copy/paste (however, you can copy / paste from/to text input fields, including the address field)
- can only click / activate links in zoomed-in state – in page view mode, you can’t do this. In this respect, most other browsers with zoom are better; particularly because, here, you also need to wait for the zoomed-in state to be loaded
- while „scroll down”, „scroll up” etc. button events are processed (unlike in some other browsers like Touch Browser), they are strictly mapped to the same functionality as that of the D-pad. This means you can’t quickly scroll up/down a page – you can only use the touchscreen to do that (also see the lack of quick positioning a page)
- no direct access to IEM favorites (favorites are online only)
- no niceties like accelerated scrolling (unlike with NetFront 3.5 or Touch Browser)
- while it does support some shortcut buttons (for example, 6 for SmartFit, 5 for Refresh, 2 for Enter address etc.), these shortcuts are in no way as useful as those of Opera Mini. Again, there are no ways of page scrolling, which would be highly useful.
- No goodies like User-Agent overriding or disabling images / Flash animation / Java applets.
Conformance tests:
(Note that most of these tests – except the ones that need some interaction with the client: for example, file up/download – produce exactly the same results as with the desktop version of Firefox. I, to be on the safe side, re-tested them.)
File download: didn’t download the 7.5M test file (http://www.winmobiletech.com/sekalaiset/q3ce-1.1b-release-aximx50v-ppc2003.zip) in 15 minutes - download has just stalled.
File upload: doesn’t work (the control is shown but it doesn’t work) (http://www.winmobiletech.com/052008SkyFire/fileuploadtest.png)
Compliance tests:
The new W3C test (http://www.pocketpcmag.com/cms/blogs/3/opera_mini_4_1_full_multiplatform_tutori): not very bad (http://www.winmobiletech.com/052008SkyFire/w3ctestresult.png)
As you’ll also see, based on this and the User-Agent header, the engine clearly uses Firefox 2.0.0.11. I’ve tested this with the desktop 2.0.0.13 version (3b5 delivers worse results as can be seen in HERE (http://www.pocketpcmag.com/cms/blogs/3/multiplatform_web_browser_w3c_compliance)) and got exactly the same results (http://www.winmobiletech.com/052008SkyFire/desktopfirefox2013w3c.png)
Incidentally, I’ve also tested the just-released 3.0rc1 of Firefox to see whether it has fixed the compliance issues of the betas. The result is HERE (http://www.winmobiletech.com/052008SkyFire/desktopfirefox3rc1.png) and shows it is definitely better than the 3.0 betas – but not better than the 2.0.0.11+ series.)
Macromedia / Adobe Flash: works (http://www.winmobiletech.com/052008SkyFire/YouTubeWorks.png); client-server connection, much-much faster than in DeepFish / Thunderhawk animation.
As can be seen, even YouTube works. Sound didn’t work on my HTC Universal; other people at XDA-Developers, on the other hand, reported it working.
Frame tests (see the chart (http://www.winmobiletech.com/032007WebBrowsers/chart.html) of my Bible for more info):
Maximal number of sub-framesets?: 2.html (http://www.winmobiletech.com/032007WebBrowsers/Frames/2.html) was the first to work; 1.html (http://www.winmobiletech.com/032007WebBrowsers/Frames/1.html) still didn’t. Pretty good, though, compared to the other browsers.
Max. number of parallel frames (http://www.winmobiletech.com/032007WebBrowsers/SimpleFrames/index.html): no restriction, it seems (http://www.winmobiletech.com/052008SkyFire/ParallelFrameTest.png)
Frame boundaries aren’t settable; a frame in a (separate) tab / window isn’t viewable either.
Iframe support: works (http://www.winmobiletech.com/052008SkyFire/iframetest.png)
Dynamic HTML forms / explicit form field disabling (http://www.pocketpcmag.com/blogs/index.php?blog=3&p=865&more=1&c=1&tb=1&pb=1): supported (http://www.winmobiletech.com/052008SkyFire/DynamicHTMLforms.png)
WAP: not supported (http://www.winmobiletech.com/052008SkyFire/noWap.png)
Acid2 test: much better than that of IEM (http://www.winmobiletech.com/052008SkyFire/acid2test.png)
Java Applets: supported. A demo screenshot of the Animator Applet (http://java.sun.com/applets/jdk/1.3/demo/applets/Animator/example1.html) is HERE (http://www.winmobiletech.com/052008SkyFire/appletsupport.png). Another demo; now, with Live Feedback ImageMap (http://java.sun.com/applets/jdk/1.4/demo/applets/ImageMap/example1.html) is HERE (http://www.winmobiletech.com/052008SkyFire/AppletDemo2.png).
Incidentally, it’s worth noting the JPEG compression effects (blocks), which also show SkyFire uses exactly the same client/server model as Thunderhawk.
Ajax:
The two pages linked from AJAX: Getting Started (http://developer.mozilla.org/en/docs/AJAX:Getting_Started): works (http://www.winmobiletech.com/052008SkyFire/Ajax1.png)
Google Image Labeler: works (http://www.winmobiletech.com/052008SkyFire/imagelabeler.png)
Haven’t tested: caching (it has no caching, as with all the other client/server browsers not using for example separate images like Opera Mini or Thunderhawk). I haven’t tested full page loading speed (with my standard PPCMag test (http://www.winmobiletech.com/072005BrowserRoundup/PPCMagTest/)) either as the browser only receives the first about two pages upon loading a page; therefore, it’s impossible to benchmark the loading of the full page.
HTTP Headers: (also see THIS (http://www.pocketpcmag.com/cms/blogs/3/an_updated_list_of_mobile_user_agents) for the why’s of including them in here)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/2007112718 Firefox/2.0.0.11
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
X-Skyfire-Version: THNWD_xxx.xxx.fixme
X-Skyfire-Screen: 240,320,240,296
X-Skyfire-Phone: Phone with crappy default browser # touchscreen
Via: 1.1 skyadmin.sjc1.skyfire.com:3128 (squid/2.6.STABLE6)
X-Forwarded-For: 10.100.120.119
Cache-Control: max-age=259200
Connection: keep-alive
Verdict
Client/server-based and, as opposed to the text-based Opera Mini and Thunderhawk, image transfer-based clients will always have the same advantages over purely client-based ones; most importantly, having access to a desktop Web browser on the server, with even Java applet support. The same stands for the disadvantages: they will always exhibit the same problems, pretty much independent of the time and effort spent on making them as sophisticated as possible.
Fortunately, SkyFire behaves pretty well in this respect. While it, in my opinion, hardly can be called a decent alternative to Opera Mini or Mobile (it still has a LOT of problems – for example, the unacceptably high idle (!) CPU usage – to fix and, again, the client/server image transfer-based networking model is pretty much restricted), it’s already much better than DeepFish has ever been and it even beats the native Pocket PC version of Thunderhawk in many respects (when it comes to, for example, Flash support). It is also much better than (some of – I can only speak about the ones that I’ve thoroughly tested at, say, MWC) the non-Windows Mobile-based mobile Web browser solutions like PocketSurfer 2.
While, I’m afraid, because of the networking model’s huge restrictions, it will never match „lightweight” browsers like Opera Mini or even Opera Mobile, it’s still nice to see there is some serious development producing even newer Web browsers.
SkyFire is a client/server Web browser for both Windows Mobile platforms: touchscreen-enabled Pocket PC’s (in WM6+ parlance, Windows Mobile Classic and Pro devices) and touchscreen-less MS Smartphones (Windows Mobile Standard). It utilizes image-based transfer, just like the (cancelled) DeepFish and some non-Windows Mobile-based solutions like PocketSurfer 2 (http://www.pocketpcmag.com/cms/blogs/3/mwc_web_browsing_webkit_thunderhawk_news).
Please note that this is NOT an in-depth review but a comparison to the other browsers out there. It’s immensely more useful for both end users (so that you can decide whether it’s at all worth getting an account or just wait for later versions) and the developers themselves. This also means you’ll want to read my past Web browsing-related articles to understand everything in this article as, at times, I’ll switch to „geek speech”. Start with my W3C presentation (http://www.pocketpcmag.com/cms/index.php?q=blogs/3/2625) and follow the links back to, say, the Web Browsing Bibles. Also, search for „SkyFire” on my blog to find my earlier SkyFire-based posts – I’ve linked to several forum threads discussing the browser. In addition, In addition, I also recommend BrightHand's generic overview (http://www.brighthand.com/default.asp?newsID=13761) of the app - it offers a gentle introduction to SkyFire's capabilities, while, as has already been stated, my article is strictly a comparative, technical "geek speech" review targeted at more experienced Web users.
Note that the tests have been run on the latest 0.6.0.4503 version.
http://www.winmobiletech.com/052008SkyFire/SkyfireMain.png
A screenshot of the main menu (http://www.winmobiletech.com/052008SkyFire/SkyfireSettings.png); the Settings menu (as you can see, there aren’t much to set) is shown HERE (http://www.winmobiletech.com/052008SkyFire/SkyfireSettings2.png).
Pros
- It uses the Firefox 2.x engine, which is clearly better than Internet Explorer, even as of version 8. That is, it’s just much more standards-compliant than IE-based client/server mobile browsers like PocketSurfer 2
- It works flawlessly over any kind of Internet connection; not just U.S. mobile phone operators (unlike what the SkyFire folks state – and the popular belief). The latter is only needed for registering for the first time. Fortunately, after moving to another country and even swapping your SIM card / switching to another device (from a, say, CDMA(2000) to a GSM/WCDMA one) , you can go on using your account: for re-activation on another phone, you won’t need to have an active U.S. phone number any more.
- web standard compliance-wise, pretty good, including even Ajax
- high-quality and high-compliance Flash and Java support (strictly in client/server model; sound emulation may not work on some models)
- URL history (as with most other browsers, though) (http://www.winmobiletech.com/052008SkyFire/browsinghistory.png)
- Acceptable forward caching of approximately the following page (better than DeepFish used to be or that of PocketSurfer 2)
- The SmartFit mode works pretty OK and intelligently; I haven’t ever run into a situation when it didn’t failed to eliminate the need for horizontal scrolling. In this regard, it should be compared to Opera Mini 4+’s equally advanced text reformatting / reflowing algorithm in non-mobile view, (on non-high-res devices) zoomed in mode.
- In zoomed in mode, the cursor keys can be used for touchscreen-less link selection (and for scrolling in the four directions); in zoomed out mode, you can use it for scrolling the zoom-in window. That is, you don’t necessarily need to use your Pocket PC in two-hand mode – as is, of course, the case with the MS Smartphone (Windows Mobile 6 Standard) client.
- Compared to DeepFish: immensely better and faster. The only advantage of DeepFish was the support for hi-res on hi-res devices.
Cons:
- huge CPU usage when maximized (58% on a 624 MHz Xscale PXA270) independent of page contents (http://www.winmobiletech.com/052008SkyFire/HalfScreenAndCPUUsage.png) (that is, it'll happen even with no Flash / animation taking place). When minimized, no CPU usage.
- no support for multiple tabs (documents), unlike in most comparable browsers. This means you’ll need to always reload a page, should you want to return to it and can’t just switch quickly (back) to other/older pages.
- no hi-res (for example, VGA) support – not only as far as the low-res contents is concerned, but also when rendering input fields; then, its coordinates will be effectively halved on a high-resolution screen (http://www.winmobiletech.com/052008SkyFire/VGAtexInputFields.png). Fortunately, this doesn’t cause much problems with most pages.
- zoomed-out state provides pretty bad resolution / intelligibility (example HERE (http://www.winmobiletech.com/052008SkyFire/ZoomedOutScreenResNotVeryGood.png); incidentally, it also shows a message window showing a „connection lost” dialog)
- if you switch to another program and, then, back (with, say, an overridden app button), there are chances only half the screen will be used. A HTC Universal screenshot is HERE (http://www.winmobiletech.com/052008SkyFire/HalfScreenAndCPUUsage.png)
- much as there’re (non-standard) scrollbars on the right / bottom edge of the screen (example HERE (http://www.winmobiletech.com/052008SkyFire/Scrollbars.png)), they can’t be used to quickly position in the docs (the same problem as with Touch Browser)
- no page / link / image saving - of, for that matter, any kind of link / image context menus
- not any kind of copy/paste (however, you can copy / paste from/to text input fields, including the address field)
- can only click / activate links in zoomed-in state – in page view mode, you can’t do this. In this respect, most other browsers with zoom are better; particularly because, here, you also need to wait for the zoomed-in state to be loaded
- while „scroll down”, „scroll up” etc. button events are processed (unlike in some other browsers like Touch Browser), they are strictly mapped to the same functionality as that of the D-pad. This means you can’t quickly scroll up/down a page – you can only use the touchscreen to do that (also see the lack of quick positioning a page)
- no direct access to IEM favorites (favorites are online only)
- no niceties like accelerated scrolling (unlike with NetFront 3.5 or Touch Browser)
- while it does support some shortcut buttons (for example, 6 for SmartFit, 5 for Refresh, 2 for Enter address etc.), these shortcuts are in no way as useful as those of Opera Mini. Again, there are no ways of page scrolling, which would be highly useful.
- No goodies like User-Agent overriding or disabling images / Flash animation / Java applets.
Conformance tests:
(Note that most of these tests – except the ones that need some interaction with the client: for example, file up/download – produce exactly the same results as with the desktop version of Firefox. I, to be on the safe side, re-tested them.)
File download: didn’t download the 7.5M test file (http://www.winmobiletech.com/sekalaiset/q3ce-1.1b-release-aximx50v-ppc2003.zip) in 15 minutes - download has just stalled.
File upload: doesn’t work (the control is shown but it doesn’t work) (http://www.winmobiletech.com/052008SkyFire/fileuploadtest.png)
Compliance tests:
The new W3C test (http://www.pocketpcmag.com/cms/blogs/3/opera_mini_4_1_full_multiplatform_tutori): not very bad (http://www.winmobiletech.com/052008SkyFire/w3ctestresult.png)
As you’ll also see, based on this and the User-Agent header, the engine clearly uses Firefox 2.0.0.11. I’ve tested this with the desktop 2.0.0.13 version (3b5 delivers worse results as can be seen in HERE (http://www.pocketpcmag.com/cms/blogs/3/multiplatform_web_browser_w3c_compliance)) and got exactly the same results (http://www.winmobiletech.com/052008SkyFire/desktopfirefox2013w3c.png)
Incidentally, I’ve also tested the just-released 3.0rc1 of Firefox to see whether it has fixed the compliance issues of the betas. The result is HERE (http://www.winmobiletech.com/052008SkyFire/desktopfirefox3rc1.png) and shows it is definitely better than the 3.0 betas – but not better than the 2.0.0.11+ series.)
Macromedia / Adobe Flash: works (http://www.winmobiletech.com/052008SkyFire/YouTubeWorks.png); client-server connection, much-much faster than in DeepFish / Thunderhawk animation.
As can be seen, even YouTube works. Sound didn’t work on my HTC Universal; other people at XDA-Developers, on the other hand, reported it working.
Frame tests (see the chart (http://www.winmobiletech.com/032007WebBrowsers/chart.html) of my Bible for more info):
Maximal number of sub-framesets?: 2.html (http://www.winmobiletech.com/032007WebBrowsers/Frames/2.html) was the first to work; 1.html (http://www.winmobiletech.com/032007WebBrowsers/Frames/1.html) still didn’t. Pretty good, though, compared to the other browsers.
Max. number of parallel frames (http://www.winmobiletech.com/032007WebBrowsers/SimpleFrames/index.html): no restriction, it seems (http://www.winmobiletech.com/052008SkyFire/ParallelFrameTest.png)
Frame boundaries aren’t settable; a frame in a (separate) tab / window isn’t viewable either.
Iframe support: works (http://www.winmobiletech.com/052008SkyFire/iframetest.png)
Dynamic HTML forms / explicit form field disabling (http://www.pocketpcmag.com/blogs/index.php?blog=3&p=865&more=1&c=1&tb=1&pb=1): supported (http://www.winmobiletech.com/052008SkyFire/DynamicHTMLforms.png)
WAP: not supported (http://www.winmobiletech.com/052008SkyFire/noWap.png)
Acid2 test: much better than that of IEM (http://www.winmobiletech.com/052008SkyFire/acid2test.png)
Java Applets: supported. A demo screenshot of the Animator Applet (http://java.sun.com/applets/jdk/1.3/demo/applets/Animator/example1.html) is HERE (http://www.winmobiletech.com/052008SkyFire/appletsupport.png). Another demo; now, with Live Feedback ImageMap (http://java.sun.com/applets/jdk/1.4/demo/applets/ImageMap/example1.html) is HERE (http://www.winmobiletech.com/052008SkyFire/AppletDemo2.png).
Incidentally, it’s worth noting the JPEG compression effects (blocks), which also show SkyFire uses exactly the same client/server model as Thunderhawk.
Ajax:
The two pages linked from AJAX: Getting Started (http://developer.mozilla.org/en/docs/AJAX:Getting_Started): works (http://www.winmobiletech.com/052008SkyFire/Ajax1.png)
Google Image Labeler: works (http://www.winmobiletech.com/052008SkyFire/imagelabeler.png)
Haven’t tested: caching (it has no caching, as with all the other client/server browsers not using for example separate images like Opera Mini or Thunderhawk). I haven’t tested full page loading speed (with my standard PPCMag test (http://www.winmobiletech.com/072005BrowserRoundup/PPCMagTest/)) either as the browser only receives the first about two pages upon loading a page; therefore, it’s impossible to benchmark the loading of the full page.
HTTP Headers: (also see THIS (http://www.pocketpcmag.com/cms/blogs/3/an_updated_list_of_mobile_user_agents) for the why’s of including them in here)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/2007112718 Firefox/2.0.0.11
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
X-Skyfire-Version: THNWD_xxx.xxx.fixme
X-Skyfire-Screen: 240,320,240,296
X-Skyfire-Phone: Phone with crappy default browser # touchscreen
Via: 1.1 skyadmin.sjc1.skyfire.com:3128 (squid/2.6.STABLE6)
X-Forwarded-For: 10.100.120.119
Cache-Control: max-age=259200
Connection: keep-alive
Verdict
Client/server-based and, as opposed to the text-based Opera Mini and Thunderhawk, image transfer-based clients will always have the same advantages over purely client-based ones; most importantly, having access to a desktop Web browser on the server, with even Java applet support. The same stands for the disadvantages: they will always exhibit the same problems, pretty much independent of the time and effort spent on making them as sophisticated as possible.
Fortunately, SkyFire behaves pretty well in this respect. While it, in my opinion, hardly can be called a decent alternative to Opera Mini or Mobile (it still has a LOT of problems – for example, the unacceptably high idle (!) CPU usage – to fix and, again, the client/server image transfer-based networking model is pretty much restricted), it’s already much better than DeepFish has ever been and it even beats the native Pocket PC version of Thunderhawk in many respects (when it comes to, for example, Flash support). It is also much better than (some of – I can only speak about the ones that I’ve thoroughly tested at, say, MWC) the non-Windows Mobile-based mobile Web browser solutions like PocketSurfer 2.
While, I’m afraid, because of the networking model’s huge restrictions, it will never match „lightweight” browsers like Opera Mini or even Opera Mobile, it’s still nice to see there is some serious development producing even newer Web browsers.