Daily Task Tracker is a simple web application that helps users organize and keep track of their daily tasks.
The application allows users to add a task, mark a task as completed, and delete a task when it is no longer needed.
The application is designed for anyone who wants a simple way to keep track of things they need to do during the day.
It can be easy to forget small tasks or lose track of what has already been completed. The Daily Task Tracker provides a simple place to record tasks and see their progress.
- Add a new task
- Mark a task as completed
- Delete a task
- See the number of pending tasks
- See the number of completed tasks
- Prevent empty tasks from being added
- HTML
- CSS
- JavaScript
- Antigravity IDE
- Gemini 3.1 Pro High
- Git
- Live Server
I decided to keep the application simple because the goal of the project was to build a basic functional app rather than a complex product.
I focused on the core actions a user would need: adding, completing, and deleting tasks.
I also decided not to add features such as user accounts, authentication, or a database because they were not necessary for this version of the application.
I started with a basic prompt asking the AI agent to build a Daily Task Tracker using HTML, CSS, and JavaScript.
After the first version was generated, I tested the application manually. I tested adding a task, marking it as completed, deleting it, and trying to submit an empty task.
The core functions worked correctly. I also discovered during testing that the generated application already prevented users from submitting an empty task.
After testing the first working version, I initialized Git and created my first commit to record the initial version of the project.
One challenge was understanding how to move from an AI-generated application to a properly documented development project.
Instead of immediately pushing the project to GitHub, I tested the application first and used Git to record the working version. This helped me understand the importance of testing and version control as part of the development process.
Through this project, I learnt that building an application is not only about generating code. I also need to test the application, understand the decisions being made, track changes with Git, and document the development process.
I also learnt the importance of using clear commit messages so that the history of a project shows how it developed over time.
This week, I added a task filtering feature to improve how users organise and view their tasks.
The application now has three filters:
- All — shows every task.
- Pending — shows tasks that have not been completed.
- Completed — shows tasks that have been completed.
I chose to add this feature because the original application already handled adding, completing, and deleting tasks. Filtering makes it easier for users to focus on what they still need to do without changing the original design.
I tested the feature using both pending and completed tasks, and all three filters worked as expected.
This week, I added an Edit Task feature to the Daily Task Tracker.
- Users can edit an existing task without deleting it.
- A pencil icon provides access to the edit action.
- Edited task names are saved to Local Storage.
- Changes remain after refreshing the browser.
- Existing All, Pending, and Completed filters continue to work.
I tested the feature by editing an existing task to "Complete Week 5 Ship Log" and refreshing the browser. The edited task remained saved after the refresh.