I was referring to the desktop plugins that the OP was asking about.
Obsidian on iOS is largely a web view, so it can just run most of the same JavaScript plugins as on the desktop. Zotero's iOS app is a real native Swift app with native UI, so it can't support plugins in the same way.
A future version of the iOS app could potentially include a JavaScript API that allowed user-installed plugins to perform certain explicitly exposed actions, but each API would need to be anticipated and implemented ahead of time. We've been adding sandboxed APIs for specific functions to the desktop app, with many more coming soon, and some of those would likely be supportable on iOS in the future, but it wouldn't be anything like the unfettered access to modify Zotero internals that desktop plugins have now.
A more comparable example would be the Office apps for iOS, which allow JS-based plugins via fixed hooks, with most UI in a sidebar. That's much closer to what we'd be able to offer in some hypothetical future plugin system.
(Also note that essentially all documentation you see on this site is going to be about the desktop app.)
Obsidian on iOS is largely a web view, so it can just run most of the same JavaScript plugins as on the desktop. Zotero's iOS app is a real native Swift app with native UI, so it can't support plugins in the same way.
A future version of the iOS app could potentially include a JavaScript API that allowed user-installed plugins to perform certain explicitly exposed actions, but each API would need to be anticipated and implemented ahead of time. We've been adding sandboxed APIs for specific functions to the desktop app, with many more coming soon, and some of those would likely be supportable on iOS in the future, but it wouldn't be anything like the unfettered access to modify Zotero internals that desktop plugins have now.
A more comparable example would be the Office apps for iOS, which allow JS-based plugins via fixed hooks, with most UI in a sidebar. That's much closer to what we'd be able to offer in some hypothetical future plugin system.