iOS has always used Virtual Memory. The difference being there’s no storage-backed swap on iOS. This will change for M1 iPads with 128GB+ storage starting with iPadOS 16.
Guidelines for improving the performance of memory-related code.
developer.apple.com
I expect similar to MacOS, iPadOS will handle paging in and out, and this will be something out of the app’s control.
At 3,000 P/E cycles and similar write volumes to M1 Macs (I’m seeing 100GB/day), I estimate around 5 years lifespan for the 64GB model and that’s not taking into consideration write amplification. 128GB doubles that life expectancy and 256GB quadruples it.
The potential is high for a class action lawsuit if masses of 64GB iPads die within 5 years or so. I’m guessing this is part of the reason why they’re not adding swap to the 64GB Air 5. Of course, the SSD controller is part of the M1 chipset (and A9-A15 for that matter) so maybe if they figure out a method to reduce NAND flash wear, they might implement swap on lower storage models.
Here’s a thought, what if Stage Manager isn’t Apple’s end goal? What if all the new M1 exclusive features in iPadOS 16 (VM swap, Stage Manager, Display Scaling) are merely building a foundation, setting up an environment on iPads where Mac apps could run in the future (whenever that may be)? In this way, M-series iPads could get programs like full MS Office, Adobe, FCP, etc. (as long as it’s available on Mac App Store and compatible with M1) without the need to create a touch-optimized UI. Perhaps those future goals are why they’re capping the minimum requirement at M1.