Loading video...

Video Failed to Load

Go Home

โš›๏ธ React project structure for mid-sized applications โ†“ ๐ŸŒถ๏ธ opinionated

85,221 views โ€ข 1 year ago โ€ขvia X (Twitter)

10 Comments

George Moller's profile picture
George Moller1 year ago

I've been working professionally with React for more than 8 years and I compiled all my knowledge into 100+ infographics and 70+ video tutorials just like this one. Check them out โ†“

tottzi's profile picture
tottzi1 year ago

Whatโ€™s your suggestion for a large sized app? And whatโ€™s your opinion about the atomic structure?

Ifeora Okechukwu Patrick's profile picture
Ifeora Okechukwu Patrick1 year ago

I would rather change the 'utils' ๐Ÿ“ to a different name like 'common' ๐Ÿ“‚

Camilo Vargas's profile picture
Camilo Vargas1 year ago

The animations in these videos are fantastic! ๐Ÿค— This structure for React projects is solid. Iโ€™m not usually a front-end developer, but when I need to tackle "full-stack" tasks, I tend to use something similar

George Moller's profile picture
George Moller1 year ago

Are gou mostly a backend developer? Whatโ€™s your stack?

dino's profile picture
dino1 year ago

Screaming Architecture?

Pavel Romanov's profile picture
Pavel Romanov1 year ago

That's a good structure for mid-size apps. Been working with a similar one for quite some time. The only thing different for me is the name of shared components. The fold called just "shared"

George Moller's profile picture
George Moller1 year ago

I like that too! Pretty explicit and self explanatory ๐Ÿ‘Œ

Atif Riaz's profile picture
Atif Riaz1 year ago

That's amazing

Don "God Abeg" Billiono's profile picture
Don "God Abeg" Billiono1 year ago

After 14yrs doing Php, Angular, React, C# across multiple production grade projects, I have never seen a structure like this, so I would respectfully disagree.

Related Videos