BondoMan

Transaction logging app for raw material trades

BondoMan Mobile Application

BondoMan is an application centered around managing transactions efficiently. Users are required to log in initially to access its features, with the endpoint providing a token upon successful login for further access. The app enables users to manipulate transaction data, including addition, modification, and deletion, with minimal input requirements such as transaction title, category (Income, Expense), amount, and location, automatically recording the transaction date and user's location if permitted. Transactions are stored in Room using the Repository Pattern for offline access, displaying them comprehensively with details like transaction category, amount, name, location, and date. Users can add transactions, scan receipts, view transaction summaries via graphs, and export transaction lists to spreadsheets (xlsx or xls) for external viewing. BondoMan also features internet connectivity checks, providing alerts when offline, and incorporates a broadcast receiver in the transaction addition fragment for receiving intents from the "Randomize Transaction" button on the Settings Page.

📝 Table of Contents

• General Information
• Tech Stacks
• Libraries
• Main Features
• Bonus 1 - Twibbon Feature
• Bonus 2 - OWASP Analysis
• Bonus 3 - Accessibility Testing
• Task Division
• Contributors

📢 General Information

Bandung Bondowoso, a project manager tasked with building a thousand temples, faces a daunting challenge. Given a project by Roro, who lacks understanding in project management triangles—budget, deadline, and quality—Bondowoso must complete the monumental task within a single night with limited budget and high-quality expectations. Amidst numerous transactions for purchasing raw materials, precise cost calculations are crucial to align with the initial budget plan, as Roro refuses to pay otherwise. Initially, Bondowoso records all transactions on stone tablets, but with the immense scale of the project, he seeks assistance from the Jin students at the Institute of Jin in their sixth semester to develop a financial management application. He trusts that they possess the intelligence to tackle such a task.

The application built for Bondowoso is tailored to run seamlessly on his Android device, aiding him in managing his finances for the temple construction project. With a focus on tracking transactions, ensuring budget compliance, and facilitating efficient resource allocation, the app is designed to alleviate Bondowoso's burden and streamline the financial aspect of the project. By providing a user-friendly interface for recording transactions, analyzing expenses, and generating reports, the application empowers Bondowoso to make informed financial decisions, ultimately contributing to the smooth progress of the temple construction endeavor.

👨🏻‍💻 Tech Stacks

Kotlin | Google Maps | GMail | Room-SQLite | Spreadsheet | Android Studio

📖 Libraries

Here's list of libraries that used in this project.

Libraries	Purposes
com.squareup.retrofit2	Type-safe HTTP client for Android for making HTTP requests to a RESTful API.
androidx.recyclerview	Efficiently display large sets of data in a scrollable list or grid format while minimizing memory usage and improving performance.
androidx.camera	High-level API for accessing device cameras and implementing common camera features such as preview and image capture.
org.jetbrains.kotlinx:kotlinx-coroutines	Provides support for Kotlin coroutines, which are a powerful concurrency design pattern used for asynchronous programming.
androidx.room	Provide an abstraction layer over SQLite, making it easier to work with a SQLite database within application.
org.apache.poi	Provide Java libraries for reading and writing various Microsoft document formats, such as Excel spreadsheets (.xls and .xlsx).
com.google.android.gms:play-services-location	Providing a comprehensive set of APIs for location awareness, geofencing, activity recognition, and location updates.
com.github.PhilJay:MPAndroidChart	Serves the purpose of providing a versatile and customizable charting library for Android applications.

And some android core libraries like appcompat, constraintLayout, livedata, viewmodel, fragment, navigation, and many more!

⭐ Main Features

Here's BondoMan main features and its interface.

Splash Screen	Login Page	Transaction Page	Insert New Transaction Page
Update Transaction Page	Get Transaction Location	Transaction Graph Page - Potrait	App Setting Page
Transaction Graph Page - Landscape		Scan Notes Page	Scan Result View
Delete Transaction Popup	Upload Notes to Scan	Send Transaction List	Randomize Transaction Result

