Mvp In Rust: One Team, One Language, Three Platforms In Two Weeks. I Will Not Promote

Hello, startupers and entrepreneurs!

My English is limited, so I polished this text with ChatGPT to convey the ideas as clearly as possible.

Where the idea came from

Recently, an HR manager from the UK contacted me: his company was looking for a Dioxus developer to unify their entire stack. He expected to gain:

• One language instead of separate front-, back-, and mobile-specialists
• One team capable of handling all development
• Lower costs through role consolidation and tighter integration
• High performance thanks to Rust

The project never took off—reasons unknown—so I decided to assess several Rust cross-platform solutions myself.

Why this matters for startups

• Single codebase for web, desktop, and mobile
• One Rust team instead of three specialized teams
• Rapid MVP launch without learning multiple technologies at once
• Transparent time & resource estimates: my prototype took ~2 weeks in evenings and lunch breaks; a comparable React+Node stack typically needs at least 1–1.5 months

Phase 1: Dioxus

Pros:

• React-style model (hooks, state)
• Supports Web, desktop, and mobile

Cons:

• Limited examples and documentation
• Larger browser bundle than common alternatives
• Still maturing—better suited to enthusiasts than enterprise

Experiment: Tauri + Leptos

Why this combo?

• Entire back- and frontend in Rust—no language switching
• Tauri delivers cross-platform packaging without dictating UI tech
• Leptos enables fast SSR (Server Side Rendering) web pages and a lightweight CSR (Client Side rendering) client

Outcome after two weeks:

• A ToDo app with a single codebase
• Web: fast-loading, SEO-friendly SSR pages
• Desktop/Mobile: native Tauri shell using the same UI code
• Server: Axum + SurrealDB
• Tooling: cargo-make, trunk, and tauri-cli configured once and reused unchanged

What’s next—and your thoughts

I see real advantages for startups: fewer roles, fewer technologies, and a shorter development cycle.

Questions for you:

1. How appealing is the idea of a unified Rust codebase across three platforms?
2. Would you adopt this approach even if you don’t write code yourself?
3. Who has used Dioxus, Tauri, or Leptos in business projects—and what were the results?
4. What risks do you see in dropping separate “frontend” and “backend” teams?

I’d love to hear your feedback and real-world examples! If you’d like to discuss further, leave a comment.