It would be counter-intuitive if I endorse a Recoil-based solution on this thread that talks about a different library, LOL. But since I want to help as much a

It would be counter-intuitive if I endorse a Recoil-based solution on this thread that talks about a different library, LOL. But since I want to help as much as I can, my advice is, regardless of which library you choose, or which approach (atomic vs. monolithic/structured)... start with analyzing which parts of the state in your app really are supposed to be "shared" state. I have a feeling you may be trying to use "shared" state libraries to manage state that only the individual components would actually need. Do those dynamic components actually need to share data? The answer to that is the first important consideration, IMHO, before you can go forward. Good luck.