lapce/floem

A native Rust UI library with fine-grained reactivity

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 45 minutes ago
Added to GitGenius on September 16th, 2026
Created on January 31st, 2023
Open Issues & Pull Requests: 100 (+0)
GitHub issues: Enabled
Number of forks: 218
Total Stargazers: 4,275 (+0)
Total Subscribers: 19 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 21.7 hours
Mean response time: 92.8 days
90th percentile: 418.3 days
Tracked items: 106

Most active contributors

Sign in to see contributor activity.

How this project is maintained

88% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 76% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 40
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 424 days
Stale 30+ days: 38
Stale 90+ days: 36

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • S: help wanted (2)
  • T: bug (2)
  • A: documentation (1)
  • P: macos (1)
  • T: enhancement (1)
  • T: question (1)
  • good first issue (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Floem is a native Rust UI library that builds graphical interfaces using fine-grained reactivity.

The library addresses the challenge of building performant, responsive user interfaces in Rust by implementing a reactive system where UI components automatically update only when their dependencies change. This approach avoids unnecessary re-renders and keeps the interface responsive even with complex state management. Floem uses a declarative syntax for defining UI layouts and behavior, allowing developers to express interfaces in a way that maps naturally to the underlying reactive model.

Floem suits developers building native desktop applications in Rust who want fine-grained control over rendering performance and state updates. It works well for projects where UI responsiveness matters and where the overhead of full-tree re-renders would be problematic. The library is appropriate for teams comfortable with Rust's ecosystem and willing to adopt its reactive programming model rather than seeking a more traditional imperative UI framework.

The project shows active development with regular commits addressing both new features and maintenance. Work spans across core reactivity improvements, widget implementations, and documentation. The codebase receives consistent attention to both expanding capabilities and refining the existing architecture based on practical usage patterns.