The downside of Opera Mini's client/server model is that complex JavaScript doesn't always behave as expected. Opera Mini's backend infrastructure uses the HTML rendering engine from Opera's desktop browser, which means that Opera Mini can reproduce complex webpages with relatively high accuracy. These features are also available in the latest Opera Mobile beta, which we reviewed last year. It automatically wraps blocks of text so that it will fit the width of the screen, effectively eliminating the need for horizontal scrolling. In that rewrite, Opera aimed to deliver a more desktop-like browsing experience by displaying the full page and allowing users to zoom in and scroll through content. The Opera Mini codebase was rewritten almost entirely for version 4, which was released last year. It's worth noting that this rendering mechanism is also used to facilitate "Turbo Mode" in Opera Mobile. In addition to significantly reducing the amount of work that has to be done on the user's mobile device, this approach also boosts page loading speed. In order to reduce bandwidth consumption and computational overhead, Opera Mini relays all page requests through Opera's backend server infrastructure which will load and prerender page content and then compress it before transmitting it to the user. Opera Mini is Opera's lightweight MIDP browser for J2ME-enabled feature phones and other devices that aren't capable of running Opera Mobile. With swift page rendering and top-notch usability, it's guaranteed to turn heads. It offers an outstanding new user interface that is a significant improvement over previous versions of Opera Mini and even outshines the most recent builds of Opera Mobile. Opera Mini got a boost this week with the launch of the first Opera Mini 5 beta release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |