
Short answer
Most React tutorials end with a working demo and no idea why it works. The fix is to choose projects by the concept they force you to learn. Every idea below says which concepts it teaches, what to build first, what data it needs, and the mistake that catches most people.
Don't reach for Create React App. The React team deprecated it for new apps in February 2025. The official React docs now recommend starting with a framework: Next.js (App Router), React Router (v7) or, for native mobile apps, Expo. If you'd rather learn the basics without a framework, the docs also cover starting from a build tool such as Vite, Parcel or RSbuild.
For the beginner projects here, a Vite single-page app is plenty. React's docs note that a build tool gives you a client-only app with no built-in routing or data fetching, which is exactly what makes these small projects good practice: you add each piece yourself.
npm create vite@latest my-app -- --template react-ts
| Idea | Who it is for | React concepts | Core features | Difficulty |
|---|---|---|---|---|
| Bill and tip splitter | First-week learners | useState, derived values | Amount, tip, people, per-person total | Easy |
| Habit tracker | Beginners | Lists and keys, effects for localStorage | Add habits, tick days, streaks | Easy |
| Weather card | Beginners ready for APIs | Data fetching, loading and error states | City search, current weather, 5-day view | Easy |
| Quiz game | Beginners | Conditional rendering, useReducer | Questions, score, timer, results | Easy to medium |
| GitHub profile explorer | Intermediate learners | Fetching chained requests, custom hooks | User search, repos list, sorting | Medium |
| Kanban board | Intermediate learners | useReducer, context | Columns, cards, move, persist | Medium |
| Recipe box with routes | Intermediate learners | Routing, URL params, lifting state | List, detail page, search, favorites | Medium |
| Multi-step signup form | Intermediate learners | Form actions, useActionState | Steps, validation, pending state | Medium |
| Notes app with optimistic saves | Advanced learners | useOptimistic, Actions | Create, edit, instant UI, rollback on error | Hard |
| Personal dashboard on Next.js | Advanced learners | Server and client components | Widgets fed by server data, auth | Hard |
| Photo gallery with lazy-loaded views | Advanced learners | lazy, Suspense, memo | Grid, lightbox, editor view loaded on demand | Hard |
| Mobile flashcards with Expo | Web devs trying native | React Native components, navigation | Decks, review mode, spaced repeats | Hard |
Three inputs and one answer. Build the form first, then the per-person total. Data: none. Watch out for: storing the total in state. React's docs are direct on this: when something can be calculated from existing props or state, calculate it during rendering instead. Round money in integer cents, or $10 split three ways will show a cent that belongs to nobody.
A list of habits with a checkbox for each day of the week. Build add and tick first, streaks second. Data: habits with id, name and an array of completed dates, saved to localStorage. Watch out for: using the array index as the key. Delete a habit and the checkboxes jump to the wrong row. Use a stable id.
A city search that shows current conditions and a short forecast. Open-Meteo needs no API key; its free tier is for non-commercial use and is limited to 10,000 calls a day. Build the three screen states (loading, error, result) before any styling. Watch out for: race conditions. Type fast and an older response can land after a newer one. React's docs fix this with a cleanup function that ignores stale responses.
Build this with a prompt on Greta.sh — describe the app, Greta writes and deploys it.Ten questions, a score and a results screen. Data: a JSON file of questions, each with options and the correct index. Start with the question flow; add a timer last. Watch out for: five separate useState calls that must change together. Once "next question" updates the index, score and timer at once, move the logic into useReducer.
Search a username, show the profile, then the public repos with sorting by stars or last update. Pull the fetch logic into a custom hook once you write it twice. Data: GitHub's REST API. GitHub's docs set the unauthenticated limit at 60 requests per hour, so cache results and show a clear message when the limit hits. Never put a personal token in front-end code.
Three columns and cards you can move. Build add, edit and move with buttons first; drag and drop is a layer on top. Data: cards with id, title, column and createdAt. Watch out for: prop drilling. Context lets a parent component provide data to the entire tree below it, so put the reducer's dispatch there rather than passing it through four levels.
A list page, a detail page per recipe and a favorites page, each with its own URL. React Router fits well; the React docs describe it as the most popular routing library for React. Data: a local JSON file of recipes. Watch out for: keeping the search term only in component state. Put it in the URL so a refresh or a shared link keeps the results.
Three steps, validation and a pending state on submit. This is the place to learn useActionState, which returns the state, an action to dispatch and an isPending flag. Data: none until you connect a backend. Watch out for: cleared fields. React resets uncontrolled fields after a form action succeeds, so decide which values must survive a validation error and keep them on purpose.
Notes appear the moment you press save, before the server answers. useOptimistic exists for this: it lets you update the UI optimistically while the real request runs. Data: a notes table in any hosted database or a small API. Watch out for: failure. Decide what the user sees when the save fails, and test it by turning the network off.
Widgets for tasks, calendar and a reading list, with data loaded on the server. React's docs note that the Next.js App Router implements React Server Components, so a server-only component can be an async function that reads from a database and passes data to interactive components. Data: a database plus sign-in. Watch out for: marking everything as a client component out of habit, which throws away the point of the exercise.
Want to try one of these? Start on Greta.sh — no setup, no boilerplate — just a prompt.A grid of photos, a lightbox and a heavier editor view. Load the editor with lazy, which defers loading a component's code until it first renders, and wrap it in Suspense with a fallback. Data: your own images or any photo API whose terms allow it. Watch out for: reaching for memo before measuring. Profile first with React Developer Tools, then fix what is slow.
Decks, a review mode and cards that come back sooner when you get them wrong. React's docs describe Expo as a framework for universal Android, iOS and web apps with native UIs, free to build with, with optional paid cloud services. Data: decks stored on the device. Watch out for: web habits. There is no div or CSS file here, so expect a day of learning the native components.
Want a head start? Paste one of these into an AI coding assistant or app builder, read the code it writes, then rebuild the part you didn't understand by hand. For more build ideas outside React, see our web app ideas and AI project ideas.
Gets the fetch, loading and error states right in the first version, which is the part most tutorials skip.
Build a React app with Vite and TypeScript that shows the weather for a city. Input: a city name. Use the Open-Meteo geocoding endpoint to turn it into coordinates, then the forecast endpoint for current temperature, wind and a 5-day forecast. No API key. Show three states clearly: loading, error (with a retry button) and the result. Fetch inside useEffect with a cleanup flag so a slow response for an old search never overwrites a newer one. Keep the last 5 searched cities in localStorage and show them as quick buttons.
Sets up the reducer and the saved state on day one, so drag and drop is an add-on rather than a rewrite.
Build a Kanban board in React with three columns: To do, Doing, Done. Manage all cards with useReducer. Actions: add card, edit title, move to column, delete. Each card has id, title, column and createdAt. Save the state to localStorage on every change and load it on start. Put the dispatch function in a context so any card can move itself without passing props through every level. Add drag and drop between columns last, after buttons for moving cards already work.
Uses React's form actions instead of an onSubmit handler, which is how the current docs show forms.
Build a 3-step signup form in React 19: account (email, password), profile (name, role from a list), and confirm. Use a form with an action and useActionState for each step's submit, and show the isPending state on the button. Validate on submit: email format, password at least [12] characters, required fields. Show each error next to its field and keep what the user typed when validation fails. Allow back and forward between steps without losing data. Fake the final save with a 1-second delay.
If you'd rather pick from projects that aren't tied to one framework, our vibe coding projects and AI app projects for your portfolio are good next stops.
What is a good first React project?
A bill splitter or a habit tracker. Both fit in one or two components, need no server, and teach the basics that every later project uses: useState, rendering lists with keys, and calculating values during render instead of storing them.
Should I still use Create React App?
No. The React team deprecated Create React App for new apps in February 2025. React's docs now point to a framework such as Next.js or React Router, or to a build tool such as Vite, Parcel or RSbuild if you want to start from scratch.
Which React projects teach data fetching?
The weather card and the GitHub profile explorer. Both call a public API, so you have to handle loading, errors and responses that arrive out of order. React's docs show a cleanup flag that ignores stale responses for exactly that race condition.
Do I need a backend for these React projects?
Not for the beginner and most intermediate ideas: they use browser storage or public APIs. The advanced ideas need a server or a database, which is where a framework with server rendering or a hosted backend comes in.
What React projects look good in a portfolio?
Ones that show more than a tutorial does: the multi-step form with real validation, the Kanban board with a reducer and saved state, or the Next.js dashboard. Ship it live, write a short README on the trade-offs, and keep the commit history honest.
© 2026 Questera
Follow in Google