EDIT: See cma's comment below which adds more info: apps that use their own render still support foveated rendering too.
EDIT: See cma's comment below which adds more info: apps that use their own render still support foveated rendering too.
(source: "Discover Metal for immersive apps - WWDC23 - Videos - Apple Developer " https://developer.apple.com/videos/play/wwdc2023/10089/)
If they try to hide it by restricting access to reading the foveation texture, you can be sure anti privacy apps like Immersive Facebook will try tricks like recovering it from GPU timestamp queries (render two transparent triangles covering the screen in separate draw calls, find which took the longest, subdivide and repeat).
This seems prudent, because as personal as smartphones are, a headset like the Vision Pro dials that up tenfold. Considering what third parties have done with just the information surfaced in mobile operating systems, or heck even the web, I shudder to think of what they'd do with gaze data and a high fidelity color 3D map of your surroundings.
In this particular case I think perhaps a better approach would be to allow apps to bypass App Store restrictions so long as their source code is public and binaries match that code. This would naturally deter those with shady intentions, allow FOSS projects to thrive, allow both manual and automated third party vetting of apps, and help users better know what they're getting into.
All of this is: Apple taking further control of the experience.