Repository navigation
Releases: thuver104/MyRupees-expenceTrackingAndroidApp
Release list
v3.0.1
💰 MyRupees v3.0.1
MyRupees is a modern personal finance tracking Android app designed to help users manage their income, expenses, budgets, and recurring payments with ease. Built with a focus on simplicity and performance, version 3.0.1 introduces multi-user support and robust financial planning tools.
📸 Screenshots
📱 Features
- ✅ Multi-user support – Seamlessly handle multiple user accounts.
- 💵 Track Income & Expenses – Log and categorize transactions quickly.
- 📊 Budget Management – Set monthly budgets and get visual progress indicators.
- 🔁 Recurring Transactions – Schedule payments with auto-notifications.
- 🔔 Smart Reminders – Get notified before recurring payments are due.
- 🧠 Minimal SharedPreferences – Mostly powered by SQLite & ORM for better scalability and structure.
- 📂 Transaction History – Browse and manage your financial records effortlessly.
🛠️ Tech Stack
- Kotlin
- SQLite Database
- ORM (Room)
- SharedPreferences (used minimally for lightweight configs)
- Android Jetpack Components
- MVVM Architecture
🔔 Notifications
MyRupees supports recurring transactions that trigger system notifications two days before the due date. Once marked as "Paid," notifications stop for that instance to avoid spam.
🆕 What's New in v3.0.1
- 🔄 Added recurring transaction notifications
- 👥 Multi-user account handling
- 💹 Enhanced budget tracking and alerts
- 🐞 Minor bug fixes and performance improvements
📦 Installation
Clone the repo:
git clone https://github.com/thuve-codes/MyRupees-expenceTrackingAndroidApp.git
---
v2.0.1
Release Notes: MyRupees v2.1.1
Release Date: May 11, 2025
Overview
This release enhances the MyRupees Android application to support user-specific functionality, ensuring that each user's transactions, budgets, and recurring transactions are managed independently in a multi-user environment. The update addresses issues where data was shared across users, improving personalization and data accuracy.
Features
- User-Specific Transactions:
- Transactions in
MainActivityandAddTransactionActivityare now filtered and stored with the logged-in user's username, retrieved fromuser_preferenceswith the keycurrent_user. - Ensures users see only their own transactions on the main screen and when adding new ones.
- Transactions in
- User-Specific Budgets:
BudgetActivitynow stores budgets and monthly reset data per user using keys likebudget_<username>andsaved_month_<username>.- Expense calculations are filtered by the logged-in user, providing accurate budget tracking.
- User-Specific Recurring Transactions:
- Added a
userfield to theRecurringTransactiondata class to associate transactions with specific users. RecurringTransactionActivityfilters transactions by user and stores new recurring transactions with the current user's username.RecurringNotificationWorkerprocesses notifications per user, ensuring users receive alerts only for their upcoming payments.
- Added a
- Consistent User Management:
- Introduced a
getCurrentUser()function across activities to retrieve the logged-in user's username fromuser_preferences, replacing the incorrectSharedPrefManager.getCurrentUsername()method.
- Introduced a
Bug Fixes
- Fixed incorrect transaction filtering in
MainActivity, which previously showed guest transactions for logged-in users. - Resolved budget conflicts in
BudgetActivity, where all users shared a single budget. - Corrected
AddTransactionActivityto store transactions with the logged-in user's username, preventing them from being saved as "Guest". - Ensured
RecurringTransactionActivityandRecurringNotificationWorkerhandle only the logged-in user's transactions, fixing display and notification issues.
Breaking Changes
- Data Schema Change: The
RecurringTransactiondata class now includes auserfield. Existing recurring transactions without this field may cause deserialization errors. A migration script is recommended to assign a defaultuser(e.g., "Guest") to legacy transactions. - Budget Storage: Budgets are now stored with user-specific keys (e.g.,
budget_<username>). Existing budgets undermonthly_budgetwill not be accessible. Consider a one-time migration to copy budgets to the new format.
Recommendations
- Migration for Existing Data:
- Update
SharedPrefManager.loadRecurringTransactionsto handle legacyRecurringTransactionobjects by assigning a defaultuservalue. - Migrate existing budgets from
monthly_budgettobudget_<username>for current users during the first app run after this update.
- Update
- Centralized User Management: Consider creating a
UserManagerutility class to centralize thegetCurrentUser()logic, reducing code duplication across activities. - Database Consideration: For scalability, evaluate migrating transaction and recurring transaction storage to a database like Room, especially for users with large datasets.
Known Issues
- The login process (not provided) is assumed to set
current_userinuser_preferences. If this is not the case, user-specific functionality may default to "Guest". RecurringNotificationWorkerprocesses transactions for all users in the background. If notifications should be limited to the last logged-in user, further modifications are needed.
Installation
- Clone the repository:
git clone https://github.com/<your-username>/myrupees.git - Checkout the release tag:
git checkout v1.1.0 - Build and run using Android Studio.
Contributors
- [Your Name] - Implemented user-specific functionality and release notes.
Feedback
Please report issues or suggest improvements via the GitHub Issues page.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Thank you for using MyRupees!
MyRupees v0.1.0
myRupees - Release Notes
Version 0.1.0 (Initial Release)
Released on: 2025 April 28
Build Number: 100
🎉 Key Features Introduced
- Transaction Management (CRUD Operations)
- Create, Read, Update, and Delete transactions seamlessly
- Recurring Payments
- Schedule and track repeating expenses/income
- Customizable frequency (daily, weekly, monthly, etc.)
- Notification System
- Alerts for upcoming recurring payments
- Reminders for due transactions
- Data Export
- Export transactions to
.txtformat for backup/analysis
- Export transactions to
- Local Storage
- Uses SharedPreferences for lightweight data persistence
⚙️ Technical Implementation
- Built with Android SDK (min API level [Insert Min API])
- Current Storage: SharedPreferences
- Future-Ready Architecture: Preparing for SQLite & Room DB migration
🚀 Coming Soon (Planned Features)
- ✅ SQLite Integration (In Development)
- ✅ Room Database ORM (Planned)
- Enhanced reporting with charts/graphs
- Multi-device sync capability
- CSV/Excel export options
🐛 Known Issues
- Limited data capacity with SharedPreferences (will be resolved with SQLite)
- No bulk transaction operations
- Recurring payment customization needs improvement
📥 Installation
Available on [Asserts , Download Apk and Install
Minimum Android Version: [Insert Version]
myRupees helps you take control of your finances with simple, powerful tools. More features coming soon!









