Alex Russel did a lot of writing on this and posts yearly updates based on the state of the phone market. You can pick median, P75 or P95 device based on the analysis and set up targets based on that.
I did it the simple way and bought a first item in "sort by cheapest" smartphone list. That's Alcatel 1, and it's extremely underpowered. It's maybe a bit overkill, but if something runs on that device, it will run amazing on anything else.
Hmm....that's a cool writeup but not really what I was looking for. Anyway, let's take the phone configuration he mentions:
"The A51 featured eight slow cores (4x2.3 GHz Cortex-A73 and 4x1.7 GHz Cortex-A53) on a 10nm process"
Looking at Wikipedia, it also has at least 4 GB of RAM and comes with 4G Internet.
The Alcatel 1 also seems to have at least a 1 GHz CPU and at least a gigabyte of RAM.
I also had a look at the Samsung Galaxy Watch. Lowest spec I could find was 1 GHz dual core + 768MB RAM (bluetooth), 1.5 GB (LTE).
The machine I was doing the web-based Postscript rendering on was a PowerMac G3. Single core 32 bit processor running at 266 MHz and and with 192MB of RAM. Connection was early DSL, 768 KB down, I think 128 KB up.
I did not do any heroic optimizations, it was fast "as-is".
So I think my point stands that modern computers, including low end Smartphones and watches are incredibly powerful and fast, including the networks.
If your tech stack manages to bring that hardware to its knees for basic UI rendering, and requires a lot of optimization effort to run barely reasonably, then there is something fundamentally wrong with your tech stack.
> If your tech stack manages to bring that hardware to its knees for basic UI rendering, and requires a lot of optimization effort to run barely reasonably, then there is something fundamentally wrong with your tech stack
Yea, I think this is the problem, but the hard part is that it's largely outside of your control on the web. Alcatel 1 is technically a super computer, but it can't even run its own UI properly. I optimize my websites on it and while laggy, they sometimes run faster than Chrome's UI that displays them, it's crazy.
Running the system + the browser is already way too much and there's almost no perf budget left for the website - and it doesn't help that web tech is inherently sub-optimal in many ways, so you're already pessimized on all fronts. Even a baseline a simple page with almost no content is laggy on this device.
> it's largely outside of your control on the web.
On the web or in the JS ecosystem?
While I agree that even just the browsers are monster applications, usually duplicating (at least) the entire OS they are running on, just usually worse.
However, most browsers are perfectly capable of extremely snappy rendering and interactions, even on low-powered devices.
Let's remember that WWW.app was developed on a NeXT Cube, 25 MHz 68040, probably in the 16-64 MB RAM range (min was 8, but I am assuming it was more than the min), and that was plenty snappy.
Yes, pretty often. Like I said, Alcatel 1 can't even handle it's own native UI. Just opening the search/url input has like 2 second latency. On a fresh start, it's like 20s. Typing on a native keyboard is super laggy and slows down the whole phone.
Sites like Hacker News and textual blogs work pretty fine if you get lucky and nothing is running in the background, but you have to wait for a while for the phone to stop crunching stuff. The scrolling has noticable latency and random hiccups. If you scroll too fast, the content will show up delayed.
Once you add some images or a bit of javascript, you start to feel a lot more jank. You often get a perf hit when you recieve push notifications or when you re-connect to wifi, or open a native keyboard accidentaly, same with triggering browser UI or tapping the back button. Also, the browser sometimes just crashes (I guess out of memory?).
It certainly is usable, but the latency variance of various actions is wild. Sometimes it feels ok to use, but other times the whole session is like 1 fps for 5 minutes.
Alex Russel did a lot of writing on this and posts yearly updates based on the state of the phone market. You can pick median, P75 or P95 device based on the analysis and set up targets based on that.
https://infrequently.org/2024/01/performance-inequality-gap-...
I did it the simple way and bought a first item in "sort by cheapest" smartphone list. That's Alcatel 1, and it's extremely underpowered. It's maybe a bit overkill, but if something runs on that device, it will run amazing on anything else.
Hmm....that's a cool writeup but not really what I was looking for. Anyway, let's take the phone configuration he mentions:
"The A51 featured eight slow cores (4x2.3 GHz Cortex-A73 and 4x1.7 GHz Cortex-A53) on a 10nm process"
Looking at Wikipedia, it also has at least 4 GB of RAM and comes with 4G Internet.
The Alcatel 1 also seems to have at least a 1 GHz CPU and at least a gigabyte of RAM.
I also had a look at the Samsung Galaxy Watch. Lowest spec I could find was 1 GHz dual core + 768MB RAM (bluetooth), 1.5 GB (LTE).
The machine I was doing the web-based Postscript rendering on was a PowerMac G3. Single core 32 bit processor running at 266 MHz and and with 192MB of RAM. Connection was early DSL, 768 KB down, I think 128 KB up.
I did not do any heroic optimizations, it was fast "as-is".
So I think my point stands that modern computers, including low end Smartphones and watches are incredibly powerful and fast, including the networks.
If your tech stack manages to bring that hardware to its knees for basic UI rendering, and requires a lot of optimization effort to run barely reasonably, then there is something fundamentally wrong with your tech stack.
> If your tech stack manages to bring that hardware to its knees for basic UI rendering, and requires a lot of optimization effort to run barely reasonably, then there is something fundamentally wrong with your tech stack
Yea, I think this is the problem, but the hard part is that it's largely outside of your control on the web. Alcatel 1 is technically a super computer, but it can't even run its own UI properly. I optimize my websites on it and while laggy, they sometimes run faster than Chrome's UI that displays them, it's crazy.
Running the system + the browser is already way too much and there's almost no perf budget left for the website - and it doesn't help that web tech is inherently sub-optimal in many ways, so you're already pessimized on all fronts. Even a baseline a simple page with almost no content is laggy on this device.
> it's largely outside of your control on the web.
On the web or in the JS ecosystem?
While I agree that even just the browsers are monster applications, usually duplicating (at least) the entire OS they are running on, just usually worse.
However, most browsers are perfectly capable of extremely snappy rendering and interactions, even on low-powered devices.
Let's remember that WWW.app was developed on a NeXT Cube, 25 MHz 68040, probably in the 16-64 MB RAM range (min was 8, but I am assuming it was more than the min), and that was plenty snappy.
> > it's largely outside of your control on the web.
> On the web or in the JS ecosystem?
I meant outside of your control on that device.
Hmmm...that is the opposite of what you wrote earlier.
Are you claiming that even plain/styled HTML is too slow on these kinds of devices?
Yes, pretty often. Like I said, Alcatel 1 can't even handle it's own native UI. Just opening the search/url input has like 2 second latency. On a fresh start, it's like 20s. Typing on a native keyboard is super laggy and slows down the whole phone.
Sites like Hacker News and textual blogs work pretty fine if you get lucky and nothing is running in the background, but you have to wait for a while for the phone to stop crunching stuff. The scrolling has noticable latency and random hiccups. If you scroll too fast, the content will show up delayed.
Once you add some images or a bit of javascript, you start to feel a lot more jank. You often get a perf hit when you recieve push notifications or when you re-connect to wifi, or open a native keyboard accidentaly, same with triggering browser UI or tapping the back button. Also, the browser sometimes just crashes (I guess out of memory?).
It certainly is usable, but the latency variance of various actions is wild. Sometimes it feels ok to use, but other times the whole session is like 1 fps for 5 minutes.