I am currently working on porting Museeks [0] from Electron to Tauri 2.0, mainly to reduce the memory and app size footprints, which are the main things everybody complains about with Electron.<p>What I really like:<p>- the dev experience is stellar and comes out of the box. No need to setup binary compilation, webpack, vite, hot-reload, TS compilation for back-end, etc yourself. You can pick your favorite JS framework with Vite, during setup, or use a Rust frontend (kind of what electron-forge is doing, but it is buggy, and landed yeaaaars after Electron was released).<p>- the architecture makes sense (commands, security, plugins, all very well-designed)<p>- they provide official plugins for common-usecases (SQL, config, etc)<p>- Rust is fun and interesting to learn for folks like me used to high-level languages like JS or Python<p>What I don't like as much:<p>- facing webview-specific UI issues (feature X does not work on Safari, Y not on gtk-webview etc), with Electron, you know if X works on Windows, it will work on Linux or MacOS<p>- some rough edges with the framework or the ecosystem (not as mature or dev-friendly as npm's or Electron), but the crates (and Tauri's) maintainers are very friendly and reactive.<p>- the focus on mobile apps, It seems like a very different space, and it feels weird to try to build with big mashup framework. I would rather have them work on more integrations, but whatever.<p>- changes in the Rust backend can take minutes to compile, and rust-analyzer is damn slow.<p>Overall I'm really happy and having a lot of fun. I will keep working on this port and release it when I can. Kudos to the Tauri team, what you are building is awesome :)<p>[0] <a href="https://museeks.io" rel="nofollow">https://museeks.io</a>