Ledger/app/src/main/java/at/xaxa/ledger/ui/category/add/AddCategoryUI.kt

@@ -9,8 +9,6 @@ import androidx.compose.material.icons.Icons
 import androidx.compose.material.icons.filled.Add
 import androidx.compose.foundation.rememberScrollState
 import androidx.compose.foundation.verticalScroll
-import androidx.compose.material.icons.filled.Info
-import androidx.compose.material3.AlertDialog
 import androidx.compose.material3.DropdownMenuItem
 import androidx.compose.material3.ExperimentalMaterial3Api
 import androidx.compose.material3.ExposedDropdownMenuBox
@@ -18,7 +16,6 @@ import androidx.compose.material3.ExposedDropdownMenuDefaults
 import androidx.compose.material3.Icon
 import androidx.compose.material3.OutlinedTextField
 import androidx.compose.material3.Text
-import androidx.compose.material3.TextButton
 import androidx.compose.runtime.Composable
 import androidx.compose.runtime.getValue
 import androidx.compose.runtime.mutableStateOf
@@ -46,33 +43,6 @@ fun AddCategory(
     var name by remember { mutableStateOf("") }
     var selectedIconIndex by remember { mutableStateOf(-1) } // Store index of selected icon
     var expanded by remember { mutableStateOf(false) } // Controls dropdown visibility
-    var parsingError by remember { mutableStateOf(false) }
-
-    if (parsingError) {
-        AlertDialog(
-            icon = {
-                Icon(Icons.Default.Info, contentDescription = "Info Icon")
-            },
-            title = {
-                Text(text = "Parsing error")
-            },
-            text = {
-                Text(text = "One or more fields contain invalid input. Please review your entries and try again.")
-            },
-            onDismissRequest = {
-                parsingError = false
-            },
-            confirmButton = {
-                TextButton(
-                    onClick = {
-                        parsingError = false
-                    }
-                ) {
-                    Text("Okay")
-                }
-            }
-        )
-    }
 
     Column(
         modifier = modifier
@@ -162,8 +132,6 @@ fun AddCategory(
 
                         categoryViewModel.addCategory(newCategory)
                         onButtonClick()
-                    }else{
-                        parsingError = true
                     }
                 }
             )

Ledger/app/src/main/java/at/xaxa/ledger/ui/category/edit/EditCategory.kt

