How hardiksjain/finplan360 works
Project Type and Purpose
• This is a full-stack mobile application where the mobile frontend (developed in Flutter) communicates with a Django backend.
• Its primary purpose is to help users track expenses by scanning debit/credit SMS messages, categorizing and visualizing their expenses, and providing tour recommendations based on spending habits.
Main Architectural Components
• Frontend (Mobile App):
• Built using Flutter, with separate folders for Android, iOS, web, macos, linux, and windows.
• Contains modular pages such as login, registration, home, profile, and expense pages.
• Handles SMS fetching, expense categorization, pie chart visualization, and tour recommendations.
• Backend (Server):
• Built using Django (files and folders such as manage.py, settings.py, urls.py, models.py, views.py, and serializers.py).
• Provides RESTful APIs to handle user authentication, registration, expense data processing, and possibly sending recommendations.
• Contains migration scripts to set up the database schema.
• Database:
• Uses SQLite (db.sqlite3) for data persistence (user accounts, expense transactions, etc.).
• Additional Data/Service:
• A dataset folder containing a travel_packages.csv file to support tour recommendation logic.
• External mobile SMS integration (for fetching and analyzing debit messages).
Relationships and Interactions
• The mobile app provides a user interface where users register, log in, and manage their finances.
• User actions (login, fetching SMS data, expense categorization) trigger API calls from the Flutter frontend to the Django backend.
• The backend processes these requests, interacts with its SQLite database, and, when needed, uses the travel packages CSV data to generate tour recommendations.
Architectural Patterns and Design Principles
• The Django backend follows the MTV (Model–Template–View) pattern with clearly separated models, views, and serializers for API endpoints.
• The Flutter frontend is organized into distinct modules (pages and components) that manage presentation and business logic separately.
• The design follows a clear separation of concerns: presentation (frontend) vs. business logic/data handling (backend).
• Using migration files indicates a versioned and controlled evolution of the database schema.