Why is MVVM considered a reactive approach?

MVVM is considered reactive because in it, the View and the ViewModel automatically react to each other's changes through the data binding mechanism and observable properties.

The ViewModel stores data as observable objects. When a value changes, the View updates immediately without manual code. If the user changes something in the interface, the new value is automatically passed back to the ViewModel.

This behavior makes the application reactive: the interface does not wait for update commands but reacts by itself to the state of the data. This removes the imperative "update the screen" code, reduces the number of bugs, and simplifies the logic of synchronizing state with the UI.