As you grow your knowledge in React.js, you will notice that there are many sources with simple code examples but only a few of advanced stuff. And many of them have "outdated code" (no hooks, class components everywhere, etc).

What if you want to know how to structure a medium to large codebase? Or if you want to know if you are doing everything fine?

One way to improve your skills is to study what other devs are doing. How they approach their projects can teach you lessons that maybe will take you weeks to learn.

That's why I made this list of open-source React.js applications you can learn from. All uses modern features such hooks, context and many uses redux-toolkit. So, no matter if you already have hit a plateau as seasoned developer or if you're just starting, take a look!

1) Take Note – Live

📝 A free, open source notes app for the web. Contribute to taniarascia/takenote development by creating an account on GitHub.

Take Note is an open-source project to take notes, known as "The Note Taking App for Developers"

It's a simple plain-text take note app with markdown support. Without all the fancy stuff that we don't need :)

The code seems to be good organized:

React app code structure

It uses React hooks (yay!) and redux-toolkit =) (see the slices folder).

auth.ts, authentication slice using redux toolkit

2) Cloud Music

React 16.8打造精美音乐WebApp. Contribute to sanyuan0704/react-cloud-music development by creating an account on GitHub.

This is a clone of NetEase, a cloud music streaming service. The README is in Chinese but the code is in plain English.


This project uses redux (without redux-toolkit) and hooks. What I find interesting in this project is the code structure:

react-cloud music code structure

At first, it seems pretty standard but after reviewing the reducer (store/reducer.js) I noticed that they are "grouping" (inside application folder) some components and styles alongside the redux logic:

3) Todoist clone

Subscribe to my YouTube channel: - Building Todoist Using React - karlhadwen/todoist

Karl Hadwen did this Todoist clone, and he even has a video tutorial on Youtube.

Screenshot from

For the "backend", he used Firebase instead of building an API from scratch. He used context and didn't use redux (yes, you don't always need to use redux).

4) Mortgage – Live

Mortgage overpayment calculator using React with Hooks and D3 - paulhoughton/mortgage

Mortgage is a mortgage overpayment calculator!

Screenshot from Live website

It uses D3 to draw the chart and hooks! It is a small app but it is a good start to learn how to use hooks in calculator-like applications.

5) Tomato Work – Live

🍅 tomato-work for React 个人事务管理系统. Contribute to xjh22222228/tomato-work development by creating an account on GitHub.
130+ ⭐

Tomato-work is a personal affairs management system written in React using hooks and redux:

Live demo from READMe

For the UI, it uses Antd, which is pretty awesome btw. The code structure is standard:

Code structure

What I find interesting is that it has a services folder (remind me of angular) where each file is an abstraction to make API calls. So instead of calling axios directly in the component, he uses a service function instead.

6) Write with me – Live

Real-time Collaborative Markdown Editor . Contribute to dabit3/write-with-me development by creating an account on GitHub.

Write with me is  a real-time collaborative markdown editor written in React with hooks and it uses AWS Amplify

As you can see, this is a small project:

Code structure

So, the code structure is not organized using different folders. All the state management is done using useReducer hooks.

There is a graphql folder because Amplify works with graphql

7) JIRA Clone – Live

A simplified Jira clone built with React/Babel (Client), and Node/TypeScript (API). Auto formatted with Prettier, tested with Cypress. - oldboyxx/jira_clone

This is a simplified JIRA Clone which looks awesome!

Screenshot from the live website

Analyzing the code structure, you can see it uses cypress and jest for testing:

Code structure

As the author says, it is a good example of a modern real-world React codebase. There are the features (from README):

The project features from README

8) Spectrum – Live

Simple, powerful online communities. Contribute to withspectrum/spectrum development by creating an account on GitHub.
Tags: react, graphql, expo, styled-components, nodejs

Spectrum is a platform that allows you to create and participate in awesome communities.

I have seen many people recommending this repository. And there is a good reason for this: the repository is their entire product!

That being said, this codebase isn't your typical open source project because it's not a library or package with a limited scope—it's our entire product.

In my opinion, this is one of the best open source full-stack react projects that shows off how to properly structure a large codebase

Spectrum folder structure: Full-stack JavaScript in action

The frontend SPA (react) lives in src folder

SPA frontend folder structure

As you can infer from the folder structure, they split the code by "type" of code (components, reducers, hooks, etc).

9) GitHub profile README Generator – Live | Repo

This tool provides an easy way to create GitHub profile README with the latest add-ons like visitors count, GitHub stats etc.

Demo (extracted from the README)

This is an example of a Gatsby project that uses hooks. The files are organized by type which is fine for the size of the project:

File Organization

If you haven't created your GitHub profile, maybe you can now by using this tool (I did!)

What to do Next

Questions like "what is the best state management tool" or "what is the best way to organize your code" does not have one size fits all answer.

As you have seen in this post, different projects choose different organization and tools. The problem with it is when we start we don't have a good guidance of what to do, which lead us to overthinking and analysis paralysis.

That's why I created a FREE e-book 🎁 with good practices about:

  1. Code styling and quality.
  2. Organizing your project files.
  3. How to manage your state.