TeamTasewa's Expense Tracker - Version 1


Planning is a must if we want to succeed in life, and that is what our expense tracker aims for. Inspired by the words of Alexander Graham bell, we decided to plan out the details of our application. 

The goal of this blog post is to give a detailed view of the features of the Expense tracker application. 


In any application, a good interface can determine whether or not it will be great; after all the user needs to feel comfortable when using it. Hence our first objective was to develop a blueprint for the UI. 



Here is a brief explanation of the flowchart:


  1. Welcome Page: When the user enters the application the first thing that they will notice is a stunning UI. It also has two options for login and signs up. 

  2. Login / Register: Here the user will log in using their credentials to access their account if they have already signed up, else they can fill the registration form, to create a new account.

  3. Dashboard: After logging in, the user will be able to view the dashboard. Here, the user can access any of the following:

    1. User Profile: The user can access their profile, make any changes if required, and also sign out.

    2. Income: The user can add, update, and view the income

    3. List of Expenses: The user can add, update, delete and view their expenses

    4. Balance: The balance will be updated automatically once the user deletes or adds the expenses and/or incomes. If the total expenses exceed 25% of the income, then the user will receive pop-up notifications indicating that their balance is low.

    5. View Stats/Graph: This feature will take us to a separate page where the expense tracking application will generate a report to show past Income-Expense via multiple graphs. 


We are planning on using HTML for the front-end and CSS along with a few bootstrap libraries for styling the pages. Thus, HTML, CSS and JS will be the technologies that we will be using for developing the front end.

For the backend, we can do either of the following:
    1) Use Local Storage or a List to store information.
    2) Use a database to store data. 
            If we decide to use a database for the backend, then we will use PostgreSQL.

Finally, to develop the View Graphs for our application we will be using a few of the existing libraries in JS such as chart.js.

Nothing becomes perfect overnight. After doing a SWOT analysis we've concluded that our application has a few drawbacks and so, here we are with the first attempt at a better version of our project. We are aiming to develop a more efficient expense tracker than other existing apps. We hope our project successfully replaces traditional methods like notes and excel sheets. The modules that we’ve presented here will be developed effectively and attractively.

Stay tuned for future versions!

Comments

Post a Comment

Popular posts from this blog

TeamTasewa's Expense Tracker - Version 2

Image
  Version 2 This is version 2 of our project, and we'll be diving deep into the working of our expense tracker. In our application, we will be importing the SQLite3 module. To connect the application to the SQLite database from the application, we need to call the Database() function of the SQLite3 module. The sqlite3.Database() will return a Database object and will open the database connection automatically. When a user opens the web app, the first thing that they will see is the Welcome Page. Here, users have an option to either login using an existing account or sign up.  New users fill in the given form, click the “Sign-Up” button and are taken to the Dashboard. The details provided will be stored in the database using an insert statement. Existing users enter their credentials which are read using the inbuilt getReadableDatabase() function and are verified with the data in the database using the string match() method. If correct, the user is redirected to the Dashboard....
Read more

TeamTasewa's Expense Tracker - Version 3

Image
This  is version 3 of Team TASEWA's Expense Tracker application. Overall diagram Click on image for a better view or ( Drive link ) Subsystems Login/Sign Up Subsystem : When the user first accesses the application, they will see the welcome page. This page has two buttons - sign up and log in. If the user already has an account, they can click on the ‘Login’ button; they will be redirected to the login page where they can enter their credentials. These details will be verified with the data in the database. If there is a match, the user will be redirected to the dashboard. If there isn’t a match, the user will be notified of the wrong entry and will be prompted to enter the details again. If the user doesn’t have an account, they can click on the ‘Sign Up’ button; they will be redirected to the sign-up page where they can enter the details required to create an account. These details will be stored as a new entry in the database Once the details have been stored, the user will be r...
Read more