UC Browser 2.7 For Windows Phone Released

By | December 27, 2012

UC Browser For Windows Phone Receives A Major Update

For both WP7 and WP8.

Now here is something to fill the gap in case you are not satisfied with the IE9 or IE10 Mobile: a new version of UC Browser

While its performance seems to be below that of IE10, it makes up for that with a variety of features. Starting with version 2.7, the Speed Dial page has been moved to the homepage, allowing you to quickly access your favorite web sites.

In addition to that, WP7 users will be excited to know that there is now an option to keep your screen on while downloading files so Wi-Fi stays connected (recent WP8 update fixed this).

Those are not the only changes though, there are performance improvements, Incognito mode and more.

UC Browser 2.7 Changelog

Rotation Lock
Touch to lock the rotation, either in portrait or landscape view

Smart Downloads
Keeps the screen on while downloading, which makes sure your Wi-Fi stays connected

Incognito Browsing
No browsing history will be saved while using Incognito Browsing mode

Speed Dial
Speed Dial on homepage makes it easier to visit your favorite websites

QR Code Scanning
Scan QR codes or use QR code images already in your phone

Personalized Wallpaper
Customize your browser to your liking with a variety of wallpapers

Faster Start-up
Start-up speed is 20% faster than UC Browser 2.6


UC Browser 2.7

[Via: WPCentral]

About (Author Profile)

Vygantas is a former web designer whose projects are used by companies such as AMD, NVIDIA and departed Westood Studios. Being passionate about software, Vygantas began his journalism career back in 2007 when he founded FavBrowser.com. Having said that, he is also an adrenaline junkie who enjoys good books, fitness activities and Forex trading.

Comments (12)

Trackback URL | Comments RSS Feed

  1. Przemysław Lib says:

    Of course its SLOWER.

    How can it be otherwise?

    No JIT == no fast JS.

    No threads == no fast rendering engine.

    No C++ == inability of using ready engines from “desktops” or even from Android.

    The BEST they can do (in terms of perf) is to get IE engine and build their browser on top of it.

    • Shane Bundy says:

      I agree with the JIT argument. JS can’t be as fast as on desktop if there’s no JIT compiler.

      The threads I disagree with. You don’t need a bucket load of threads for an engine to be fast. It’s a can of worms so let’s not go there.

      If an engine doesn’t use C++ then that shouldn’t affect performance, as it’s up to the vendor to optimise it properly.

      Building on top of the IE engine is a lazy way to release a product on any Windows platform.

      • Przemysław Lib says:

        You NEED one thread for handling user input. Second for painting on the screen.

        Than you can have tabs in separate threads. You can have plugins in separate threads. Etc. Lots of use for lots of threads. (On android FF and Chrome work that way).

        Yes if C++ is not available to all web browsers on WinP than they are at “same disadvantage”. But they are not. IE is wrote with C++.

        Is lazy but if you can not do better, than its best :P Like WebKit on iOS is best cause its ONLY choice.

        • Shane Bundy says:

          I didn’t say you CAN’T have threads, I was just saying you don’t need a whole lot of them for a fast rendering engine.

          If an app isn’t written in C++ they’re all at the “same disadvantage”. Other than runtime performance, what else could it be? Security (C++ is bad at that)? Reliability (C++ is bad at recovering from errors)? Every language has some sort of flaw.

          About it being “best” if someone can’t do better than what’s already there, I agree. Opera Mini on iOS uses its own engine but it’s only on Opera’s proxy servers and not on the actual device but it’s still a browser that doesn’t use the WebKit engine, though.

          • Przemysław Lib says:

            :D Did not know about Opera Mini.

            So they put engine outside of the box :)

            Anyway. To make modern (fast!) rendering engine you need a lot of specialized (and potentially harmful, or energy inefficient) APIs.

            Lack of them put 3rd party web browser vendors at disadvantage compared to OS manufacturer (who can use those API..).

            It also is valid for other applications but web browsers tend to use state of the art tech. And there is always demand for more of it.

            MS limitation harm competition there.

          • Shane Bundy says:

            An API allows external applications to interact with that application. Nothing to do with being “energy inefficient”.

            Some of Microsoft’s APIs are quite restricted and it does put them at a disadvantage, but you can blame the broken software patent system for not allowing innovation to flow within that infrastructure.

          • Przemysław Lib says:

            Shane Bundy
            Yes API is JUST API. So if its about wakeup/idle API than it can be about saving power.

            PS MS is patent-happy. And no, restrictions in WinP, WinRT are BY DESIGN.

          • Shane Bundy says:

            Fair enough. If it’s an API for power-saving tasks then I’m for it. I remember WebKit removing some sleep() commands in their code to improve performance. I think it caused a slight power regression but nothing noticeable.

            And yes. Microsoft is patent-happy. Yes, the restrictions in RT and such are by design and it’s a good thing MS fired Sinofsky because of them.

      • Rafael says:

        IE’s Trident is the only engine browsers can be made of on Windows Phones… It isn’t laziness..