Dioxus 0.7 Roadmap

[jkelleyrtp]

Dioxus 0.7 Roadmap

Dioxus 0.7: next release of Dioxus with a scheduled release date of March 31, 2025.
Focus: QoL, cohesiveness, community, release cadence, and shipping long-standing work.
Timeline: January → March (3 month cadence)

• January: address current bugs, QoL, small features, and initial native integration, design
• February: Work on hard/big stuff - split, patch, component library
• March: Release Cycles and bug fixes

Office-hours video: https://www.youtube.com/watch?v=_t2O2TnFOpQ

Headlining Features

• Dioxus-Native Renderer and Blitz 0.1
• Rust Hot-Reloading via Binary Patching
• Component Library Primitives
• Full-stack improvements including better error types, websockets/SSE, and smaller binaries
• Integrated Tailwind V3 and V4 support for Dioxus CLI
• Improve velocity (CI, auto-releases, staging, semver-checks)
• Telemetry Integration in dioxus-cli (anonymous and opt-out)
• Playground on website
• Component library on website
• Video Tutorials and “Vlog” content

January: fixing bugs and QoL for 0.6

• Address most bugs in the issue tracker (currently 141 issues labeled “bug”)
• Address QoL items (around 80 items considered “papercuts”)
  • More complete documentation
  • Mobile device dx serve support
  • Flakey docsite SSG
  • NixOS users bring a lot of issues
  • Hot-reload for desktop apps losing placement and app route, etc
  • OpenSSL non-vendored fix
  • Rework FileEngine API
• Better, faster CI for more reliable releases
  • harnesses for CLI, bundle, hot-reload
  • auto-release workflow (ie markdown-based posting)
  • Bundle sizes, build timings, screenshots?
• Fullstack Tweaks
  • Integrate error types with suspense and HTTP status codes
  • Expose WASM builds of server for Cloudflare worker deploys
  • Integrated WebSocket support
  • Document Axum extension in guide
  • First-party dockerfile
• Roll out playground on docsite (hidden at first)
• Videos: hot-dog tutorial and something casual

February: work on larger features

• Integrating current dioxus-native into dioxus itself (headed by @nicoburns)
  • Should we migrate to winit in this release?
• Component library primitives (headed by @DogeDark)
  • Should we attack just the primitives or go for a full solution?
• Binary Patching integration (headed by @jkelleyrtp and @ealmloff)
• Improved Fullstack Hot-Reloading Engine
• Videos
  • Project showcase?
  • How Dioxus works?

March: Release and Testing

• Roll out component library on docsite (hidden at first)
• Several Alpha releases
• Dogfooding the new Dioxus features, fixing bugs
• Landing page and marketing materials
• Releasing 0.7
• Videos:
  • Blitz In-Depth
  • Dioxus 0.7 Release

How the community can help

Several areas that we need help!

• Working down our very large list of bugs https://github.com/DioxusLabs/dioxus/issues?page=5&q=is%3Aopen+is%3Aissue+label%3Abug
• Blitz is still quite young and missing many event types (mouseover, forms) and widgets (input types, iframe, etc)
• Dogfood Dioxus and share your experience - help us maintain a list of “papercuts” in the framework and then help fix them
• Our documentation is rapidly improving but still isn’t perfect - helping write new sections or review existing sections

[mcmah309]

I thought I’d drop this here in case it was missed - Thoughts on the planned component library: #3716

In addition, just adding something like recommending using https://daisyui.com/ (or other) in the docs would accomplish the goal here without taking up any current or future developer resources.

[Sitin]

I am curious, how far are we from 0.7 at the moment?