Is your feature request related to a problem? Please describe.
Currently, the Expense Tracker stores all expense data in the browser’s localStorage. This creates several limitations:
Data is lost if browser cache is cleared
Data is not accessible across multiple devices
No centralized storage
The application remains purely client-side
This limits the project’s scalability and real-world usability.
Describe the solution you'd like
I would like to implement a basic backend system to enable persistent expense storage.
The backend should:
Set up a simple server (Node.js + Express)
Connect to a database (MongoDB / SQLite)
Provide REST API endpoints:
POST /expenses → Add new expense
GET /expenses → Fetch all expenses
DELETE /expenses/:id → Delete an expense
Replace localStorage usage with API calls
Ensure frontend communicates with backend using fetch()
This will convert the project from a frontend-only application into a basic full-stack application.
Describe alternatives you've considered
An alternative approach would be continuing to use localStorage for simplicity. However, this does not provide persistent or scalable storage and limits future enhancements like authentication or multi-device support.
Additional context
This enhancement will:
Improve project architecture
Introduce backend integration
Make the project closer to real-world applications
Provide a foundation for future upgrades such as authentication and user-specific data
I would like to work on this issue if assigned.
Is your feature request related to a problem? Please describe.
Currently, the Expense Tracker stores all expense data in the browser’s localStorage. This creates several limitations:
Data is lost if browser cache is cleared
Data is not accessible across multiple devices
No centralized storage
The application remains purely client-side
This limits the project’s scalability and real-world usability.
Describe the solution you'd like
I would like to implement a basic backend system to enable persistent expense storage.
The backend should:
Set up a simple server (Node.js + Express)
Connect to a database (MongoDB / SQLite)
Provide REST API endpoints:
POST /expenses → Add new expense
GET /expenses → Fetch all expenses
DELETE /expenses/:id → Delete an expense
Replace localStorage usage with API calls
Ensure frontend communicates with backend using fetch()
This will convert the project from a frontend-only application into a basic full-stack application.
Describe alternatives you've considered
An alternative approach would be continuing to use localStorage for simplicity. However, this does not provide persistent or scalable storage and limits future enhancements like authentication or multi-device support.
Additional context
This enhancement will:
Improve project architecture
Introduce backend integration
Make the project closer to real-world applications
Provide a foundation for future upgrades such as authentication and user-specific data
I would like to work on this issue if assigned.