2024-10-17
3609
#react#redux
Neo Ighodaro
315
Oct 17, 2024 ⋅ 12 min read

Understanding Redux: A tutorial with examples

Neo Ighodaro Neo Ighodaro is a twenty-something-year-old fullstack web developer and graphic designer not based in Lagos, Nigeria.

Recent posts:

the replay oct 15 graphic

The Replay (10/15/25): AI’s accessibility problem, React 19.2, and more

Discover what’s new in The Replay, LogRocket’s newsletter for dev and engineering leaders, in the October 15th issue.

Matt MacCormack
Oct 15, 2025 ⋅ 34 sec read
AI has an accessibility problem: What devs can do about it

AI has an accessibility problem: What devs can do about it

Jemima Abu examines where AI falls short on accessibility and how we can best harness AI while still building products that everyone can use.

Jemima Abu
Oct 15, 2025 ⋅ 10 min read

Want to run your AI model locally? Here’s what you should know

Cloud AI made scaling easy, but local AI brings control, cost stability, and data privacy. Explore the hardware realities, tradeoffs, and strategies shaping this shift.

Clara Ekekenta
Oct 15, 2025 ⋅ 6 min read

Stop writing REST APIs from scratch in 2025

Writing REST APIs by hand is a thing of the past. Frameworks like tRPC, Fastify, and Hono eliminate boilerplate with schema-driven design, improving speed and safety.

Ikeh Akinyemi
Oct 14, 2025 ⋅ 3 min read
View all posts

25 Replies to "Understanding Redux: A tutorial with examples"

  1. @nighodaro, loved the article, thank you. Though, I’m having a hard time understanding why do we take in the last code snippet – usename for Status?
    ““

  2. Hi, Thanks for your article. Do you think it could be possible and enough to just use a React Context do avoid the props drilling problem ?

  3. What an amazing and helpful explanation! I’ve read several articles but this one was the most clear one! It helps me understand the concepts of Redux

  4. Great article. Never imagined I would learn it so much easily. Highly recommended for everyone, who wishes to know about Redux. Thanks a ton.

  5. @author

    I want to quote the below lines-
    “If the data needs to be passed from a parent to a child deep down the tree, this can still be accomplished using React utilities like Context. But when it comes to sharing the state between components on the same level, Redux is the inevitable option.”

    Read below line
    >>> But when it comes to sharing the state between components on the same level, Redux is the inevitable option.
    >>> My thoughts, even if the components on the same level we can go with Context API, why Redux is the inevitable option here, Please clear my doubt.

Leave a Reply