Dolphin Browser acquires its own engine
The MoboTab Inc. team, which develops the popular Dolphin HD browser for Android and Apple iOS, today introduced a beta version of the new browser for the Android platform. Previously, the browser was just an add-on over the standard WebKit and V8 libraries, which are included in the standard distribution package of the Android distribution. The new version went the way of Google Chrome Beta and works with its own engine WebKit. What came of this, I will consider in the test-comparison with Google Chrome.
Google Android 4.0.3 will be used as an experimental platform, in the form of a modified Virtous Prime firmware on ASUS eeePad Transformer Prime TF201 tablet (NVIDIA Tegra 3, 4xCortex-A9, 1 GB RAM, NVIDIA GeForce ULP 3).
I use the standard Google V8 Benchmark, HTML5Test, Browsermark as tests.
Compare the latest available version of Chrome Beta with Dolphin HD Engine Version Beta.
The HTML5Test test is the most widely known test that verifies the implementation of web specifications in the rendering engine and provides test results in an accessible form. At the same time, the test is not able to check the quality of implementation, so the engine can formally support this specification, but in fact it would be better for the developer not to support it. This is especially true for Google Chrome.
The browser dials a magnificent number of 450 + 3 units. This is an absolute record for all existing mobile browsers, including experimental. The engine formally supports almost everything that is possible, so it’s easier to say that it’s not implemented - there is no support for subtitles, there is no support for video codecs, including free Ogg Theora and WebM, there is an implementation of mp3 from the audio codecs, everything else, including including ogg vorbis, no. It is clear that this is not part of any HTML5 standard in any edition of the W3C or WHATWG, but nonetheless. There is also no support for Drag and Drop. All other things, dryuki a la geolocation, WebGL, WebSocket, IndexedDB, Web Workers implemented.
')
Chrome shows more restrained results. Only 371 + 11 points. Chrome is not yet implementing support for everything and everyone, but it is gaining bonus points due to the support of all codecs except MPEG-4 and Ogg Theora. WebGL is supported in the engine, but for now Google considers it necessary to cut it through the flag.
This test from Google checks the performance of the V8 engine, which is used in Google Chrome and in Dophin HD. Chrome Beta uses the 3.8.9 branch engine, but it wasn’t possible to figure out the version implemented in Dolphin HD. According to the test results, relative equality is obtained with a slight superiority of the Google browser.
This benchmark also checks the performance of the JavaScript engine, but its purpose is purely smartphone. According to the testing methodology, it is similar to the Futuremark Peacekeeper. Means of the engine draw simple pictures, build primitive DOM operations. The benchmark was popular in the era of the iPhone 3GS, but now it does not lose its relevance.
Chrome is faster here too
This test from the highly respected habraiser babarun verifies the implementation of the hardware accelerated HTML5 canvas. The Tegra 3 has a built-in though architecturally clumsy, but quite tolerable GeForce ULP 3 video accelerator. But since both Chrome and Dolphin have support for hardware acceleration, this test will also be implemented.
At 960 polygons, the browser draws a phenomenal result of almost 54 fps.
But Chrome cannot boast of such a result:
Dolphin formally supports WebGL, so you should check the performance with 3D GRAFON11! 11
As I expected, support will be clumsy. Draw draws a picture, but so slowly that nothing serious can not be said. Perhaps this is a software bug, and it is possible to heal the increase in iron power, but for the time being WebGL cannot be used on mobile platforms for anything complicated:
So, summing up, the guys from MoboTab managed to show a result similar to the new-fashioned Chrome Beta. Given the support for syncing bookmarks and data with a Google account, the implementation of extensions, which is only being implemented in Chrome, and a very smart interface, the MoboTap browser makes serious claims to be the best WebKit browser for Android.
QR code:
Address to download . Works on Android 3/4, as well as with limited functionality under Android 2.3.x.
Google Android 4.0.3 will be used as an experimental platform, in the form of a modified Virtous Prime firmware on ASUS eeePad Transformer Prime TF201 tablet (NVIDIA Tegra 3, 4xCortex-A9, 1 GB RAM, NVIDIA GeForce ULP 3).
I use the standard Google V8 Benchmark, HTML5Test, Browsermark as tests.
Compare the latest available version of Chrome Beta with Dolphin HD Engine Version Beta.
HTML5Test
The HTML5Test test is the most widely known test that verifies the implementation of web specifications in the rendering engine and provides test results in an accessible form. At the same time, the test is not able to check the quality of implementation, so the engine can formally support this specification, but in fact it would be better for the developer not to support it. This is especially true for Google Chrome.
Dolphin hd
The browser dials a magnificent number of 450 + 3 units. This is an absolute record for all existing mobile browsers, including experimental. The engine formally supports almost everything that is possible, so it’s easier to say that it’s not implemented - there is no support for subtitles, there is no support for video codecs, including free Ogg Theora and WebM, there is an implementation of mp3 from the audio codecs, everything else, including including ogg vorbis, no. It is clear that this is not part of any HTML5 standard in any edition of the W3C or WHATWG, but nonetheless. There is also no support for Drag and Drop. All other things, dryuki a la geolocation, WebGL, WebSocket, IndexedDB, Web Workers implemented.
')
Chrome beta
Chrome shows more restrained results. Only 371 + 11 points. Chrome is not yet implementing support for everything and everyone, but it is gaining bonus points due to the support of all codecs except MPEG-4 and Ogg Theora. WebGL is supported in the engine, but for now Google considers it necessary to cut it through the flag.
Google v8 benchmark
This test from Google checks the performance of the V8 engine, which is used in Google Chrome and in Dophin HD. Chrome Beta uses the 3.8.9 branch engine, but it wasn’t possible to figure out the version implemented in Dolphin HD. According to the test results, relative equality is obtained with a slight superiority of the Google browser.
Dolphin hd
Chrome beta
Rightware browsermark
This benchmark also checks the performance of the JavaScript engine, but its purpose is purely smartphone. According to the testing methodology, it is similar to the Futuremark Peacekeeper. Means of the engine draw simple pictures, build primitive DOM operations. The benchmark was popular in the era of the iPhone 3GS, but now it does not lose its relevance.
Dolphin hd
Chrome beta
Chrome is faster here too
Babarun canvas-accelerate
This test from the highly respected habraiser babarun verifies the implementation of the hardware accelerated HTML5 canvas. The Tegra 3 has a built-in though architecturally clumsy, but quite tolerable GeForce ULP 3 video accelerator. But since both Chrome and Dolphin have support for hardware acceleration, this test will also be implemented.
Dolphin hd
At 960 polygons, the browser draws a phenomenal result of almost 54 fps.
Chrome
But Chrome cannot boast of such a result:
Webgl
Dolphin formally supports WebGL, so you should check the performance with 3D GRAFON11! 11
As I expected, support will be clumsy. Draw draws a picture, but so slowly that nothing serious can not be said. Perhaps this is a software bug, and it is possible to heal the increase in iron power, but for the time being WebGL cannot be used on mobile platforms for anything complicated:
Total
So, summing up, the guys from MoboTab managed to show a result similar to the new-fashioned Chrome Beta. Given the support for syncing bookmarks and data with a Google account, the implementation of extensions, which is only being implemented in Chrome, and a very smart interface, the MoboTap browser makes serious claims to be the best WebKit browser for Android.
QR code:
Address to download . Works on Android 3/4, as well as with limited functionality under Android 2.3.x.
Source: https://habr.com/ru/post/146128/
All Articles