3 ms·
Didn't the author address this by talking about testing on both burner and top-line android models vs getting the web app working decently on an iPhone 4S?
by r00fus 11y ago
Didn't the author address this by talking about testing on both burner and top-line android models vs getting the web app working decently on an iPhone 4S?
- georgemcbay 11y agoNot really. Top of the line Android phones can actually be worse for this problem than cheaper ("burner") ones. Top-of-the-line Android phones tend to follow the pattern of having a CPU with many cores each of which is slower than the CPU would be if they used a single core solution. This is excellent for native apps that properly use multithreading, but dreadful for web apps since JavaScript as it is commonly written (ignoring the various *Worker extensions to the language attempted over the years) is essentially single-threaded, so the majority of the app code is running on one slow core while the rest sit idle (or run background services that have nothing to do with the foreground app).