It's running on a Raspberry Pi, not a phone.
Re:QML vs. HTML5
by jamescostian on Saturday July 29, 2017 @01:15AM
(#14879620)
I'm not sure which Raspberry Pi, but assuming it's the latest one (this is the latest one, right?), here are its specs: https://www.raspberrypi.org/products/raspberry-pi-3-model-b/
Here are my phone's specs: http://www.gsmarena.com/apple_iphone_6s-7242.php
IMO they aren't super different. Sure, my phone runs at 1.84GHz while the Pi runs at 1.2GHz, but the Pi also has twice as many cores. My phone does have twice the Pi's RAM, but I don't think RAM is what made a difference here.
Here's the whitepaper
https://cdn2.hubspot.net/hubfs/149513/Whitepapers/WHITEPAPER...
Yes, it's a Raspberry Pi 3.
No, it's not comparable to an iPhone 6s.
An iPhone 6s is about 5 times faster.
http://browser.geekbench.com/v4/cpu/3444316
http://browser.geekbench.com/v4/cpu/3496162
A Raspberry Pi 3 is about equivalent to a Samsung Galaxy S III (a five year old phone.)
http://browser.geekbench.com/v4/cpu/search?page=1&q=galaxy+s...
Re:QML vs. HTML5
by jamescostian on Saturday July 29, 2017 @01:52PM
(#14882260)
You're totally right. Those geekbench scores are quite different! Scrolling and tabs with different information were still very fast on my iPod Touch (this was 5 years ago), and I could always tap on images like logos and they would work. But I don't have any 5 year old devices to try the range slider, so that could very possibly be another thing (in addition to the virtual keyboard) where QML totally outperformed HTML5
There were also two things they said the HTML5 version didn't have at all - a virtual keyboard and clicking on an image. Tapping on images is something people have been doing in HTML for a very, very, very long time. It's not that hard, and it works just fine. I'd say it's probably pretty difficult to mess up.
I think the real advantage shown in the video was the virtual keyboard. I just googled "virtual keyboard" and tapped on the first link on my phone, and the experience was awful.