You don't architecture you project around React - you simply fit react in wherever you want to render the UI. React has a very small API, most of which are simple lifecycle methods for dealing with changes in the state of a component [1].

You tell React that you'd like to Render component X inside DOM element Y, and that's really all React does. There's no architecturing your project around React.

[1] https://facebook.github.io/react/docs/react-component.html

Even though, the number of React's API is still larger than [Binding.scala's API](https://static.javadoc.io/com.thoughtworks.binding/binding_2...).

The architecture of any web application will be affected by your view layer, whether it is react, custom built, or any thing else.

Yes, if use react, you need an architecture compatible with the reactive paradigm.

You will want an application architecture if you're writing a complex project with any view library. React isn't special in this regard.

Agreed. It's only special because some people want to call it a library instead of a framework.

That's because it _is_ a library. If you compare it to something like Ember, it's pretty obvious that's what it is.