This way you'll be able to run more than one "web app" at the same time on your devices.
A few years ago, I had two computers on my desk, my beefy dev with double screens and some good specs for the time and my test machine which was the standard given to every non dev, with a 1024x768 screen.
I couldn't say to the boss that the code was ready until I tested it on that machine, which was sometimes eye opening and why a 2Mb HTML page wasn't a good idea.
I don’t think I would want to work in that environment anymore.
It's probably a bit better than when Unity was new. I do remember the first x-com remake in 2012 was lasting longer on battery than $random_unity_indie.
If you are making products that depend on people spending money on them, you generally don't have to care about broke people with 15 year old computers.
I was stuck once in a cabin in the woods with an old Android phone. I’m glad it still worked, and that people curating software experiences for it had more empathy — and more business sense — than this comment displays.
If that’s your goal this machine is still too powerful. Web apps generally care about single thread performance. The machine has a single thread performance that exceeds any and all Intel/AMD processors, according to Geekbench (A18 Pro: 3445; Ryzen 9 9950X: 3385). My own test for ensuring my web app performs well involves a machine less than half as fast, and my web app runs with all assertions turned on.
Not true at all: https://www.cpubenchmark.net/single-thread/