Mobile CPUs and the Performance Inequality Gap
1–10 of 63 posts
Re: Mobile CPUs and the Performance Inequality Gap
#2Even though the average Android phone doesn’t compare performance wise to an iOS device and really sucks when it comes to running complicated web apps, it’s mostly Android users here who claim that progressive web apps are the future and that Apple is holding them back.
Re: Mobile CPUs and the Performance Inequality Gap
#3What do you iPhone users do with all of your power?
Re: Mobile CPUs and the Performance Inequality Gap
#4Even though the average Android phone doesn’t compare performance wise to an iOS device and really sucks when it comes to running complicated web apps, it’s mostly Android users here who claim that progressive web apps are the future and that Apple is holding them back.
Because Angular, React, Vue aren't needed for like 90% of those applications, server side rendering is more than enough.
Specially when tons of "native" applications are actually Cordova and Ionic garbage that take longer to start than a HTTP server reply to the native browser.
Native applications are great, when we are talking about stuff that actually makes use of the GPGPU or hardware sensors.
Outside games, office and drawing applications, I don't have any applications installed that couldn't easily be done as mobile Web sites.
Re: Mobile CPUs and the Performance Inequality Gap
#5geekbench have unreliable perfromance stats that've been favoring iphone for a looong while.
check your conclusions - 90% of articles with rocking iphone performance cite geekbench.
Re: Mobile CPUs and the Performance Inequality Gap
#6Even though the average Android phone doesn’t compare performance wise to an iOS device and really sucks when it comes to running complicated web apps, it’s mostly Android users here who claim that progressive web apps are the future and that Apple is holding them back.
Because Angular, React, Vue aren't needed for like 90% of those applications, server side rendering is more than enough. Specially when tons of "native" applications are actually Cordova and Ionic garbage that take longer to start than a HTTP server reply to the native browser. Native applications are great, when we are talking about stuff that actually makes use of the GPGPU or hardware sensors. Outside games, offic…
How are you going to have a PWA that works offline with server side rendering? The latest “Apple wants to force everyone to develop apps instead of using the web so they can get their 30% cut of mostly free apps” controversy was about offline storage expiring after 7 days.
Not to mention that the same people who are buying cheap Android phones probably have limited data plans and/or low bandwidth.
Re: Mobile CPUs and the Performance Inequality Gap
#7What about no.js?
Re: Mobile CPUs and the Performance Inequality Gap
#8geekbench have unreliable perfromance stats that've been favoring iphone for a looong while. check your conclusions - 90% of articles with rocking iphone performance cite geekbench.
We also know that the average selling price of Android is less than half that of an iPhone. Most Android phones being sold are lowend phones.
Besides that, there have been plenty of articles where they found that Android manufacturers were detecting when benchmarks were being run and cheating.
Re: Mobile CPUs and the Performance Inequality Gap
#9What are these charts intended to show? The relative differences seem broadly the same, going back years.
Is the idea that if all Android phones were magically 2x faster, some type of app architecture would magically become usable?
Re: Mobile CPUs and the Performance Inequality Gap
#10geekbench have unreliable perfromance stats that've been favoring iphone for a looong while. check your conclusions - 90% of articles with rocking iphone performance cite geekbench.
Practical experience with developing native cross platform applications in my experiece strongly aligns with geekbench results.
Cross platform as in most CPU intensive code is in C++ that is exactly shared between both, only trivial but obviously needed differences in input handling. And for Android the renderer is Vulkan and for iOS it’s metal, both essentially identical in how features are used.
Some super high end Android phones come close in some cases, but on average iOS devices wipe the floor with Android ones.
I want to emphasize that on top of Android HW being slower on average it is also hampered by the decision to use Java. Some api’s are Java only requiring JNI, which is slow, to access. Another issue is GC pauses, they are small but can result in skipped frame here and there, making the experience subtly worse.