I’ve been working on very large web applications for the past few years, starting from ground zero and, with a dozen other developers, making them scale up to now be used by millions of people. And sometimes, if you didn’t start with a good folder structure, it can become difficult to keep your code organized.
Nathanael Beisiegel wrote an interesting article where he explains his strategy in the organization of large React applications, but I still wasn’t completely satisfied by his approach. So I decided to spend some time to figure out what could be the best way to organize my future React projects.
Note: I use Redux files in all the examples of this article. If you don’t know what Redux is, you can have a look to the documentation here.
Note2: All examples are based on ReactJS, but you can use exactly the same structure for a React-Native application.
Edit April 2018: If you want to improve your codebase structure, you might also be interested in an article I’ve recently written about Why React developers should modularize their applications.
What are the challenges when you build an application?
This has happened or will happen to pretty much all developers over the course of their career:
- You build an application for a client with a team of a few developers, everything works very well all together.
- Your client requires new features, fine, you add them.
- Your client asks you to remove some features and add new ones, it starts to get complicated, you didn’t think about that, but you make it work even though it’s not perfect.
- Your client now wants you to change another feature, remove some others and add another one that wasn’t expected. At that point, you grab the scotch tape and start patching some code. You are not really proud of it but it works.
- 6 months later, after some other iterations, the code of the application gets really complicated to read and understand, everything looks like some Italian spaghetti pasta.
Until the day your client decides to create a new version of the application, with some fresh new code and features. In some cases, you end-up keeping complicated legacy code that lives with the new code, and this becomes even harder to maintain. And all of this happened because your app wasn’t properly designed from the beginning.
When I started to learn React, I found a few very good articles explaining how to create Todo lists or very simple games. Those articles were very useful to understand the basics of React, but I quickly got to a point where I wasn’t able to find much about how I could use React to build actual applications, something with a few dozens pages and hundreds of components. For Best web design company visit Vivid Designs
After some research, I learned that every React boilerplate project on Github results to similar structures, they organize all the files by type. This might look familiar to you:
/src /actions /notifications.js /components /Header /Footer /Notifications /index.js
/containers /Home /Login /Notifications /index.js
/reducers /login.js /notifications.js
/styles /app.scss /header.scss /home.scss /footer.scss /notifications.scss
This folder structure might be okay to build your website or application, but I believe that it is not the best folder structure.
When you organize your files by type, as your application grows, it often becomes difficult to maintain. By the time you realize this, it’s too late and you will have to invest a lot of time and money to change everything, or to support what you have for the next few years.
What could be a better approach to organize your application?
Pods in Ember are great but still limited, and I wanted something much more flexible. After a few experiments, trying to find what would be the best structure, I got to a point where I decided to group all related features together, and nest them as needed. This is what I use now:
/src /components /Button /Notifications /components /ButtonDismiss /images /locales /specs /index.js /styles.scss /index.js /styles.scss
/scenes /Home /components /ButtonLike /services /processData /index.js /styles.scss
/Sign /components /FormField /scenes /Login /Register /locales /specs /index.js /styles.scss
/services /api /geolocation /session /actions.js /index.js /reducer.js /users /actions.js /api.js /reducer.js
Each component, scene or service (a feature) has everything it needs to work on its own, such as its own styles, images, translations, set of actions as well as unit or integration tests. You can see a feature like an independent piece of code you will use in your app (a bit like node modules).
To work properly, they should follow these rules:
- A component can define nested components or services. It cannot use or define scenes.
- A scene can define nested components, scenes or services.
- A service can define nested services. It cannot use or define components or scenes.
- Nested features can only use from its parent.
Note: By parent feature, I mean a parent, grandparent, great-grandparent etc… You cannot use a feature that is a “cousin”, this is not allowed. You will need to move it to a parent to use it.
Let’s break this down.
You all already know what a component is, but one important thing in this organization is the ability to nest a component into another component.
Components defined at the root level of your project, in the components folder, are global and can be used anywhere in your application. But if you decide to define a new component inside another component (nesting), this new component can only be used its direct parent. Top web development company in Hyderabad check Vivid Designs
Why would you want to do that?
When you develop a large application, it happens quite often that you need to create a component that you definitively know you won’t reuse anywhere else, but you need it. If you add it at the root level of your components folder, it will get lost with hundreds of components. Sure, you could categorize them, but when it’s time to do some clean-up, you won’t remember what they are all for or if they are still being used somewhere.
Although, if you define at the root level only the main components of your application, such as buttons, form fields, thumbnails, but also more complicated one like listComments, formComposer with their own children components, it gets much easier to find what you need.
/src /components /Button /index.js
/Notifications /components /ButtonDismiss /index.js
/actions.js /index.js /reducer.js
- Button can be used anywhere in your application.
- Notifications can also be used anywhere. This component defines a component ButtonDismiss. You cannot use ButtonDismiss anywhere else than in the Notifications component.
- ButtonDismiss uses Button internally, this is authorized because Button is defined at the root level of components.
A scene is a page of your application. You can see a scene just like any component, but I like to separate them into their own folder.
If you use React-Router or React Native Router, you can import all your scenes in your main index.js file and setup your routes.
With the same principle components can be nested, you can also nest a scene into a scene, and also define components or services into a scene. You have to remember that if you decide to define something into a scene, you can only use it within the scene folder itself.
/src /scenes /Home /components /ButtonShare /index.js
/Sign /components /ButtonHelp /index.js
/scenes /Login /components /Form /index.js /ButtonFacebookLogin /index.js /index.js /Register /index.js
- Home has a component ButtonShare, it can only be used by the Home scene.
- Sign has a component ButtonHelp. This component can be used by Login or Register scenes, or by any components defined in those scenes.
- Form component uses ButtonHelp internally, this is authorized because ButtonHelp is defined by a parent.
- The Register scene cannot use any of the components defined in Login, but it can use the ButtonHelp.
Not everything can be a component, and you will need to create independent modules that can be used by your components or scenes.
You can see a service like a self-contained module where you will define the core business logic of your application. This can eventually be shared between several scenes or even applications, such as a web and native version of you app.
/src /services /api /services /handleError /index.js /index.js
/geolocation /session /actions.js /index.js /reducer.js
I recommend you to create services to manage all api requests. You can see them as a bridge/an adapter between the server API and the view layer (scenes and components) of your application. It can take care of network calls your app will make, get and post content, and transform payloads as needed before being sent or saved in the store of your app (such as Redux). The scenes and components will only dispatch actions, read the store and update themselves based on the new changes.
I’ve been working with this folder structure for the past few months on a personal project built with React-Native, and I can tell you this saved me a lot of time. It’s much more simpler to have all related entities grouped together, it makes things easier to work with.
I would recommend you to limit the number of nested folders to 3–4 levels. Normalizing your structure by limiting nesting will avoid complexity and help you maximize the reusability of your code.
Edit: I wrote another article explaining why your should modularize your application. This is one way to normalize your application structure.
Why React developers should modularize their applications?
This folder structure is one of many other ways to organize your project, that’s the way I like it now and I hope this will help you improve yours!
If you are interested to see working projects, I have a few on my Github account that follows this folder structure:
- https://github.com/alexmngn/react-rock-paper-scissors (ReactJS)
- https://github.com/alexmngn/react-native-authentication (React-Native)