Working on an update to the Performance Inequality Gap series[1], and it occurs to me that I don't think web developers grok how hard mobile is. There are *new* devices, targeted at the US market, w/ 320x240 resolution, 512MB of RAM, and 2014's finest A53 cores. They sell for $50 and do volume:
https://www.cricketwireless.com/prepaid-phones/smartphones/cricket-debut-flex-graphite-gray.html
[1]: https://infrequently.org/series/performance-inequality/
This sort of device is why average selling prices continue to fluctuate in a tight band between $300 and $325 (new/unlocked), even as the high-end continues to push new price peaks. You've gotta sell a *LOT* of < $200 phones to offset a $1200 "pro max" device.
To be sure, a $200 device is a damned sight better than a $50 flip phone, but *worlds* different from the iPhones and Pixels and S23 Ultras that webdevs carry.
Here's what $200 gets you today (new, unlocked):
https://www.motorola.com/us/smartphones-moto-g-power-5g/p?skuId=885
https://www.gsmarena.com/motorola_moto_g_power_5g-12219.php
Totally umodified, cache-free A78's and A53's, mercifully produced on a 6nm process. Not that it helps:
https://browser.geekbench.com/v6/cpu/compare/4216222?baseline=3639070
Lest you think that's an outlier, here's the $350 Motorola Edge vs an iPhone 15 Pro:
https://browser.geekbench.com/v6/cpu/compare/4200094?baseline=3639070
The data's really, really clear: most *new* phones (even in the US and the UK) are 20-35% as fast as the ones developers carry.
But it's worse than that! Most phones in the fleet are more than 18 months old, which means the median device is *whatever cost ~$350 two years ago*.
That is not a fast device. It doesn't have 5G. It absolutely will not deliver a good UX if you're building with the usual React nonsense.