reactiveui/reactiveui

An advanced, composable, functional reactive model-view-viewmodel framework for all .NET platforms that is inspired by functional reactive programming....

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 58 minutes ago
Added to GitGenius on September 7th, 2026
Created on June 11th, 2010
Open Issues & Pull Requests: 5 (+0)
GitHub issues: Enabled
Number of forks: 1,150
Total Stargazers: 8,536 (+0)
Total Subscribers: 341 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 2
Closed in 7 days: 1
Avg open age: 311 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

  • bug (106)
  • feature request (33)
  • future (11)
  • Backer Requested (9)
  • reactiveui-core (4)
  • Hacktoberfest (3)
  • blazor (3)
  • consumer-experience (3)

Detailed Description

ReactiveUI is a composable, cross-platform model-view-viewmodel framework for .NET platforms that applies functional reactive programming principles to abstract mutable state from user interfaces.

The framework addresses the challenge of managing complex application state and UI synchronization by enabling developers to express feature logic in a single, readable location using reactive patterns. It leverages functional reactive programming to decouple state management from presentation, making applications easier to reason about and test. The approach centers on composable reactive streams that automatically propagate state changes through the UI layer.

Developers should adopt ReactiveUI when building applications that benefit from declarative, testable state management across multiple .NET platforms. The framework suits projects targeting WPF, WinForms, WinUI, MAUI, Xamarin, Avalonia, Blazor, Android, iOS, and other .NET platforms. It includes platform-specific packages for each target, along with dedicated testing utilities and validation extensions. The framework ships in two interchangeable distributions built on the same core engine, differing only in which reactive interop types appear in the public API, allowing developers to choose based on their dependency preferences without rewriting code.

The project maintains active engagement with its community through documentation, sample applications, and discussion channels. Development activity shows consistent attention to cross-platform support, with platform-specific packages regularly maintained alongside the core framework. The codebase includes source generators for code generation tasks and dedicated testing packages, indicating ongoing investment in developer experience and tooling. Documentation covers scheduler usage and integration patterns, reflecting practical focus on real-world adoption challenges.