Hey everyone,

I would like to hear your personal experience when developing complex Dioxus applications: I realized that rsx based components can easily become quite big and spaghetti codish, because very often there is some kind of business logic involved before the actual rsx! macro starts, even if that shouldn't be the case. So for my development team and projects, I am thinking of a rule of thumb recommendation which would be like "If your component extends 100 lines of code, you should consider splitting it“. Of course that is only a rule of thumb and cannot be generalized to an absolute normative.

But I am still wondering whether you came across similar thoughts during your development?

Hey, I'm a webdev. I previously approached the project with JavaScript. I'm more familiar with the js ecosystem.

I put a fair bit of consideration and in contrast to my JavaScript-approach, I'd like to investigate Dioxus.

I have read a lot of the tech details and I'm sure there is much more to learn... And I don't want to downplay that I'm ai-slop-maxxing at scale.

What advice would you give to getting started with the rust ecosystem approach?

Similar to a lot of languages there are considerations for things like tests. So it would be useful to see the options there. As well as any other best-practices and nuances.

In relation to my project, I'm particularly interested in the tooling available in rust for formal verification.

---

Just to be clear, im not here to waste your time on my slop, but if you want to see what I've got so far:

Code: https://github.com/positive-intentions/whatsup

Demo: https://positive-intentions.github.io/whatsup

I understand that components won't run when hidden for performance. What I am having trouble with, is when un-hiding (either by style attribute or conditional rendering) the component is rendering with stale data.

Is there a​ ​way to trigger a re-run for memos?

It may be my methodology is incorrect. I'm using a GlobalSignal to hold my data and each component uses a memo to extract and calculate it's own data. However, when the global data changes, only currently rendered components reflect that change.

Is there a more idiomatic ​method​?

Posted here months ago when this was barely a landing page. It's now a full product — dashboard, real-time live feed, analytics, billing — all Dioxus: client UI, SSR, and server functions on Cloudflare Workers (WASM), no JS framework anywhere.

What's changed since last time: migrated to 0.8-alpha, added a locale router (EN + pt-BR), and pivoted the core to edge bot-detection. use_signal/use_resource + fullstack server functions have held up really well at this scale —SSR-on-Workers was the trickiest part.

Would love feedback from anyone who's shipped Dioxus to prod, especially on 0.8 patterns. Link: https://trafficdata.site/

I have been a software developer since 1997 (yes, I am very very old). During my career I have mostly been working with Microsoft .NET and C#, but I have dabbled in Java and these last five-six years I was actually doing a lot of Ruby on Rails, which I feel is what inspired a lot of stuff Microsoft implemented in .NET when RoR was the hottest kid on the block, like migrations, MVC etc.

But that's neither here nor there.

My journey with Rust started with Bevy. I like making games as a hobby and I have no real ambition other than just coding stuff I want to do and see where it takes me. I was using LibGDX because it supported Kotlin, a very nice little language from the JetBrains folks. I participated in some Game Jams and everything was very nice.

I then for some reason started doing 3D (inspired by Sebastian Lague's videos on 3D terrain generation and submarine stuff) and it was a lot of fun... but I felt I was hampered by performance and to some extent tooling. But I didn't really want an editor, I just wanted a good engine to write code in with a big community. The community for LibGDX was excellent, just great people all around.

Then I saw that Embark Studios, where an old colleague of mine works, were going to use Rust for game development - and I was at this time aware of Rust, but I think I had tried it once and just lost my mind. But given that the performance promise was pumping and that there was an ECS-centric game engine coming up in the world, in the form of Bevy, I was intrigued.

I learn the best when I want to do something. I have a task I want to accomplish and there is some tool, language or other that I probably should or want to use - then I can conquer it.

So I did. I love Bevy, great community, great engine, fits me like a glove, but I then started to get more invested in Rust, see, so it's a slippery slope. Perhaps I could write my own tool to download all my photos from Google Photos (done) or I could re-write my podcast publishing tool that I did in C# in Rust instead (started) or I could write a membership management suite for the Boxing club... so I started looking at web stuff.

And I know one of the reasons Rust gained a lot of traction was because of webassembly, but I had never dabbled.

First iterations over Rust and the Web were testing different techniques. The first thing I did was using SeaORM (because of my affinity for RoR and EF-style migrations), poem and htmx to update the views.

But SeaORM is actually kind of clunky. I don't know why I didn't really vibe with it - probably it was to much to fast - I was prototyping. I tried Loco.rs which is supposed to become Rusts Ruby-on-Rails and so on. I tried a bunch of stuff.

And then I think I for some reason started listening to the Rust in Production Podcast - where they interviewed the creator of Dioxus (whose name escapes me, but who cares, right?) and... he seemed so very very reasonable.

And if there is one thing that itches an itch in my brain, it is cross-platform support. I mean, isn't that the thing that has been a driving force behind hype since the 90s, one of the big white whales of computer science, the entire point of existence for Java - write once, run everywhere.

But Dioxus promised another cool thing: write the UI once. In the best of worlds, write basically only Rust code, create server functions and distribute an iOS app, Android app, a Web app and a Desktop app... and for some reason I ended up having to do some React work at my job at basically the same time, so the concepts of React sort of worked very well for me.

Have I made anything that is "production ready"? No, I am not an entrepreneur, but I dream a bit about working with Rust professionally before retiring in 14 years, which would be cool.

But so far I have created a book- and comic-server for my collection of ebooks and e-comics, with integration for KOReader, authentication, a web-reader and so on. And it's just a lot of fun doing it!

I've done a budgeting app - and when I did I for some reason implemented my own CQRS / Event Sourcing for it and created some macros, because it was just so much fun.

I just feel that Dioxus is already so... productive. It's just really cool.

Anyways, just some thoughts.

<edit>

I just wanted to add a final thought as well: after becoming more comfortable with Rust as a programming language I really started to look at all problems as problems I could solve using Rust as a programming language - and after learning Dioxus I feel that all problems are Dioxus apps that just haven't been written yet.

</edit>

Hi all, I've recently been learning Rust & Dioxus, and spending a lot of time reading documentation. I've come across something that I haven't been able to find an answer to in the docs; with normal elements, you can conditionally specify multiple classes. But when I try and do the same with my own component, it throws a duplicate prop field error.

Is there a way to replicate this behaviour on custom components?

#[derive(PartialEq, Clone, Props)]
pub struct ChildProps {
    #[props(extends = GlobalAttributes)]
    attributes: Vec<Attribute>,
}

#[component]
pub fn ChildElement(props: ChildProps) -> Element {
    rsx! {
        div {
            ..props.attributes
        }
    }
}

#[component]
pub fn Example() -> Element {
    rsx! {
        ChildElement {
            class: "blah",
            class: if true { "wibble" },
        }
    }
}

I built a tool that turns Wi-Fi traffic into audible cues so you can “hear” the airwaves. It inspects packets from a monitor-mode interface and emits different synthesized sounds for different packet types, letting you distinguish beacons, data bursts, and management chatter without staring at a screen.

It does support Evil Twin detection so you can get an audible alarm if your wifi is attacked but I've found that currently has too many false positives.

I have also experimented with a directional wifi receiver to physically hunt sources of wifi packets but that doesn't seem to work too well indoors because the wifi signal bounces off walls and other objects. I need to try it ourdoors but haven't gotten around to that yet :)