🤳 Bonus 1 - Twibbon Feature

Twibbon Page	Twibbon Result #1	Twibbon Result #2

Twibbon is what we called when we overlay a base image with another image to create a new and creative picture. With this feature, user can choose between 6 different and funny overlay to go with their image. They can capture their photo, and immediately receive a twibbon of it. They can use this feature as much as they like and experiment with the different overlay provided.

💥 Bonus 2 - OWASP Analysis

OWASP (Open Web Application Security Project) Top 10 is a list of the ten most critical application security risks. Here is our analysis on 3 of them and how we address those security vulnerabilities.

🔒 M4: Insufficient Input/Output Validation

Insufficient validation and sanitization of data from external sources, such as user inputs or network data, in a mobile application can introduce severe security vulnerabilities. Mobile apps that fail to properly validate and sanitize such data are at risk of being exploited through attacks specific to mobile environments, including SQL injection, Command Injection, and cross-site scripting (XSS) attacks.

These vulnerabilities can have detrimental consequences, including unauthorized access to sensitive data, manipulation of app functionality, and potential compromise of the entire mobile system.

Inadequate output validation can result in data corruption or presentation vulnerabilities, allowing malicious actors to inject malicious code or manipulate sensitive information displayed to users.

An application can be vulnerable to insufficient input/output validation due to:

• Lack of Input Validation: Failure to properly validate user input can expose the application to injection attacks like SQL injection, command injection, or XSS.
• Inadequate Output Sanitization: Insufficient sanitization of output data can result in XSS vulnerabilities, allowing attackers to inject and execute malicious scripts.
• Context-Specific Validation Neglect: Neglecting to consider specific validation requirements based on data context can create vulnerabilities, such as path traversal attacks or unauthorized access to files.
• Insufficient Data Integrity Checks: Not performing proper data integrity checks can lead to data corruption or unauthorized modification, compromising reliability and security.
• Poor Secure Coding Practices: Neglecting secure coding practices, such as using parameterized queries or escaping/encoding data, contributes to input/output validation vulnerabilities.

Here are how we address the vulnerabilities.

1. Unsanitized Query and Improper Parameter To prevent SQL Injection attacks, we use Room as persistence mechanism and define the queries and its parameters in DAO (Data Access Object) interface. Room will handle the parameter binding and ensure the execution of properly sanitized query.

2. Improper Output From Calling Server API To handle malicious output given by server API when requesting something, we use data class to contain the output/response. This ensure proper and structured data type usage and correct data name.

3. Unexpected User-Generated Output To handle occasion where processing user input leads to null value, we use default value so that the application still behaves expectedly when that result is used again.

4. Malformed User Input Data Ensuring that user fills all the required data before processing to prevent unexpected output that may affect subsequent usage of that output.

🔒 M8: Security Misconfiguration

Security misconfiguration in mobile apps refers to the improper configuration of security settings, permissions, and controls that can lead to vulnerabilities and unauthorized access. Threat agents who can exploit security misconfigurations are attackers aiming to gain unauthorized access to sensitive data or perform malicious actions. Threat agents can be an attacker with physical access to the device, a malicious app on the device that exploits security misconfiguration to execute unauthorized actions on the target vulnerable application context.

Security misconfigurations in mobile apps can be exploited through various attack vectors, including:

• Insecure default settings: Mobile apps often come with default configurations that may have weak security settings or unnecessary permissions enabled, making them vulnerable to attacks.
• Improper access controls: Misconfigured access controls can allow unauthorized users to access sensitive data or perform privileged actions.
• Weak encryption or hashing: Improperly implemented or weak encryption and hashing algorithms can be exploited to gain access to sensitive information.
• Lack of secure communication: Failure to use secure communication protocols, such as SSL/TLS, can expose sensitive data to eavesdropping and man-in-the-middle attacks.
• Unprotected storage: Storing sensitive data, such as passwords or API keys, in an insecure manner, such as plain text or weakly encrypted, can lead to unauthorized access.
• Insecure file permissions: Storing application files with world-readable and/or world-writable permissions.
• Misconfigured session management: Improper session management can result in session hijacking, allowing attackers to impersonate legitimate users.

