Neither Tauri nor Dioxus is trying to be flutter. The only similarity is that those projects exists in GUI space.

Tauri is an electron alternative. It handles windows creation, rendering of web pages as well as IPC between frontend and backend.

Dioxus is a frontend framework similar to Next.js and other react-based frameworks.

Flutter uses an entirely different approach to GUI.

The linked article literally states: Our goal is to build a "Flutter but better."

I never know how to position Dioxus, so would be happy to have some 3rd party insight.

When I say we use a webview, people immediately jump to Tauri. But we're very architecturally different than Tauri. No WASM on native, just a regular old executable.

When I compare us to Flutter, people immediately think of Flutter's negatives (poor web support). We have excellent web support (DOM is 1st class).

When I compare us to React Native, people immediately think the web is 2nd-class and then wonder why we don't implement NSScrollView and all that.

We are shooting for something like Flutter (web, desktop, mobile, embedded) but where the web is the defining feature.

As someone outside Dioxus, how do you think I should describe it?

> We have excellent web support (DOM is 1st class)

ah I missed that... I read something about Flutter and WASM and kind of assumed it was rendering to canvas

that's very nice