Great post. I entirely agree that the “arbitrary code” part is what might trouble plugins for PS on iOS. I don’t agree that it would be hard to deploy them or that they have to be in the bundle, if they were allowed though. That’s as simple as PS providing a Photoshop/Plugins folder in Files.
It isn’t a “it’s hard to do” problem, it’s an issue with how Apple wants security to operate on iOS coming into conflict with the lassiez-faire approach to security desktop OSes have had historically. That lax approach has helped in many ways create the culture we see around extensibility/tweaking/etc, so it’s not inherently bad, but it isn’t the sort of “don’t trust, verify” world connected devices tend to live in these days.
Yes, they *could* just do an App Store rules change and let apps load arbitrary code from outside their own bundle (or ship their own JS interpreter, etc, etc). But if they haven’t budged yet, I don’t see them doing it now.
Apple would want these signed, and deployed through the App Store. That requires dev work on their part, and creates a platform specific process plugin devs would have to go through during their ports. All things that delay the ability