Here are how we address the vulnerabilities.

1. Debugging Enabled in Manifest To prevent exposing sensitive information in debug mode, set android:debuggable="false" in the application tag of the AndroidManifest.xml file.

2. Unprotected Exported Components To protect activities from unauthorized access, set android:exported="false" for activities that don't need to be accessed by other applications.

3. Improper Content Provider Permissions Limit access to content providers by setting appropriate permissions and ensuring android:exported="false" unless necessary for external access.

4. Improper Content Provider Permissions Utilize internal storage or external storage with proper permissions. Before write to user's external download directory, we ask the user permission first. If the user permissions has already been granted then proceed the file saving.

🔒 M9: Insecure Data Storage

Insecure data storage in a mobile application can attract various threat agents who aim to exploit the vulnerabilities and gain unauthorised access to sensitive information. These threat agents include skilled adversaries who target mobile apps to extract valuable data, malicious insiders within the organisation or app development team who misuse their privileges, state-sponsored actors conducting cyber espionage, cybercriminals seeking financial gain through data theft or ransom, script kiddies utilising pre-built tools for simple attacks, data brokers looking to exploit insecure storage for selling personal information, competitors and industrial spies aiming to gain a competitive advantage, and activists or hacktivists with ideological motives.

Here are common manifestations of these issues:

• Lack of Access Controls: Insufficient access controls within the application may allow unauthorized users or attackers to gain access to sensitive data stored on the device or in the app’s databases.
• Inadequate Encryption: Failure to properly encrypt sensitive data can result in unintended data leakage if an attacker gains access to the storage location. Without encryption, the data is easily readable and can be exploited.
• Unintentional Data Exposure: Mobile applications may inadvertently expose sensitive data through application logs, error messages, or debug features, allowing unauthorized individuals to view or capture sensitive information.
• Poor Session Management: Weak session management can lead to unintended data leakage. If session tokens or user authentication information are not adequately protected or managed, they can be intercepted or manipulated, allowing unauthorized access to sensitive data.
• Insufficient Input Validation: Inadequate input validation and data sanitization can lead to unintended data leakage. Attackers may exploit this weakness to inject malicious scripts or retrieve sensitive data by manipulating input fields.
• Cloud Storage Misconfigurations: If the mobile application uses cloud storage services for data storage and the configurations are mismanaged or misconfigured, it can result in unintended exposure or unauthorized access to stored data.
• Third-Party Library Vulnerabilities: Insecure third-party libraries used in the mobile application may have vulnerabilities that could lead to unintended data leakage. Attackers can exploit these vulnerabilities to gain unauthorized access to sensitive information.
• Unintended Data Sharing: Improper handling of data sharing features within the application can result in unintended data leakage. If sensitive data is shared with unintended recipients or if the sharing process is not adequately secured, it can lead to privacy breaches

Here are how we address the vulnerabilities.

1. The Appropriate Implementation of Permissions by utilizing the Android permission system, which allows users to grant specific permissions for access to certain data or features such as location access permission and gallery access permission.

2. Strong Session Management by implementing robust session management to protect user data and utilizing unique session tokens and ensure they are securely stored on the device.

3. Careful Data Sharing Management. When handling data sharing features, we provided adequate control to the users.

4. Careful Data Log Management and Error Handling by ensuring that sensitive data is not included in application logs. Additionally, we implemented error handling mechanisms that prevent the logging of sensitive data in error messages.

🙋‍♂️ Bonus 3 - Accessibility Testing

Accessibility Scanner is a tool developed by Google and used to scan an application's user interface to provide recommendations on how to improve the application's accessibility. Accessibility Scanner enables anyone, not just developers, to quickly and easily identify common accessibility improvements; for example, zooming in on small touch targets, increasing contrast for text and images, and providing content descriptions for unlabeled graphic elements.

