Honestly I usually find it pretty difficult to be able to plan out exactly what components I'm going to need until I'm in the middle of trying to implement the UI. That's probably mostly because of a lack of upfront requirements most of the time haha.
But I usually end up starting with a container redux connected component. Then as I start filling up the render with lots of UI, I start refactoring that UI out into smaller dumb components.
This feels like a pretty natural progression for me, since you usually need to orchestrate a bunch of stuff from redux first. Then as you start flushing out all the interactions needed and start to see the pieces of UI that are good "dumb" component candidates you can just pop them out into stateless functions and put them in separate files. You're usually able to already know what props these dumb components need as well.
I'm curious if others end up following this same approach?
Thanks for your input! And I totally agree! I progress in a similar way when building an application. But of course it heavily depends on the application and it's UX you want to build :)
Definitely same. I'd love to be able to implement this strategy at a much earlier stage, but unfortunately my boss isn't too familiar with react thinking so as time progresses move to this structure but initially nope... well at least a work.
Honestly I usually find it pretty difficult to be able to plan out exactly what components I'm going to need until I'm in the middle of trying to implement the UI. That's probably mostly because of a lack of upfront requirements most of the time haha.
But I usually end up starting with a container redux connected component. Then as I start filling up the render with lots of UI, I start refactoring that UI out into smaller dumb components.
This feels like a pretty natural progression for me, since you usually need to orchestrate a bunch of stuff from redux first. Then as you start flushing out all the interactions needed and start to see the pieces of UI that are good "dumb" component candidates you can just pop them out into stateless functions and put them in separate files. You're usually able to already know what props these dumb components need as well.
I'm curious if others end up following this same approach?