Would it be possible to allow native apps to use Delta Chat as a transport between the various users, to persist the data, and to provide the identity of the users? I would expect:
The user probably needs to have Delta Chat installed to use these “native-xdc” apps
The “native-xdc” apps should communicate with Delta Chat over a standard interface, that could also be implemented by other apps (chatmail or other kinds of messengers)
They should not have access to all the user’s messages; they should only have the access to the messages that a webxdc app has, and need to be invited to each group separately just like a webxdc app
The app should not need to implement IMAP or SMTP, that should be the job of Delta Chat
All deltachat apps are actually using this strategy. They’re all nice frontends on top of chatmail core. Chatmail core is a binary you run and interact with over standard input and output with json messages. Here’s a blog post detailing how it works at the lowest level:
There are also libraries to make it easier to work from other languages, like go or python
The request uses unusual terminology and seems to blur the boundary between at least three things. Could you please share a more concrete scenario for what you would like to use this for?
Let me see whether I understand it correctly. You find the webxdc sandbox too constrained and inefficient, hence you would like to implement a game outside the sandbox (or extend an existing native app) and possibly ship it using a native package manager.
In this use case, it would be desirable if the given game would not have to rely on the lowest level RPC API that also gave unrestricted access to all accounts (or run a separate RPC loop for each such app). Rather, a more restrictive API would need to be built on top of this via which each app could be granted granular permission per-chat on a shared instance of the RPC API (or DC client). This would be very expensive to build (much simpler things could not be completed within years).
In place of having to operate a game backend, you would like to pipe the multiplayer code through webxdc update payloads or Iroh. This would already be possible without DC using WebRTC or STUN/TURN. You would like to implement access control by relying on manual invitation to private Delta Chat groups. This would also be possible to accomplish with invite code passwords. For otherwise interacting with groups by native code, separate bot daemons are usually built. What use would you have from Delta Chat?