Epic Web Conf regular tickets are available now!

Prices go up soon

Join the community and network with other great web devs.

Time's up. The sale is over
Illustration of a microphone

Calls with Kent C. Dodds.

You call, I'll answer.

Listen to the podcasts here
Phone sitting on a stool

What's this all about?

The goal of the Call Kent Podcast is to get my answers to your questions. You record your brief question (120 seconds or less) right from your browser. Then I listen to it later and give my response, and through the magic of technology (ffmpeg), our question and answer are stitched together and published to the podcast feed.

I look forward to hearing from you!

Record your call

Calls with Kent C. Dodds Season 2 — 50 episodes

10.State bloating vs api call (again and again)
06:40
Keywords

React, redux, state-management

Description
When a user enters the tab (btw it's a SPA) I call the api in useEffect and saving the response in redux store. May I know is it better approach to call the api again and again when the user leaves and enters the page? (In this case I see a flicker of loading every time) or storing the response in redux store (UX for this screen is good but is it harming the performance overall?) or storing the response in component state? (Is there any difference b/w this and above approach performance wise?)
Thanks again for this opportunity & Regards Rahimuddin
10.State bloating vs api call (again and again)
06:40
Keywords

React, redux, state-management

Description
When a user enters the tab (btw it's a SPA) I call the api in useEffect and saving the response in redux store. May I know is it better approach to call the api again and again when the user leaves and enters the page? (In this case I see a flicker of loading every time) or storing the response in redux store (UX for this screen is good but is it harming the performance overall?) or storing the response in component state? (Is there any difference b/w this and above approach performance wise?)
Thanks again for this opportunity & Regards Rahimuddin
10.State bloating vs api call (again and again)
06:40
Keywords

React, redux, state-management

Description
When a user enters the tab (btw it's a SPA) I call the api in useEffect and saving the response in redux store. May I know is it better approach to call the api again and again when the user leaves and enters the page? (In this case I see a flicker of loading every time) or storing the response in redux store (UX for this screen is good but is it harming the performance overall?) or storing the response in component state? (Is there any difference b/w this and above approach performance wise?)
Thanks again for this opportunity & Regards Rahimuddin
10.State bloating vs api call (again and again)
06:40
Keywords

React, redux, state-management

Description
When a user enters the tab (btw it's a SPA) I call the api in useEffect and saving the response in redux store. May I know is it better approach to call the api again and again when the user leaves and enters the page? (In this case I see a flicker of loading every time) or storing the response in redux store (UX for this screen is good but is it harming the performance overall?) or storing the response in component state? (Is there any difference b/w this and above approach performance wise?)
Thanks again for this opportunity & Regards Rahimuddin

Looking for more content?

Have a look at these articles.

See the full blog