I'm pretty good at Rust, and Go is pretty easy - both compile to wasm or desktop native and have web/dekstop UI toolkits that have tiny memory footprints see:<p>1. https://www.egui.rs/
2. https://gioui.org/<p>I find using slack, discord, and zoom unpleasant.<p>I've been toying with writing a zoom and slack replacement native for all platforms in either Rust or Go.<p>Should I do it?<p>I don't want to build it - and be the only one to use it - so I'm hoping I can get enough inspiring comments to go for it.
I think you might want to dig into what you find unpleasant about them, then see if other people have the same issues and are willing to go through the trouble of changing platforms for it.<p>It will definitely be a huge challenge and I think "native apps" and small memory footprint is only relevant to a small group of people.<p>> I don't want to build it - and be the only one to use it - so I'm hoping I can get enough inspiring comments to go for it.<p>In that case you should think about your marketing/sales plan first. How are you going to get users? Why would they switch? Who will you target? Why do people choose certain tools? Why will your tool be better than the existing ones? etc etc. Validate these things cheaply before you start building for months.<p>I can give you my personal 2c: I use both Zoom and Slack and am quite happy with them. Tbh I am unlikely to switch because my clients use them + they are performant enough; I rarely have any noticeable issues. So for me, just a native client would not convince me to switch.
There's Tauri [1], which seems to be a very good Electron alternative written in Rust.<p>[1]: <a href="https://tauri.studio/" rel="nofollow">https://tauri.studio/</a>
Basically - I have a full time job, so I need to be convinced that spending another 5 - 8 hours a day on a zoom replacement over the next few months is worth the trouble - or find a way to fund myself to do this.