Clean Reactive Architecture is a formalized and coherent architecture for reactive client applications - applications powered by React, Angular, Vue, Jetpack Compose, SwiftUI, or any framework based on the observer pattern.
Clean Reactive Architecture composes with what teams already use rather than replacing it.
-
Technical agility. The architecture supports technical agility - architectural units are small and independent, work splits along interfaces, and a change stays contained to the unit responsible for it. Agile process is only part of agile development - technical agility is the rest.
-
Shared understanding. The architecture and development methodology are formalized so that the system is understood in the same way by everyone. A developer joining a feature, a teammate picking up another person's work, or an AI agent given a task all share the same model and can implement it consistently.
-
Cross-platform portability. The architecture is the same across platforms, therefore porting is not redesigning the application but reimplementing units against the same diagram using platform-specific tools and libraries.
- Introduction - the gentle way in, for anyone who has built a component in a reactive framework.
- Architecture - the units, their responsibilities and dependencies, and the reasoning behind them.
- Development Methodology - how features are built.
The samples implement the same architecture with different frameworks and libraries. The units, the boundaries do not change - only the tools used to realize them.
- One-file React App - every architectural unit inlined in a single component in one single file. The easiest place to start.
- React App
- Angular App
- Vue App
- Next.js App - full-stack, covering both the client and the server.
- Flutter App
We are looking for maintainers to build and maintain samples of Clean Reactive Architecture for:
- Android — Kotlin / Jetpack Compose
- iOS — Swift / SwiftUI
- Vue.js
- Next.js / React — help maintain and improve the existing sample.
Maintainers help keep the samples idiomatic, aligned with the architecture, and up to date with their platforms. Contributions to documentation, tests, and code reviews are welcome too.
Interested? Open an issue and tell us which platform you would like to help with.
The architecture and development methodology are stable enough to use by application architects. An introduction for newcomers is available. Any related discussions, issues, and contributions are welcome.