$\"UC$ <\/a>\u00a0 $\"UC$ <\/a>
\n<\/span><\/span><\/div>\n

I tried UC 7.8 on three Nokia Symbian phones; a N95-3, N8 and E6, an HTC Magic Android phone and a basic Java phone, the Motorola WX400. \u00a0It seemed to work well on all the devices. Not so with a Motorola i1 Android OS 1.5 phone where the browser installed but hung on the startup screen. I wonder if the browser\u00a0really\u00a0is Android 1.5 compatible as UC\u00a0claims. Previous versions of UC worked well on this phone .<\/p>\n

On the E6, the UC Browser worked well with the small screen. It lets you use the Dpad to jump from link to link in mobile view. In zoom mode there’s virtual mouse pointer that you can move around the screen with the Dpad to highlight and hit small buttons, links and UI elements that tend to be hard to tap\u00a0accurately\u00a0on such a small screen.<\/p>\n

The new Android UI is\u00a0essentially\u00a0the one used in the touch screen Symbian version since UC 7.7<\/a>. \u00a0A bottom (right side on the E6) toolbar, which can be hidden if desired, gives one click access to the back and forward buttons, home screen and window menu. \u00a0A menu icon on the toolbar brings up a tabbed menu offering access to settings and advanced features like clipboard management and the download manager. I like the UC touch menu design and find it requires fewer clicks for most actions than Opera Mini 6.1’s touch UI.<\/p>\n

Site\u00a0compatibly\u00a0was generally good with one\u00a0significant\u00a0exception, Twitter. I had no problems opening most sites. But the mobile and desktop versions of Twitter.com and third party Twitter webapps like Dabr would frequently either hang after I entered my user ID and password or throw a “403 rate limit exceeded error”. \u00a0While this could have been a Twitter issue rather than a UC one, Twitter would work normally in Opera Mini and the Android browser during the time it was failing in the Android browser.<\/p>\n

Interestingly, when you put the UC browser in zoom mode on Android it uses Android’s native WebKit based direct browser engine rather than UC’s own proxy based one. As a result, rendering in zoom mode on Android is\u00a0nearly\u00a0pixel perfect unlike the rather messy and inaccurate\u00a0rendering found in zoom mode on other platforms. The trade off is that you lose the speed and data saving advantages of \u00a0a proxy browser in zoom mode on Android. Also, if you switch from zoom mode to mobile view on Android refreshing the page doesn’t actually switch the mode, you have to load a different page before the browser actually starts using the proxy engine.<\/p>\n

Although I generally prefer Opera Mini, the Opera Mini servers have been misbehaving a lot lately with web forms frequently not posting and links going to totally\u00a0different\u00a0sites than they should. Due to these problems I’ve been using UC more and more lately and am finding it generally more reliable, other than the issues with Twitter.<\/p>\n

$\"UC$ <\/a>\u00a0 $\"UC$ <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"