Part of the selling point of DPS is that it "supposedly" creates apps that will work in either orientation... many users prefer to read or browse in a portrait orientation... this is a perfectly logical use case and something that your application is supposed to support.
Yet instead of trying to offer any real solution or any information that might actually help me solve this issue you simply ask me why we are producing a dual-orientation folio?? Really starting to wonder if I am getting trolled here...
So from your answer above it sounds as if DPS is smart enough to recognize shared video assets between portrait and landscape orientations... is this also true for images / type?? I am still trying to understand why doing an app in both orientations that uses all the same assets "will almost double your folio size" (your words not mine)
Is there ANYTHING that we can do (short of ditching one orientation) to help reduce the file size of our application (while keeping the dual orientation)?