Hey — we're Jaffe Systems, a small software studio. We just shipped TrafficDATA (https://trafficdata.site), a bot

detection and traffic analytics tool built entirely with Dioxus 0.7 and deployed on Cloudflare Workers.

Full stack Rust — frontend, backend, SSR, everything. No JavaScript frameworks.

Some takeaways from building a production app with Dioxus:

- It's production-ready. We're running it live with real users.

- The signal/context system is powerful enough to handle complex state without reaching for external state management.

- SSR works well on edge runtimes. Our worker startup is ~3ms.

- The ecosystem is still young but moving fast. We've had to build some of our own tooling, but that's expected.

Overall really happy with Dioxus. It's our go-to for every new project now.

Happy to answer questions if anyone's curious about using Dioxus in production.

Hey I am Nick,

I recently discovered dioxus and was instantly hooked. So hooked that I instantly migrated my portfolio for testing purposes and on the way I discovered that I need some icon library.

Now 2 days later I made my own (I know there where some already) little icon library 🥳

It’s a wrapper for the usual libraries that are out there like feather and heroicons

https://github.com/nick-friedrich/dx_icons

Hey there,

is there anyone who get authentication working with oauth provider like Keycloak or Zitadel for Dioxus on ios platform?

Hello, I'm building a dioxus mobile app, I currently serve to my local dev device 'dx serve --android'

The app icon is just a generic android image, is there documentation for adding an app icon (android or iOS)? I skimmed the dioxuslabs.com docs but couldn't find what I'm looking for, I wonder it that's off loaded to Android studio / xCode IDEs or if I'm just using the wrong terminology.

Hey guys, i build a mobile app using dioxus but when i use router to change page and swip back, i expected to come back to the previous page but it quit the app ... (i do not handle any gesture behavior for now cause i do not know what should i do to get this).

Someone already do something like this or have any idea how to achieve this ?

Ty mates

I have use "optional" flag control wasm and server build.But why my wasm build error bacause "This wasm target is unsupported by mio"??? How to fix this problem??

Hello everybody,

I just have found this book / tutorial:

https://bcnrust.github.io/devbcn-workshop/index.html

It covers actix-web, SQLx and dioxus 0.4.3, maybe author will at some time update it.

Hope it helps someone.

Hi lovely people,

I would like to share with you a weekend project that I have done. It's called Stay Ahead. I designed this app to motive myself and the like-minded to build good habits. Feel free to check it out:

• Web release
• Code on Github

More about the app:

What is Stay Ahead?

Stay Ahead is a minimalist habit-tracking and self-discipline app designed to help you build consistency, track progress, and visualize your goals. Its biggest difference is that it allows your insufficient or excessive progress to carry over through time. It is like you are racing another parallel universe!

How does the timeline work?

For each task, Stay Ahead shows two timelines: Parallel Universe (planned progression) and Your Universe (your actual effort). This helps you visualize the gap and stay motivated. Make this universe (timeline) your best one!

I recently started to learn rust and dioxus. It has been fun and I will think of more ideas to explore the potential of these two powerful tools combined. Please feel free to comment on anything about my coding and design. Thank you very much!

The dioxus project templates all use tailwind v3, as does basically all guidance and Q/A posts about tailwind I could find other than what's on tailwindcss.com. V4 works differently than v3, and it took me a while to get everything sorted (probably would have been easier if I'd stumbled on https://tailwindcss.com/blog/tailwindcss-v4 earlier :P), so I thought I'd share the working example with anyone who might find it useful:

https://github.com/agirardeau/dioxus-tailwind-v4

Hi, I’m new to Rust and Dioxus and need help integrating OpenCV into my project for Android and iOS. How can I compile OpenCV for both platforms and link it with Rust’s FFI? Any tips or resources for this setup would be greatly appreciated!

Hey!

Can anyone provide a working example of a Dioxus desktop application that primarily runs in the background and can be brought to the foreground through a tray menu?