Initiative Description
1. The Idea
Initiative Name
Cross-Platform GUI Desktop Apps
Elevator Pitch
The Cross-Platform GUI Desktop Apps Initiative aims to reduce ecosystem fragmentation and establish Rust as a premier choice for production-grade desktop development. This initiative brings together individual maintainers, organizations, and developers to coordinate investment in shared tooling, core libraries, and standard developer resources, accelerating the path to a mature, unified Rust desktop stack.
Why Now?
Pioneering, high-quality projects like Zed (via GPUI) and System76’s COSMIC desktop (via iced) have proven that pure-Rust, GPU-accelerated desktop environments are highly viable. However, the wider ecosystem remains severely fragmented between custom native canvas architectures (egui, iced, GPUI) and hybrid webview solutions (Tauri, Dioxus).
Currently, documentation, architectural patterns, and production best practices are not established. Developers are forced to solve low-level foundational challenges such as text layout, deep OS shell integrations and building common UI component primitives independently. Coordinated action is required to lower the barrier to entry before the ecosystem fractures further.
Initial Goals
- Improve Cross-Pollination: Establish structured communication channels for authors of different rendering pipelines and toolkits to collaborate on shared infrastructure.
- Guidance: Author comprehensive guides, architectural blueprints, and reference examples outlining how to choose and deploy current Rust GUI tools.
- Map Ecosystem Gaps: Document and categorize missing primitives across text rendering, hardware I/O, accessibility, and state management across frameworks (there might be more missing areas beside those I outlined).
2. Initial Participants
3. Activities & Outputs
Potential Activities
- Bi-weekly/Monthly Working Group Meetings: Regular synchronization, project showcase reviews, and experience sharing.
- Technical Investigations: Focused deep-dives into cross-framework primitives (e.g., assessing how
accesskit or taffy can scale uniformly across paradigms).
- Production Case Studies: Interviews and deep dives with engineering teams shipping apps in production (e.g., Zed, System76, Longbridge) to extract hidden constraints.
- Ecosystem Workshops: Community workshops and presentations illustrating how to build and optimize native applications.
- Open-Source Collaboration: Coordinating community development on shared, lower-level foundational crates and building experimental prototypes.
Possible Outputs
- Ecosystem Matrix and Guides: A comprehensive, regularly updated guide matching product requirements to specific Rust GUI stacks.
- Reference Architectures: OSS example applications demonstrating complex production patterns (e.g., large-data virtualization, native window styling, multi-threading in UI actions, etc).
4. Getting Started
Initial Coordinators
Expected Participation
- Meeting cadence: bi-weekly/monthly 1-hour synchronization meetings during the initial exploratory phase.
- Communication channels: a dedicated community subchannel within the RCN Zullip channel.
- Participant Involvement: anything that can help with the goal is welcomed! eg: OSS development on shared crates, authoring guides, submitting architectural case studies, presenting engineering showcases, etc.
Resources and Support
While detailed infrastructure and budgeting requirements will be formulated as the initiative matures, we anticipate requiring support from the RCN in the following areas:
- Ecosystem Grant Amplification: Assistance in identifying and coordinating with industry sponsors or foundation grants to fund targeted open-source tooling development (e.g., funding milestones for foundational, framework-agnostic crates).
- Event & Community Platforms: Technical support for hosting virtual working sessions, public panels, and community showcases.
- Conference and Media Outreach: Support from RCN marketing channels to secure dedicated presentation slots, panel tracks, or lightning talk sessions at major Rust conferences.
Future Development
While the initial phase focuses on knowledge sharing and alignment, the ultimate structural objective of this initiative is to guide the ecosystem toward a modular, unified "Complete Stack" for desktop Rust applications. This vision focuses on standardized, interoperable foundations across four layers:
- Unified Text and Layout Engines: Building toward shared standardization around foundational layout abstractions (like
taffy) and high-performance text pipelines (such as the Linebender organization's parley, vello, and skrifa) so new frameworks don't reinvent rasterization.
- First-Class Accessibility (a11y): Ensuring that screen-reader and platform accessibility hooks (via
accesskit) are natively embedded by default into all modern Rust render pipelines.
- Deep Shell and Hardware Integration: Standardizing cross-platform, safe abstractions for deep OS integrations, including system trays, native menus, background power-state management, biometric I/O, and secure system credential keychains.
- Render-Agnostic Component Layer: Designing specifications for high-performance, customizable UI components (comparable to the web tools like shadcn/ui or libraries like
gpui-component) that can define application layout and states independently of the underlying GPU renderer (Hard task!!!)
Initiative Description
1. The Idea
Initiative Name
Cross-Platform GUI Desktop Apps
Elevator Pitch
The Cross-Platform GUI Desktop Apps Initiative aims to reduce ecosystem fragmentation and establish Rust as a premier choice for production-grade desktop development. This initiative brings together individual maintainers, organizations, and developers to coordinate investment in shared tooling, core libraries, and standard developer resources, accelerating the path to a mature, unified Rust desktop stack.
Why Now?
Pioneering, high-quality projects like Zed (via GPUI) and System76’s COSMIC desktop (via iced) have proven that pure-Rust, GPU-accelerated desktop environments are highly viable. However, the wider ecosystem remains severely fragmented between custom native canvas architectures (egui,
iced,GPUI) and hybrid webview solutions (Tauri, Dioxus).Currently, documentation, architectural patterns, and production best practices are not established. Developers are forced to solve low-level foundational challenges such as text layout, deep OS shell integrations and building common UI component primitives independently. Coordinated action is required to lower the barrier to entry before the ecosystem fractures further.
Initial Goals
2. Initial Participants
3. Activities & Outputs
Potential Activities
accesskitortaffycan scale uniformly across paradigms).Possible Outputs
4. Getting Started
Initial Coordinators
Expected Participation
Resources and Support
While detailed infrastructure and budgeting requirements will be formulated as the initiative matures, we anticipate requiring support from the RCN in the following areas:
Future Development
While the initial phase focuses on knowledge sharing and alignment, the ultimate structural objective of this initiative is to guide the ecosystem toward a modular, unified "Complete Stack" for desktop Rust applications. This vision focuses on standardized, interoperable foundations across four layers:
taffy) and high-performance text pipelines (such as the Linebender organization'sparley,vello, andskrifa) so new frameworks don't reinvent rasterization.accesskit) are natively embedded by default into all modern Rust render pipelines.gpui-component) that can define application layout and states independently of the underlying GPU renderer (Hard task!!!)