It is a realistic user scenario, which in my opinion makes it a good test. The real world performance is what matters here. The user doesn't care if technically there is some trick that is being used to "cheat."
> The user doesn't care if technically there is some trick that is being used to "cheat."
Besides, if we're talking about average user, they're not force closing apps and the phone should be caching the most frequently used apps. So even then the test won't mimic real world experience even if it's about perception. Maybe initially, but not after sustained usage. People usually normalize to whatever they're using
The only reliable way I've found to use termux (as an ssh client, not anything high-resource) and Firefox at the same time is to use multi window, dragging termux out of the way of the keyboard every time I switch, as Firefox will regularly need to be reloaded otherwise; if I'm on certain heavy or lazy-loading websites or using a link with a hash in it, it'll then also lose my scroll position. This is particularly frustrating when I ssh into minimized containers with no command completion or man pages.
[1]: you actually can with devtools and dexie import export, but it always times out for my databases. Meanwhile on Firefox you can just use devtools to backup the entire profile directory and then replace it in-place.
This is actually not a good test because there are a lot of tricky and subtle things that can make the comparison highly unfair. Smartphones will cache apps so that they don't fully close. Then, if you do actually force kill them they will start up in the background.
Are we surprised a Google phone caches the Google browser which is considered to be a high priority app, commonly used, and even the backbone of other apps?