Desktop/Mobile App

[alexbmills5]

Could this easily be wrapped in a capacitor app and or electron app?

Authentication process would be similar to a plex or jellyfin server and could even hold multiple "servers".

If anyone is interested I could give this a shot as well, not sure if the developers would want this under their own repo.

[Katacc]

Would be really handy, especially with mobile/desktop notification support!

[Rand-o]

definitely think so, I got it all set up and got my friends to connect however the webpage on mobile in its current state is not really useable. Chat box unable to click, UI elements unviewable. Once that is fixed me and my buddies will have everything we need

[Kruzayn]

I made a quick wrapper in electron and added push to talk capability and ability to specify a server. heavily assisted by AI in creation, no warranty or support. if others want to mess with it while waiting on an official app, have at it. files.kruzayn.com npm. node, electron. if the admin/maintainer/creator of sharkord hates this feel free to delete my post. If the app doesnt work its not a sharkord issue at all. I can make the npm files available too if people want to mess with it. i could also rip out the PTT stuff to make it lighter and have less risk.

[deranjer]

I really want to try out electrobun for this, I might play around with that on my own.

This being a monorepo not sure if they want to share UI as much as possible across the web client and desktop/mobile clients (harder with mobile for sure).
@diogomartino Sorry for the ping, but hoping you could provide just a bit of direction on how tightly coupled you want the web client UI code and the desktop/mobile ui code.

[diogomartino]

I've looked into electronbun in the past, not sure if it's mature enough tbh. But I haven't really tested it.

[deranjer]

Just an update on this. I did play around with electrobun, great potential, but a lot of rough edges. For example in Windows had so many issues trying to get native notifications to work. That and the general lack of documentation seems to be a bit tricky. My personal recommendation is to stick with the tried and true electron, even if it is a bit bloated.

I'm willing to start work on that, but I do need some guidance. My preference would be to split out the "pure ui" elements from the client into a shared "ui" folder, and as much as possible reuse the same UI components in the desktop application. I really don't have much experience in monorepos, so it might take me a bit to do that separation, which will for sure cause some merge conflicts that will need to be worked through. However, recreating essentially the exact same layouts seems like a massive pain to maintain going forward and kind of defeats the purpose of using electron in the first place.

Let me know how you want to proceed and if you are okay with me taking a crack at this @diogomartino.

[kulzae]

Would a standalone app be a prerequisite to having mute / deafen hotkeys? Not sure if having keybinds that work when the window isn't active is possible for something browser based.

[diogomartino]

Probably, yes.

[schemen]

A dedicated app may be useful for proper audio routing is as well, since it would be able to capture a shared programs audio feed whereas a browser can't do that, yet.