sycamore-mac VS dioxus

Not inherently, but practically yes – currently. There are attempts to use it for desktop ui https://github.com/Submersible/sycamore-mac but in general nothing prevents you from using it as you like and implement a backend you need.

Sycamore. And before people start complaining that it's just a webview or a browser in disguise, I would like to add that Sycamore was built from the start to allow multiple render backends. Right now, there are only backends for DOM and SSR (Server Side Rendering) but it should be pretty easy to extend it to native UI frameworks. In fact, there is a POC here of Sycamore running on macOS: https://github.com/Submersible/sycamore-mac although it is right now far from usable.

I used this a bit, it was really great. Writing a Rust backend & exposing it to TypeScript was really slick!

There was one issue I ran into that made me think about jumping to Electron mid project, but I can't remember what it was now, but I think it was something like making my app bleed the entire MacOS window while still being moveable.

The other downside is you're going to be tempted to go down the rabbit hole and do everything in Rust. [1]

[1] https://github.com/Submersible/sycamore-mac

We have a web components example here: https://github.com/DioxusLabs/dioxus/blob/fd21c971038840130f...

Everything should work like normal except: attributes are not typed, custom event listeners must be implemented with web-sys

I think something like https://dioxuslabs.com could deliver native, cross platform apps and win back mobile.

While we took an in-depth look at Dioxus in this tutorial, there is still so much to learn. Luckily, Dioxus provides detailed documentation with references and cookbooks to guide developers. Make sure you check it out, and feel free to comment below with any questions.

You can probably imagine the challenges of integrating such a system in a robust way that does a good job and improves on the status quo. We felt like the Tauri implementation worked well for Tauri apps. But there’s a problem: it was so tightly coupled to Tauri that the work couldn’t be enjoyed by other projects (not even the ones like Dioxus who were using Tauri’s underlying technology of Tao + Wry).

Floneum is a graph editor for local AI workflows. It uses llm to run large language models locally, egui, and dioxus for the frontend, and wasmtime for the plugin system. If you are interested in the project, consider joining the discord, or building a plugin for Floneum in rust using WASI