User Experience: This represents things like scrolling speed and page reactivity when users scroll and zoom. The idea is that at some level some page blocks need to be rebuilt, and if they aren’t built fast enough, you may see blank portions of the page, or the scrolling might be jittery. If it is fast enough, the scrolling is fluid.
Networking: Of course, all of the above need data from the network, so it’s extremely important that the networking software layer is well optimized. There are many strategies to improve networking performance, and many of them rely on the smart use of cached data (a local version) so that there is as few network requests as possible.
Obviously, one may ask whether or not Qualcomm’s benchmark would favor its own chips. It’s a reasonable question to ask. Given that the benchmark is an app like any other, Qualcomm’s chip can indeed lose to a competitor (believe me, creating your own benchmark can bite you in the behind later on). Also Qualcomm actually uses it internally, so it’s best of it works properly… Finally, Qualcomm is considering releasing the code to the public, and that is probably the best way to gain legitimacy.