tabunganku

Introduction After reviewing the design, I am not fond of the current layout. To begin with, the sidebar was initially meant to filter transactions based on their respective categories. However, I have come to the realization that the functionality is complex. Hence, I prefer to remove this feature. Additionally, I have decided to remove the category icon feature. The category icon is redundant and requires additional space to maintain. Instead, I will implement a color picker to represent each category....

Main Page From main page, we can conclude that we need an API to display category list and an API to display daily transaction. To calculate the total of each category, the value can be derived from a user’s transaction data. As a result, we don’t need a specific API to do that. Add Transaction Page (There should be a “Notes” section here) In this page, we need an API to get category list for a user and an API to add a new transaction....

Entity Relationship Diagram There are 3 entities defined: User, Transaction, and Category. A user can create many transactions, but each transaction must have one category. Entity Relationship Diagram of Tabunganku. User contains username and email properties, which are self-explanatory. Column Type username Text email Text For Transaction, it contains category, which will be filled by category ID of the transaction. date property is used to store when the transaction happens, and note is additional information regarding the transaction....

Background Since I want to improve my SpringBoot skills, I want to create something that can help my current situation. One of the things that I thought is an application to track my expense. I am using Monefy in my phone right now. I think it is better for me if I can develop something similar but for web browser, and I can also get rid of the ads !...