rustyui-components 0.1.0

Shared component library for RustyUI.
Documentation
  • Coverage
  • 50%
    1 out of 2 items documented0 out of 1 items with examples
  • Size
  • Source code size: 4.12 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 992.13 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 12s Average build duration of successful builds.
  • all releases: 12s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Repository
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • jamshaidnasar

RustyUI

A modern Rust UI framework built by Zenvor Technologies, aiming for one framework across web, desktop, and mobile with shared components and a single programming model.

This repo is an early-stage scaffold for a full Rust UI ecosystem. The goal is to create a cohesive set of crates that deliver a React-like developer experience in Rust without locking you into a single platform.

Vision

  • One mental model for UI across targets
  • A core runtime that is renderer-agnostic
  • First-class tooling and ergonomics
  • Shared component libraries that work everywhere

Why Now

Rust has excellent libraries (Yew, Dioxus, Iced), but no clear dominant standard. This project aims to fill that gap with a unified architecture and strong tooling.

High-Level Architecture

  • rustyui-core: UI runtime, state model, layout abstractions
  • rustyui-components: shared component library
  • rustyui-web: web renderer (WASM + DOM)
  • rustyui-desktop: desktop renderer (native windowing)
  • rustyui-mobile: mobile renderer (iOS/Android)
  • rustyui-cli: dev tools (project scaffolding, dev server, bundling)

Repo Layout

  • Cargo.toml: workspace definition
  • crates/: all framework crates
    • core/
    • components/
    • web/
    • desktop/
    • mobile/
    • cli/

Project Status

Early scaffold. No public API stability yet.

Near-Term Roadmap

  • Define core component model and lifecycle
  • Choose layout engine strategy
  • Define renderer boundary traits
  • Build a minimal web renderer with a working counter example
  • Establish repo-wide style and contribution guidelines

Long-Term Goals

  • Platform parity with a single codebase
  • High-performance rendering and incremental updates
  • First-class dev tooling (hot reload, component preview, diagnostics)
  • A component ecosystem that feels cohesive and reliable

Getting Started

For now, this is just a workspace scaffold:

cargo check

Contributing

This is a concept in early formation. If you want to help, open issues with concrete proposals (architecture notes, API sketches, prototype benchmarks).

Names

  • Company: Zenvor
  • Framework: RustyUI