The following is what the suggestion page looks like before the application is repaired.

Result by Page	Result by Category

It was found that there were 171 suggestions from various different pages. We fulfill all these suggestions based on their categories.

1. Item Label
   The fix is documented on this commit. Here is the updates:
   • For EditTexts or editable TextViews, use an android:hint attribute to indicate the purpose of the text field.
   • Use an android:labelFor attribute to indicate that a View should act as a content label for another View.
2. Touch Target
   The fix is documented on this commit. Here is the updates:
   • Consider making the height of this touch clickable item target 48dp or larger.
   • A parent container may be handling touch events for this item. If selecting the larger container performs the same action as selecting this item, consider defining this item as not clickable. If a different action is performed, consider increasing the size of this item.
3. Text Contrast
   The fix is documented on this commit. Here is the updates:
   • When using TextView to display text, use android:textColor and android:background to define foreground and background colors with a high contrast ratio.
   • The W3C recommends:
     • At least 4.5:1 for small text (below 18 point regular or 14 point bold).
     • At least 3.0:1 for large text (18 point and above regular or 14 point and above bold).
4. Item Descriptions
   The fix is documented on this commit and this commit. Here is the updates:
   • Each element should have a unique text label that describes its visual meaning, purpose, or associated action.
   • Layouts used as rows within ListViews or RecyclerViews are often inflated repeatedly. In such a case, the repeated labels should include additional text with more identifying information or context for the description of the item.
5. Image Contrast
   The fix is documented on this commit. Here is the updates:
   When using ImageView or Image to render graphical content or iconography, make sure that contrast between foreground and background colors meets or exceeds the recommended ratios.
6. Unexposed Text
   The fix is documented on this commit. Here is the updates:
   • Visible text in a user interface component should be available to accessibility services.
   • A ViewGroup that represents a list row is labeled with a contentDescription that customizes the ordering descendant TextViews.
7. Item Type Label
   The fix is documented on this commit. Here is the updates:
   • When TalkBack announces a clickable Button element, it appends the word "button" to the text label provided by the developer. If the developer includes "button" in the text label (such as "Save button"), TalkBack might speak the word "button" twice ("Save button button").
   • A well-implemented user interface doesn't add element type or state descriptions to values of android:contentDescription, android:text, or android:hint attributes.

After fulfilling all these quite tiring suggestions, BondoMan finally succeeded in achieving high accessibility with no further recommendations. Here is the final result.

Result by Page	Result by Category

👨‍👨‍👦‍👦 Task Division

The following is the division of tasks that we carry out.

Task	13521062	13521063	13521108
Initialization
Initiate Project			✅
Setup Room Database			✅
Main Features
Header dan Navbar			✅
Login - Halaman Login			✅
Logout - Halaman Pengaturan			✅
Melakukan Penambahan, Pengubahan, dan Penghapusan Transaksi		✅
Melihat Daftar Transaksi yang Sudah Dilakukan		✅
Melakukan Scan Nota - Halaman Scan Nota	✅
Melihat Graf Rangkuman Transaksi - Halaman Graf	✅
Menyimpan Daftar Transaksi dalam Format .xlsx, .xls - Halaman Pengaturan			✅
Intent GMail - Halaman Pengaturan		✅	✅
Background Service - Mengecek expiry JWT			✅
Network Sensing - Deteksi Sinyal	✅
Broadcast Receiver - Randomize Transaksi dari Pengaturan	✅	✅
Bonus
Twibbon	✅
OWASP	✅	✅	✅
Accessibility Testing			✅

👏 Contributors

Contributors	Preparation Time	Working Time
13521062 - Go Dillon Audris	12 hours	40 hours
13521063 - Salomo Reinhart Gregory Manalu	12 hours	48 hours
13521108 - Michael Leon Putra Widhi	16 hours	36 hours