Split App in two

[olanod]

This is more of a conversation starter to know how we are going to architecture the next stage of the application. I believe splitting the app in two will help with separation of concerns but more importantly with performance and usability.

The main WASM file at this early stage is 20Mb+, in budget phones and slow internet areas having to download such a big file before start interacting with the application is a no go. The Matrix client and later the blockchain (light)client are heavy pieces of code that should be moved to run separately, in the Web this means a WebWorker and on native it could be a separate process.

How the main application communicates with this "messenger proxy" is up for discussion but we need to,

• Keep it web friendly or abstract the transport depending on the platform.
• Have a simple API, the idea is to not need an entire Matrix client on the Dioxus side.
• Be async, the UI never blocks and should avoid full-screen "loading" screens, we should fire actions an later react to status updates or streaming answers.