Congratulations 🎉
Woohoo, React has been conquered! You are officially a React guru. Take a moment to appreciate what you’ve learned throughout this course and give yourself a round of applause. With React under your tool belt, you are well-equipped to tackle complex projects confidently.
However, your React learning (or learning in general) doesn’t stop here. As proponents of a growth mindset, we believe there’s so much more to explore and learn.
What’s next
Frontend is the land of innovation, and React is one of the leaders in the space. You can keep up with the future of React by following the React RFC GitHub repository. This is where new features and changes to React are proposed, discussed, and eventually accepted or rejected. One of the groundbreaking RFCs is Server Components. Over this course, we’ve rendered our React components in the client, but here this RFC discusses how we can bring React to the server and render it there. This feature has huge potential and is worth keeping an eye on in the future.
Furthermore, you can dive into React meta frameworks. They’re a framework for React that add first-class support for functionalities like data fetching and routing. Additionally, they leverage React’s latest features to provide the best experience possible for developers and users alike. Some examples of these are Next and Remix.
You’re at a point in your React journey where you can begin learning about design patterns and architecture. patterns.dev is an exceptional resource that will help you build better React apps by leveraging powerful patterns. They are worth a bookmark!
Before you move onto the next section. Fill out this React course feedback survey to add your input and experience with the section. This helps us improve the section as well as the overall course and is greatly appreciated.
Using a backend
As you’ve seen, you can get your apps to do a lot of pretty cool things already, just using client-side JavaScript. You may have noticed, though, that there is still an important piece of the puzzle missing: unless you use Local Storage, your app ‘forgets’ the user’s preferences, as well as any other changes made, as soon as the page gets reloaded.
While Local Storage is great, it’s not ideal: it only stores data on the computer from which the user is accessing the page. This approach does not allow for the app to ‘remember’ anything when the same user tries to access it again from a different device. For that, you’re going to need a real backend, which you’ll learn all about next in our NodeJS course. With Node, we’ll be able to add a bunch of cool features to your apps like user authentication, data persistence, and more.
Contribute
The Odin Project wouldn’t exist if not for contributors sharing their precious time and resources. We’d love to hear your ideas and suggestions to improve the React course. You can share your thoughts over on our Discord or better yet, open an issue on the The Odin Project’s curriculum repository.
Good luck and happy learning!