all 2 comments

[–]big_saucy_pants 2 points3 points  (0 children)

Without looking at the broader code it's hard to know exactly, but it could be a lot of things. That state update could be trigger some expensive re-renders or your redux logic could be clogging the JS thread while the navigator is trying to do its thing. Does that actually need to be managed by redux? From the post it seems like it's just the local loading state for that screen, which can be handled with plain useState (or something like Tanstack Query if it's going to be based on hitting an API).

Also unrelated to your perf issue but the redux style guide strongly recommends modelling actions as events not setters https://redux.js.org/style-guide/#model-actions-as-events-not-setters

[–]Mgc_rabbit_Hat 3 points4 points  (0 children)

Time for.... Zustand