@@ -169,7 +169,7 @@ fun EditCategory(
             ButtonDanger(
                 modifier = Modifier
                     .padding(bottom = 8.dp),
-                "Delete",
+                "Delete Category",
                 onClick = {
                     deleteStarted = true
                     editCategoryViewModel.findEntryByCategoryId()
@@ -177,7 +177,7 @@ fun EditCategory(
             )
             ButtonSuccess(
                 modifier = Modifier,
-                "Done",
+                "Save Category",
                 onClick = {
                     editCategoryViewModel.saveCategory()
                     onButtonClick()

Ledger/app/src/main/java/at/xaxa/ledger/ui/entry/add/AddUI.kt

@@ -54,7 +54,7 @@ fun Add(
     var name by remember { mutableStateOf("") }
     var categories = addViewModel.categoryUiState.categories.collectAsState(emptyList()).value
 
-    var spending by remember { mutableStateOf("0") }
+    var spending by remember { mutableStateOf("") }
     var selectedDate by remember { mutableLongStateOf(System.currentTimeMillis()) }
     var expanded by remember { mutableStateOf(false) }
     var selectedIconIndex by remember { mutableStateOf(0) }

README.md

@@ -11,9 +11,7 @@ Ledger is a personal finance management app that enables users to log and track
 ## App Concept
 
 ### Use Case
-
 Primary Use Case:
-
 - Tracking and Managing Personal Finances
 - Viewing Financial Summaries
 - Logging Transactions
@@ -22,12 +20,10 @@ Primary Use Case:
 - Monitoring Budgets
 
 ### Target Users
-
 People who want a simple and effective way to manage their personal finances.
 People who want to stay organized by tracking their income and expenses, categorizing transactions, and gaining insights into their financial habits.
 
 Like:
-
 - Freelancers
 - Students
 - Budget-Conscious Individuals
@@ -35,21 +31,12 @@ Like:
 
 ### Mockups
 
-![Mockup](ReportImages/mockup.png)
+![Mockup](mockup.png)
-![Userflow](ReportImages/UserFlow.png)
+![Userflow](UserFlow.png)
-
-### Database
-
-![Database Design](ReportImages/database.png)
-
-The database structure consists of two tables: entry and category. The entry table stores individual records with fields like `entryid` (`primary key`), ` name`, ` amount`, ` date`, and `categoryID` (`foreign key`), while the category table stores categories with fields like `_id` (`primary key`), ` categoryName`, and ` icon`. The `categoryID` in the entry table is designed to link entries to specific categories, enabling categorization and organization of data. This structure ensures efficient data management and retrieval based on categorized relationships.
 
 ## Usability Testing Plan
-
 ### Experimental Questions & Variables
-
 1. Question: Did you find the app easy to use?
-
 	- IV: App navigation design (e.g., layout, menu structure, or usability features).
 	- DV: User-reported issues or difficulties while navigating.
 	- Methods: SEQ Question
@@ -59,19 +46,16 @@ The database structure consists of two tables: entry and category. The entry tab
 	- DV: User perception of usefulness (e.g., measured via survey or rating).
 	- Method: Likert scale How useful was it?
 3. Question: Does the user find Categories?
-
 	- IV: Visibility or accessibility of the Categories feature.
 	- DV: User success in locating or using Categories.
 	- Method: Task Completion Testing
 
 4. Question: Does the icon selection affect user satisfaction?
-
 	- IV: Icon design or selection (e.g., different icon styles or clarity).
 	- DV: User satisfaction (e.g., measured via survey or rating).
 	- Method: Open Question
 
 5. Question: How long does it take for a user to add a Category?
-
 	- IV: Process or interface for adding a Category (e.g., number of steps, clarity of instructions).
 	- DV: Time taken to complete the task.
 	- Method: Time till completion
@@ -82,16 +66,12 @@ The database structure consists of two tables: entry and category. The entry tab
 	- Method: Time till completion
 
 ### Heuristic Evaluation 
-
 Based off of Nielsen’s 10 Heuristics. Done by both team members based on the Mockup. Results were implemented in the android application.
-
 1. Visibility of System Status
-
 	- Issue: Users may not be immediately aware of changes to their balance after adding or editing a transaction, as there is no clear feedback.
 	- Recommendations: Implement a visual or auditory feedback system (e.g., a confirmation message or animation or redirect to the Balance overview) to inform users when their balance updates.
 
 2. Match Between System and the Real World
-
 	- Issues: None
 	- Recommendations: None
 
@@ -99,17 +79,14 @@ Based off of Nielsen’s 10 Heuristics. Done by both team members based on the M
 	- Issues: Users might want to create their own categories rather than use the predefined ones.
 	- Recommendations: Introduce a feature to add and delete your own categories.
 4. Consistency and Standards
-
 	- Issues: The "Your Balance" and the name of the transaction do not share the same font
 	- Recommendations: Standardize all texts to use the same font, and color scheme for a cohesive user experience.
 
 5. Error Prevention
-
 	- Issues: Users might enter invalid data, such as symbols as the amount, without receiving a warning, leading to potential errors.
 	- Recommendations: Add validation checks and warnings to prevent users from entering incorrect data, ensuring errors are caught before submission.
 
 6. Recognition Rather Than Recall
-
 	- Issues: Users may need to remember details about past transactions, such as categories or dates, which could increase cognitive load.
 	- Recommendations: Display a detailed transaction history with categories and dates visible at all times, reducing the need for users to recall information.
 
@@ -117,12 +94,10 @@ Based off of Nielsen’s 10 Heuristics. Done by both team members based on the M
 	- Issues: Users may find it time-consuming to navigate through multiple screens or steps to perform common tasks, such as adding or editing transactions.
 	- Recommendations: Ensure that all frequently used actions, like adding or deleting transactions, can be completed in as few steps as possible, with clear and accessible buttons for quick access.
 8. Aesthetic and Minimalist Design
-
 	- Issues: The interface might include too many visual elements or colors, which could distract users from focusing on their primary tasks, such as managing transactions or checking their balance.
 	- Recommendations: Ensure that the design remains clean and focused by using a limited color palette and removing any unnecessary decorative elements, keeping the interface visually simple and task-oriented.
 
 9. Help Users Recognize, Diagnose, and Recover from Errors
-
 	- Issues: Error messages may not clearly explain what went wrong or how to fix it, leaving users confused.
 	- Recommendations: Provide detailed error messages in plain language, including actionable steps to resolve the issue.
 
@@ -132,21 +107,19 @@ Based off of Nielsen’s 10 Heuristics. Done by both team members based on the M
 
 ## Results
 
+![test](test.jpeg)
+
 ### Participant Demographics
-
 - **Number of Test Subjects:** 5
-- **Demographics:** University Students aged 19-23
+- **Demographics:** Not specified in the data.
-
----
 
 ### Quantitative Evaluation
 
 #### Task Completion Time
 
 ##### Adding a Category:
-
 | Participant | Time (seconds) |
-| ----------- | -------------- |
+|-------------|----------------|
 | 1           | 18             |
 | 2           | 69             |
 | 3           | 40             |
@@ -158,7 +131,7 @@ Based off of Nielsen’s 10 Heuristics. Done by both team members based on the M
 ##### Adding a Transaction:
 
 | Participant | Time (seconds) |
-| ----------- | -------------- |
+|-------------|----------------|
 | 1           | 18             |
 | 2           | 11             |
 | 3           | 60             |
@@ -167,23 +140,12 @@ Based off of Nielsen’s 10 Heuristics. Done by both team members based on the M
 
 **Average Time:** 32.4 seconds
 
-![Time to add Category vs. Time to add Transaction](ReportImages/timeToAddCategory_vs_timeToAddTransaction.jpg)
-
-**Time to Add Category vs. Time to Add Transaction:**
-
-- The box plot shows variability in task completion times, with some participants taking significantly longer than others.
-  - For **adding a category**, Participant 2 took 69 seconds, which is an outlier compared to the others (15–40 seconds).
-  - For **adding a transaction**, Participant 3 took 60 seconds, while others completed the task in 11–43 seconds.
-- This variability suggests that some users may have struggled with the interface or navigation, particularly for adding categories.
-
----
-
 #### User Satisfaction Scores
 
 ##### Ease of Use (Scale: 1-7):
 
 | Participant | Score |
-| ----------- | ----- |
+|-------------|-------|
 | 1           | 7     |
 | 2           | 5     |
 | 3           | 7     |
@@ -192,92 +154,50 @@ Based off of Nielsen’s 10 Heuristics. Done by both team members based on the M
 
 **Average Score:** 6.4
 
-![Ease of use Graph](ReportImages/easeOfUse.jpg)
+##### Usefulness of Categories (Scale: 1-5):
 
-**Ease of use:**
+| Participant | Score |
-
+|-------------|-------|
-- The bar chart shows that most participants rated the app highly for ease of use, with four out of five giving scores of 6 or higher.
+| 1           | 3     |
-- Participant 2 gave a lower score of 5, which aligns with their feedback about difficulty finding categories and longer task completion times.
+| 2           | 4     |
-- The chart reinforces the overall positive perception of the app's usability but highlights the need to address specific pain points for users like Participant 2.
+| 3           | 4     |
-
+| 4           | 5     |
----
+| 5           | 5     |
-
-#### Finding Categories and their Usefulness
-
-##### Usefulness of Categories (Scale: 1-5) & Found Categories (Scale: Yes/No):
-
-| Participant | Score | Found |
-| ----------- | ----- | ----- |
-| 1           | 3     | Yes   |
-| 2           | 4     | No    |
-| 3           | 4     | Yes   |
-| 4           | 5     | Yes   |
-| 5           | 5     | Yes   |
 
 **Average Score:** 4.2
 
 #### Task Success Rate
 
-![Success rate of finding categories.jpg](ReportImages/successRateOfFindingCategories.jpg)
-
 **Finding Categories:**
+  - 4 out of 5 participants (80%) found the categories.
+  - 1 participant did not find the categories.
 
-- The bar chart visually confirms that the majority of participants (80%) successfully found the categories.
+**Icon Selection Satisfaction:**
-- However, 1 participant who struggled is representing areas for improvement.
+  - 4 out of 5 participants (80%) were satisfied with the icon selection.
+  - 1 participant noted that "Pets missing" in the icon selection.
 
----
+### Charts
 
-#### Usefulness of Categories vs. Found Categories
+- **Bar Chart:** Task completion times for adding categories and transactions.
+- **Pie Chart:** Percentage of participants who found categories and were satisfied with icon selection.
 
-![Usefulness of categories vs. Found categories](ReportImages/usefulnessOfCategories_vs_foundCategories.jpg)
+## Qualitative Feedback
-
-**Usefulness of Categories vs. Found Categories:**
-
-- The stacked bar chart shows a strong correlation between finding categories and perceiving them as useful.
-  - Four out of five participants found the categories and rated their usefulness highly (scores of 4 or 5).
-  - Participant 2, who did not find the categories initially, still rated their usefulness as 4, suggesting that they recognized the potential value once they located them.
-- The chart highlights the importance of making categories easy to find, as discoverability directly impacts perceived usefulness.
-
----
-
-### Qualitative Feedback
 
 **Positive Feedback:**
-
+- "The app is easy to use." (Participant 1, 3, 4)
-- "The app is easy to use."
+- "Categories are useful for organizing transactions." (Participant 4, 5)
-- "Categories are useful for organizing transactions."
 
 **Negative Feedback:**
-
+- "I could not find the categories initially." (Participant 2)
-- "I could not find the categories initially."
+- "The icon selection is missing a Pets category." (Participant 4)
-- "The icon selection is missing a Pets category."
 
 **Suggestions for Improvement:**
+- "Add more icons, especially for Pets." (Participant 4)
+- "Improve the visibility of categories in the app." (Participant 2)
 
-- "Add a Pet Icon.”
+## Updates Made to the App
-- "Improve the visibility of categories in the app."
 
----
+Based on the feedback, the following updates were made:
 
-### Updates Made to the App
+- **Improved Visibility of System Status:** Added Headings for _Category_ and _Transaction_ Screens.
-
+- **Improved Category Visibility:** The categories section was redesigned to make it more intuitive and easier to find.
-Based on the feedback and insights from the charts, the following updates were made:
-
-1. **Improved Visibility of System Status:**
-
-   - Added headings for _Category_ and _Transaction_ screens to make navigation more intuitive.
-
-2. **Improved Category Visibility:**
-   - Redesigned the categories section to make it more prominent and easier to find, addressing the issue raised by Participant 2.
-
----
-
-### Reflection
-
-#### Xaver Drabik
-
-I really enjoyed working with Florian on this project. Combining our strengths helped us create a functional and user-friendly app. Usability testing was particularly rewarding, offering insights into UI/UX design I wouldn’t have considered otherwise. Watching real users interact with the app revealed areas for improvement I might have missed. This experience deepened my appreciation for user-centered design and the importance of testing in creating a polished product.
-
-#### Florian Kraushofer
-
-I had a great time working on this project. My main focus was on the backend, and I really enjoyed tackling the coding challenges and making sure everything ran smoothly. It was cool to see how my work connected with the frontend to create a functional app. The usability testing phase was eye-opening, it showed me how small design tweaks can make a big difference for users. Overall, it was a fun and rewarding experience, and I learned a lot about both development and the importance of keeping the end user in mind.