could easily be caused by not having enough RAM and having to shuffle art assets between storage and memory

In iOS there is no swap:

In iOS, there is no backing store and so pages are are never paged out to disk, but read-only pages are still be paged in from disk as needed.

(https://developer.apple.com/library/archive/documentation/Performance/Conceptual/ManagingMemory/Articles/AboutMemory.html )

Which counterintuitively actually makes it more RAM capacity demanding than macOS. macOS’s 2-stage swapping with compression (and absurdly fast NVME) is in fact quite good, iOS has to fit in RAM and RAM only.

I wholeheartedly agree about MaxTech on average, but in this particular instance… the video is actually pretty good.

Or rather, if one watches it correctly, the material presented that remains after the filter is quite good. Namely, one should discard all claims based on pure numerology - numbers from the config, current year, “RAM used” shown by activity monitor (a big chunk of that figure is very optional file cache that only marginally improves perf, but uses up the more RAM the more you give it, for starters, + a lot more), etc.

The actual experiments with applications done on the machine, performance measurements (seconds, etc), demonstrations of responsiveness (switching from tab to tab on camera) are actually quite well done, in fact, the other youtube videos on the subject rarely include quantifiable performance / timing measurements and limit themselves to demos (or pure handwaving and numerology).

Of course, conclusions, “recommendations”, etc. in their exact wording also need to be taken with a half a metric ton of salt, but there is still a lot of surprisingly good signal in that video, as noted.