iOS AUv3 and Application do not share the same documents

One implication of the fact that AUv3 and Application do not share the same Documents is that content created in the AUv3 is not accessible from anywhere else (as opposed to the Application, which saves in On My iPad | VMPC2000XL).

I have 2 ideas:

File synchronization: When starting the standalone app, documents from the AUv3 container are copied into the standalone one. But this is a hairy approach -- what to do when a file already exists, and should files from the standalone container also be copied into the AUv3 one? There's plenty of questions to ask and decisions to take for the developer. Moreover, it's confusing to the users that they need to start the standalone app to make this sync happen. This is what https://ruismaker.com/ seems to be doing.
Setting up an additional folder that is shared between and accessible by both the AUv3 and the App. Unfortunately in this approach this folder is not accessible via the Files app. This solves the problem of seeing the same docs in both the AUv3 and the App, but it doesn't solve the problem of accessing AUv3 content outside any VMPC2000XL.

It seems inevitable that the Standalone app has to serve as a proxy. That said, another idea I have is to add Export functionality. Not sure if and what is possible here though. I know AUv3 has read access to anything inside On My iPad. I don't know about write access, though.

Some more stuff to draw inspiration from: https://forum.juce.com/t/ios-auv3-save-load-custom-presets/54140/5

izzyreal / vmpc-juce

iOS AUv3 and Application do not share the same documents #40