This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can't go back!
If you aren't satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you're on your own.
You don't have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn't feel obligated to use this feature. However we understand that this tool wouldn't be useful if you couldn't customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify
🗃 Storage Strategy localStorage: Chosen for its simplicity and zero-backend setup — ideal for lightweight, client-only apps.
Key naming: "notes-app-data" keeps the app's data scoped and easy to manage in localStorage.
AddNote.jsx: Encapsulates controlled form inputs for title and content.
NotesList.jsx: Responsible for loading and displaying notes — promotes separation of concerns.
Components are colocated to encourage modularity and easy future scaling.
useState: Used for tracking input fields, view toggles, and refresh triggers.
Why I chose useState + this submit handler: simple form management and local UI updates.
useEffect: Loads notes once on component mount.
Why useEffect to sync storage → state: ensures we hydrate note data correctly from localStorage.
Tab-style buttons toggle between Add/View modes.
Why this nav approach for simplicity: avoids routing complexity for just two UI modes.
Tailwind CSS: Chosen for fast, utility-first styling.
• Tailwind for rapid utility styling: makes it easy to build responsive, clean UIs with minimal CSS overhead.
"Saving..." spinner appears during localStorage write.
Why show spinner here: communicates ongoing write to the user.
Error banner shows if saving fails (e.g. due to quota).
Why display error banner: gives user feedback when persistence fails.