Dwayne Cole
Jul 10, 2017 · 1 min read

Interesting… so where do you think this is heading? Can you point me to the current state of the art on this ( articles, repos, videos, etc).

I’m starting from scratch, meaning developing. Since I have the luxury, I only want to use redux for what’s necessary. My biggest nightmare is pulling in tones of redux boiler only to discover it to be unnecessary (typical state of js eco). It doesn’t help that I’m a mantra faithful (I followed your contributions intensely), which claims no need for redux, particularly in a meteor environment. So Apollo client handles remote state, and mantra claims no need for redux, I’m left wondering what areas of concern should i focus my redux attention. Unfortunately, the mantra community fizzled before offering a few redux concessions.

In any case, other than asking for referrals, can you please take a a few minutes to elaborate. That is from the top of your head, what are the 1 to 5 areas where redux is most favorable either by itself (e.g., ui concerns like toggles, drawers, navigation, token storage, device, and connectivity states) and a few areas where developers might need to write action creators to augment or support the apollo client?