CLI Student Expense Tracker
Built a CLI-based expense tracker with 8+ features, enabling expense management, budget tracking, category analysis, and monthly reporting in a single terminal
8
core features
3
levels of insights
4
sample transactions included
Overview
Many college students struggle to keep track of small daily expenses such as food, travel, recharges, and online payments. This often leads to unplanned spending and poor budgeting habits. Most existing expense-tracking solutions rely on internet access, mobile apps, or complex interfaces, making them less convenient for quick everyday use. The gap identified was the need for a simple, offline, and easy-to-use expense tracker that students can access directly from the command line without additional dependencies. Process I began by understanding the core problem and identifying the essential features required for an expense tracker. I first implemented the basic functionalities such as adding, viewing, and calculating expenses. To keep the code organized and maintainable, I structured the application using a class-based approach with separate methods for each operation. Throughout development, I continuously tested features and fixed bugs as they appeared. As I became more comfortable with the implementation, I added additional features such as expense editing, deletion, category-wise analysis, monthly reports, budget tracking, search functionality, and a dashboard. Each feature was tested individually after its implementation. Results The final solution is a fully functional offline expense tracker that enables users to record, manage, and analyze expenses from the command line. The application supports expense management, category-wise spending analysis, monthly reports, budget monitoring, and dashboard insights. Additional features such as editing, deleting, and searching expenses improved usability and made the tool suitable for everyday personal finance tracking without requiring internet access. Reflection A major improvement would be adding permanent local storage using JSON or CSV files so that expense data is automatically saved and loaded across sessions. This would eliminate the need to re-enter expenses whenever the application is restarted. I would also consider adding graphical visualizations, advanced filtering options, and exportable reports to provide deeper spending insights while maintaining the application's simplicity and offline accessibility.