Plans for a web version?

[poVoq]

Since this seems to be Tauri based, any plans for a web-version?

It would probably need a webrtc proxy similar to Mumble-web, but there is a codebase for it here: https://github.com/Johni0702/mumble-web-proxy

[SetZero]

Hi! Thanks for your ticket.

Sadly from my understanding tauri doesn't support direct deployment to the web ( tauri-apps/tauri#3655 ). If something like this is wanted a bit more rewriting of the code would be needed to wrap all tauri calls into respective web calls. It would be doable but right now this isn't the primary goal of this project, as I firstly want to have a desktop and (later on) mobile app.

But if you (or someone else) wants this feature feel free to create a PR.

[FutabaWasuke]

Hi! Thanks for your ticket.

Sadly from my understanding tauri doesn't support direct deployment to the web ( tauri-apps/tauri#3655 ). If something like this is wanted a bit more rewriting of the code would be needed to wrap all tauri calls into respective web calls. It would be doable but right now this isn't the primary goal of this project, as I firstly want to have a desktop and (later on) mobile app.

But if you (or someone else) wants this feature feel free to create a PR.

Do you have more ideas about Fancy-Mumble's mobile app to talk about now?

I'm really looking forward to any updates or new news about FancyMumble. 😍

FancyMumble looks very promising to be the main Mumble client we'll use in the future, it's elegant in every way.

[SetZero]

Hi @FutabaWasuke
sorry for my late reply, I was a bit busy lately.

Regarding the mobile version:

• Tauri 2.0 allows building for Android and iOS (But it is currently in Beta, so it might take some time until it is officially done)
• I'm currently mostly focusing on Android, because I don't have an iOS device
• I tried that on the current Fancy Mumble version and it is partially working.
  • It needs some changes for some libraries I'm currently using (e.g. https://github.com/image-rs/image is only partially working, as the jpeg support is broken for android)
  • There are zero adaptions on the layout yet, so it is basically a reduced size version of the desktop client
  • The paths are not working, so it will basically "crash" on startup, when it tries to load the certificates
  • I haven't set-up any android permissions, which also causes the app to crash, as it tries to access a path it doesn't have permissions to
• As you might have guessed, it's all pretty pre-alpha and not really useable, but I try to keep the support up, so that I don't deviate too much from a somewhat "working" Android version and can later on actually support it

Here is a sneak peek of how it currently looks:

[FutabaWasuke]

Thank you for your reply, I'm really looking forward to these! Appreciate all you've done.