Problem
Right now, all tasks are being stored temporarily and get deleted if the user refreshes the page or restarts the browser.
This may not be very convenient for users who wish to save their tasks permanently since they will need to make a new list every time they visit the application.
Proposal
A good idea would be to store tasks in the local storage of the browser. In doing so, they'll stay persistent, even if the user refreshes or restarts the browser.
The application may:
-
Save the tasks automatically whenever they're added, marked, or deleted by the user.
-
Load the existing tasks on opening the page.
-
Do this without disturbing the current functionality of the application.
Results
As a result, users will always see their stored tasks whenever they visit the application and delete them only upon request.
Importance of the Feature
-
Reduces chances of losing any tasks.
-
Increases practicality for day-to-day operations.
-
Improves user experience.
This feature can be developed as part of GSSoC 2026.
Problem
Right now, all tasks are being stored temporarily and get deleted if the user refreshes the page or restarts the browser.
This may not be very convenient for users who wish to save their tasks permanently since they will need to make a new list every time they visit the application.
Proposal
A good idea would be to store tasks in the local storage of the browser. In doing so, they'll stay persistent, even if the user refreshes or restarts the browser.
The application may:
Save the tasks automatically whenever they're added, marked, or deleted by the user.
Load the existing tasks on opening the page.
Do this without disturbing the current functionality of the application.
Results
As a result, users will always see their stored tasks whenever they visit the application and delete them only upon request.
Importance of the Feature
Reduces chances of losing any tasks.
Increases practicality for day-to-day operations.
Improves user experience.
This feature can be developed as part of GSSoC 2026.