I'm developing an app that opimize the user interface for different display size: 3,5'' / 4'' / 4,7'' / 5,5''.
I'm using a different set of images for each display type, so I've followed the "App Thinning" WWDC lecture in order to stay below the 100MB IPA.
The lecture start well:
- you can produce an asset for both images and datas, good!
- you can integrate it with existing process using the Content.json, very good!
- you can clusterize resources basing to the RAM size (???) and Metal version, mmmh ok...
BUT, despite being a display related mechanism (assets mainly should manage images) it is NOT POSSIBILE distinguish between display size, resolution, or other than the scale (1x. 2x, 3x).
So 3,5'' / 4'' / 4,7'' that share the same scale CANT be clustered.
Change the current app layout management in order to un-optimize the display specific optimization is NOT an option for me.
How it is supposed to do that?
Am I missing something?
Thanks for all suggestions!