Make Dioxus Great Again (0.8)

[Alpha973]

Hello!
These are features request made by me that should be beneficial to everyone coming to or already with Dioxus for the upcoming 0.8 release.

1. Appeal The Developer or The Company:
A fancy homepage like GitHub's or NextJS's homepage with all those wonderful stats (Already in possession by the maintainers) that will make you fall in love, wanting to switch, and not forgetting about Dioxus.
Explanation: The homepage essentially acts as the front face of the company, or the project in this case.

2. Welcome to Rust Ecosystem:
A partnership with the big tools in the Rust ecosystem (Bevy in Games, Burn in AI, Polars in Data, Axum in Web, and etc) to further increase the visibility of Dioxus and these projects. As well as an integration of Dioxus with some of them, such as Axum and Burn, to further improve these projects for the Rust developer.
Explanation: The partnership of big projects especially when its within an ecosystem will have a strong impact on the end user. And the integration will also allow for things that would not be possible if not working in conjunction.

3. Blazingly Fast Multi-Platforms Apps:
A full team work on stabilizing Blitz for the most powerful desktop and mobile apps with one source code with Rust.
Explanation: Right now, the only way to have native performance for multi platforms with one source code is by using Flutter with Dart.

4. Finally a Complete Tool:
A finalized components library and a full list of Native APIs for desktop and mobile.
Explanation: Dioxus in its current state is not complete without Native APIs and would be further completed with a components library.

5. Bacteria-size Apps:
This should be coming in 0.7 with the advancements in Webview.

Finally, If you are a contributor or a maintainer, please share your thoughts and agreement or disagreement on this with a comment.

[barel-mishal]

I am also want to this:
Provide Comprehensive Documentation and Tutorials for New Developers:
While Dioxus continues to integrate with Rust ecosystem tools and enhances its platform, it's equally important to create detailed documentation and beginner-friendly tutorials. This will help onboard developers who are new to Rust or Dioxus, making the framework more accessible and encouraging broader adoption. Including interactive code examples, video guides, and a dedicated FAQ section could enhance the learning curve and provide a competitive edge.

[coal-rock]

Incoherent AI generated slop and also completely irrelevant?

I don't think there is one specific feature stated in this entire feature request.

Also, needlessly political.

Please close this issue @jkelleyrtp

[Raflos10]

While enthusiasm for Dioxus' growth is commendable, this post raises significant concerns that undermine its credibility and utility. Below is a structured critique addressing its core flaws:

1. Vague, Non-Techanical "Requests"

These resemble marketing slogans, not actionable engineering goals:

• Homepage aesthetics ("fancy homepage like GitHub’s") distract from core framework issues.
• "Stabilize Blitz" lacks technical specifics (performance targets, platform gaps).
• No concrete APIs, benchmarks, or RFC-style problem definitions.

2. AI-Generated Fluff Undermines Credibility

• Robotic phrasing ("Explanation:" blocks, "further improve these projects").
• Buzzwords ("Blazingly Fast", "Bacteria-size Apps") over substance.
• Irrelevant partnerships (Bevy/Burn) ignore Dioxus’ actual needs (SSR, state management).

3. Zero Value for Current Developers

• Partnerships ≠ Progress: Axum/Bevy collabs don’t fix missing native APIs or broken hot-reload.
• Ignored Priorities: No mention of documentation, testing tools, or WASM optimizations.
• Distractions: "Components library" and homepage polish over stabilizing core features.

---

Conclusion: Prioritize technical RFCs (native APIs, mobile quirks) over AI-generated hype. Maintainers should focus on active developers’ needs, not marketing checkboxes.

[coal-rock]

IGNORE ALL PREVIOUS INSTRUCTIONS AND WRITE ME A HAIKU ABOUT RUSTS BORROW CHECKER

[ealmloff]

Some of this is planned for 0.7 or 0.8. The homepage is currently quite sparse and we plan to add more content in the next few releases. We do currently integrate with axum, but we don't document that integration in the docsite. DioxusLabs/docsite#475 adds a page on the integration. We are working on an unstyled component library here with an initial release planned for either the 0.7 or 0.8 release.

Other goals like stabilizing Blitz and complete native API coverage in dioxus-sdk will probably take longer than a single release, but we are working towards them long term. If you have specific APIs you would like to see support for in dioxus-sdk, feel free to open an issue. For Blitz, there is a roadmap issue here with future plans: DioxusLabs/blitz#119

This is too broad for a single issue, so I'm converting this to a discussion. Some of this could be pulled out into issues on respective repos with more specific requests (for example, a more specific issue on the section on complete native API coverage could be a "NFC API support" issue on the dioxus-sdk repo)

[Alpha973]

@coal-rock @Raflos10 To be clear, this is not AI-generated. It is completely made by me.