Feedback

[artalar]

Leave a comment here about your positive experience with Reatom. It could be added to the landing page.

[Aetet]

Used it for a small internal project.
The approach felt unusual after working with Redux and MobX, but I decided to give it a chance.

Using actions instead of reducers cuts out a lot of boilerplate.
Computed atoms replace selectors nicely.

I really like the auto type inference—it’s a huge help during refactoring. Instead of manually writing types in dozens of places, you just update the source type. Feels like magic, honestly.

The async library is also really powerful and supports runtime composition. It's one of the best tools for building complex UIs with dynamic content.

My advice for new adopters: spend 2–3 days exploring the library and getting a feel for the philosophy of atomization.

Huge kudos to the Reatom team!

[kasperskei]

Reatom has been my primary tool for over a year now.
It provides a unique experience that I was missing in other libraries. Its flexible reactive primitives allow for concise, readable, and maintainable code, while offering maximum control with minimal effort.

Built-in transactions make working with complex asynchronous flows significantly easier, making Reatom a perfect fit for interacting with external APIs.

The integration with @reatom/jsx works exceptionally well for Telegram Mini Apps, browser extensions, and embedded widgets. It is a lightweight and fast alternative to heavyweight frameworks - free from unnecessary dependencies but fully powered by reactivity.

And I have to highlight the community it is a true gem of Reatom. Thanks to the people behind it, I have always received quick and helpful support, no matter how complex the issue. The community support remains top-notch. ❤️

[AgarkovRoman]

Reatom is 🫶🏻
I've been really enjoying using Reatom in my projects. Here are some things I love about it:

1. Framework-agnostic
   One of the biggest strengths of Reatom is that it's not tied to any specific UI framework. This makes it easy to keep logic outside components, resulting in simpler components and more testable overall code.

2. Elegant solutions for complex scenarios
   Some features that are quite tricky to implement with other libraries are surprisingly easy with Reatom. For example, periodic refresh can be implemented in just a few lines - incredibly powerful.

3. Great ecosystem
   The Reatom ecosystem is mature and provides tools for common use cases:
   @reatom/timer
   @reatom/persist-web-storage
   and many other helpful utilities

4. Testability
   Since atoms and effects are decoupled from the view layer, it's very straightforward to test logic without rendering components — a huge plus for maintainability.

Big thanks to the Reatom team!

[y0na24]

Reatom is my favorite state-manager right now with no discussion.

I can solve common tasks with simple primitives (atom, computed, effect), but when my app get complex it's very easy to extend the functionality with extension system.

Reatom is very flexible and you can decide yourself how to use it powers.

I love the Zen of Reatom, especially "Explicit specifics, implicit generics".

Reatom solves 90% of commons frontend tasks himself, but when you need something special, you need to use it primitives and extension system, which gives you the control of your code.

Reatom doesn't add accidental complexity to your app, it gives you the API, which solves complex problems in linear way.