Build with AI: Create a Follow-Up App with React, Supabase, and Cursor

This is the repository for the LinkedIn Learning course Build with AI: Create a Follow-Up App with React, Supabase, and Cursor. The full course is available from LinkedIn Learning.

Course Description

Learn how to build a follow-up application using React, Supabase, and the Cursor AI coding assistant. Developer advocate Ayodele Aransiola begins by modeling a multi-role schema in Supabase and enforcing row-level security policies for users, sub-admins, and super-admins. Next, Ayodele demonstrates how to leverage AI suggestions in Cursor to create and refine React components. Then, discover how to implement a GDPR-style, multi-step form that captures user consent and writes immutable, hashed audit logs. Finally, discover how to deploy your app to production. Upon finishing this course, you’ll have a production-ready application that balances developer productivity with data privacy and compliance.

See the readme file in the main branch for updated instructions and information.

Instructions

This repository has branches for each of the videos in the course. You can use the branch pop up menu in github to switch to a specific branch and take a look at the course at that stage, or you can add /tree/BRANCH_NAME to the URL to go to the branch you want to access.

Branches

The branches are structured to correspond to the videos in the course. The naming convention is CHAPTER#_MOVIE#. As an example, the branch named 02_03 corresponds to the second chapter and the third video in that chapter. Some branches will have a beginning and an end state. These are marked with the letters b for "beginning" and e for "end". The b branch contains the code as it is at the beginning of the movie. The e branch contains the code as it is at the end of the movie. The main branch holds the final state of the code when in the course.

When switching from one exercise files branch to the next after making changes to the files, you may get a message like this:

error: Your local changes to the following files would be overwritten by checkout:        [files]
Please commit your changes or stash them before you switch branches.
Aborting

To resolve this issue:

Add changes to git using this command: git add .
Commit changes using this command: git commit -m "some message"

Instructor

Ayodele Aransiola

Software Engineer