Redux so good technology.

dynamic content - redux

basic static simple app - no redux

Short answer: You might not need Redux but you should understand the concepts.

Long answer: Consider you are building an application and you want other developers to understand the logic without your help. Also, as you application becomes bigger, maintaining the states will becomes a nightmare as setting the state gets out of hands very quickly. You maintain internal states inside the components and then send those states as props to other components which needs those.

Now, after a good one year, you come back to your application to fix some issues. At this point, chances are you won't even remember the code and it becomes very difficult to understand which state is modifying a certain prop (to another component) which caused the bug. Have a predictable state container like Redux will help you in this aspect. It will becomes very much clear to you which component is modifying which thing as you can use the time-travel debugger among other stuffs.

Hope this helps!

a) If you are building a simple react app, and

b) if you are introducing lot of methods that get passed down the hierarchy chain, and

c) you are having to mutate the state of elements outside the scope of the current component,

then you will naturally end up choosing Redux. It is much simpler to publish events whenever you want to mutate objects and handle them as a reaction to the events. The challenge is the number of paradigms and patters both flux and redux introduces. It is painful at the moment (though in the next several months, I hope the boilerplate is highly reduced) to learn, but it is well worth it.

It is! It may take a little time to setup when you're doing it for the first time, but it's definitely worth it. It may seem like you're doing too much for a simple task, but as your project gets bigger, using redux really saves your life.

Short answer: absolutely.