More project photos (2)
The problem
Pocket Money Diary is an Android app that helps school students plan a weekly budget, record everyday spending, and save toward a small goal in one simple diary. A student starts the week with a weekly budget of ₹500, split across snacks, stationery, travel, games, and savings, then logs each expense as it happens and watches the remaining balance update. In the demo week, the diary shows ₹215 spent across 5 entries, ₹85 moved to savings, and ₹200 remaining, so the three figures add up exactly to the ₹500 budget. A savings goal for a geometry box set tracks ₹285 saved toward a ₹400 target, with ₹115 still to save. All records stay on the device in local storage, and the app never touches a bank account, a payment, or a money transfer.
Builder note from the demo build: the weekly reset was first sketched as a simple calendar reset that wiped everything each Monday, but testing the demo week showed that wiping the savings total too would erase the student's progress toward the geometry box set, so the build now resets only category spending each week while the savings balance of ₹285 carries forward. The quotable mechanism line of the app is that every rupee of the ₹500 budget is always in exactly one of three places: spent, saved, or remaining.
Sets a weekly budget of 500 rupees and logs each expense as it happens.
Follow the working sequence
How it works
The diary works as a closed weekly loop: set the budget, log spending, move money to savings, and review the week before the next one begins. On Monday the student sets a weekly budget of ₹500 and splits it across snacks, stationery, travel, games, and savings, giving each category its own limit. During the week every expense is logged with a description, a category, and an amount, and the app subtracts it from the remaining balance and adds it to that category's total. When the student chooses to save, ₹85 moves into the geometry box set goal in the demo week, raising its saved total to ₹285 of the ₹400 target. On Sunday the weekly summary shows ₹215 spent, ₹85 saved, and ₹200 remaining, and the next week starts fresh with category spending reset to zero while only the savings balance carries forward.
- The student opens the diary on Monday and sets the weekly budget of ₹500, split across snacks, stationery, travel, games, and savings.
- Each expense is logged with a short description, one of the 4 spending categories, and an amount in rupees.
- The app adds the amount to that category's spent total and subtracts it from the remaining balance at once.
- The category bars update, so the student sees snacks at ₹75 of ₹150, stationery at ₹60 of ₹100, travel at ₹50 of ₹80, and games at ₹30 of ₹70 in the demo week.
- When the student decides to save, an amount is moved to the savings goal instead of being counted as spending, reaching ₹85 in the demo week.
- The savings goal screen updates to ₹285 saved of the ₹400 target, at 71% progress with ₹115 still to save.
- On Sunday the weekly summary shows ₹215 spent, ₹85 saved, and ₹200 remaining, and the next week resets category spending while the ₹285 savings balance carries forward.
How it compares
| Approach | Weekly budget view | Works without a bank account | Savings goal tracking | Needs internet |
|---|---|---|---|---|
| This Pocket Money Diary | Yes · budget, spending, and savings on one screen | Yes · local diary records only | Yes · goal with progress shown | No · local storage only |
| Paper notebook diary | Partly · totals must be added by hand | Yes · paper only | Only by hand · no progress calculation | No |
| Spreadsheet budget sheet | Partly · formulas must be built first | Yes · manual entries only | Only with extra setup | No |
| Bank-linked budgeting app | Yes · automatic totals | No · needs a bank account | Yes · goal tracking included | Yes · account sync needs internet |
Tech stack:
- Kotlin · Android application code
- Android Studio · app development environment
- Room · on-device local database
- Material Design components · app interface
- HTML · CSS · JavaScript · interactive prototype of the same diary screens
- Git · version control
| Parameter | Value |
|---|---|
| Platform | Android phone or tablet · single-user diary app (design target) |
| Weekly budget | ₹500 per week (demo week value) |
| Category budgets | Snacks ₹150 · Stationery ₹100 · Travel ₹80 · Games ₹70 · Savings ₹100 (demo week values) |
| Demo week spending | ₹215 across 5 expense entries (measured from the demo) |
| Demo week savings | ₹85 moved to savings (measured from the demo) |
| Demo week remaining | ₹200 (measured from the demo: ₹500 minus ₹215 minus ₹85) |
| Category spending in demo | Snacks ₹75 · Stationery ₹60 · Travel ₹50 · Games ₹30 (measured from the demo) |
| Savings goal | Geometry box set · ₹285 saved of ₹400 target · 71% progress · ₹115 to go (measured from the demo) |
| Savings balance carried forward | ₹285 from earlier weeks plus this week (measured from the demo: ₹200 earlier plus ₹85 this week) |
| Storage | Local only via Room and SQLite · no account and no cloud sync (design target) |
| Money handling | Diary records only · no bank account · no payment · no transfer (design target) |
| Weekly reset rule | Category spending resets each Monday · savings balance carries forward (design rule) |
| Demo data set | 5 expense entries plus 1 savings transfer (measured from the demo) |
Project features
Weekly budgets, quick expense entry, category tracking, a savings goal, and a weekly summary are the capabilities that make this diary useful for a school student. The weekly budget screen shows the ₹500 budget beside ₹215 spent, ₹85 saved, and ₹200 remaining, so the student always sees the whole week at a glance. Expense entry takes only a description, a category, and an amount, and each entry updates the category totals and the remaining balance at once. The savings goal screen tracks ₹285 saved toward the ₹400 geometry box set target, showing 71% progress and ₹115 still to save. The weekly summary closes the week with one honest table: budget, spending, savings, and remaining, all adding up exactly to the weekly budget. Category bars and the weekly summary keep every figure visible, so nothing about the week stays hidden from the student.
- [Weekly budget setup] The student sets one weekly budget of ₹500 and splits it across 5 categories: snacks, stationery, travel, games, and savings. Implemented in the base build.
- [Quick expense entry] Each expense needs only a description, a category, and an amount in rupees, and the entry updates the category total and the remaining balance at once. Implemented in the base build.
- [Category spending bars] Snacks, stationery, travel, and games each show spent money against their own weekly budget, so overspending in one category is visible immediately. Implemented in the base build.
- [Savings goal tracking] The geometry box set goal shows ₹285 saved of a ₹400 target at 71% progress, with ₹115 still to save, and grows by each amount the student moves to savings. Implemented in the base build.
- [Weekly summary screen] One table closes the week: ₹500 budget, ₹215 spent, ₹85 saved, and ₹200 remaining, with the three outcome figures adding up exactly to the budget. Implemented in the base build.
- [Weekly reset rule] Category spending returns to ₹0 each new week while only the savings balance carries forward, so last week's unspent category money cannot be quietly overspent later. Implemented in the base build.
- [Local-only storage] All diary records are stored on the device with Room and SQLite, with no account, no cloud sync, and no internet needed for daily use. Implemented in the base build.
Optional on request: a second savings goal tracked beside the first, and a monthly view that adds 4 weekly summaries together. Future scope: a reminder to log the day's spending each evening, and a parent view that shows only the weekly summary without editing rights.
What is included
- Complete Android application source code in Kotlin, with weekly budgets, expense entry, category tracking, and savings goals
- Interactive prototype of the same diary screens, with the demo week showing ₹215 spent, ₹85 saved, and ₹200 remaining
- Demo-week data set used in the demonstration, with the budget split and the savings goal documented
- Weekly reset rule documentation, explaining which figures reset and which figure carries forward
- Project report PDF (background, pocket-money planning problem, methodology, worked demo week, limitations)
- PPT presentation for final review
- Viva Q&A preparation document (weekly budgets, local storage, savings goals, weekly reset logic, no-bank-account design)
Limitations & prerequisites
- The app keeps diary records only: it never connects to a bank account, never makes a payment, and never transfers money, so it cannot track real bank balances.
- All entries are typed in by hand: there is no automatic import from a bank statement or a payment app, so a forgotten entry leaves the weekly totals incomplete.
- One student uses one device: there is no account, no cloud sync, and no sharing between two phones, so diary records stay on the device where they were entered.
- The app is built for Android only: an iPhone version would need a separate build and is not part of the base project.
- Unspent category money does not roll over: the weekly reset returns category spending to ₹0 each Monday, so a student who underspends on snacks one week does not gain extra snack money the next week.
- Figures describe the demo week only: the ₹500 budget, the ₹215 spending, and the ₹285 savings total are demonstration values, and a real student's figures will differ.
- The diary records spending but gives no financial advice: it does not recommend how much to save or how to spend, and the savings goal is a target the student sets.
Frequently Asked Questions
What does the diary do with a student's weekly pocket money?
The diary turns a weekly pocket money amount into a plan the student can follow: a budget of ₹500 is split across snacks, stationery, travel, games, and savings, each expense is logged as it happens, and the remaining balance updates at once. In the demo week, 5 entries totalling ₹215 in spending plus ₹85 moved to savings leave ₹200 remaining, and the savings goal for a geometry box set reaches ₹285 of its ₹400 target. The student therefore sees where the money went without doing any arithmetic by hand.
Does the app move real money or connect to a bank account?
No, the app never moves money and never connects to a bank account, because every entry is a diary record typed in by the student and stored on the device in local storage, and no payment step exists anywhere in the app. There is no payment step, no transfer step, and no bank link anywhere in the app, so nothing in the diary can change a real balance. The ₹85 moved to savings in the demo week is a record of money the student set aside in real life, not a transfer performed by the app.
How does the weekly budget reset work?
Each new week starts with category spending back at ₹0 and a fresh weekly budget of ₹500, while only the savings balance carries forward into the next week, so the student's progress toward a savings goal survives while weekly spending starts clean. In the demo week this means the ₹285 saved toward the geometry box set survives the reset, but the ₹75 of snack spending and the other category totals do not. The rule keeps weeks comparable and stops unspent money in one category from quietly becoming extra spending money later.
Can categories and savings goals be changed?
Yes, the category budgets and the savings goal are settings the student can change at any time, because a student who spends more on travel than on games should be able to rebalance the ₹500 weekly budget to match real habits. The 5 demo categories and the ₹400 geometry box set target are starting values, not fixed rules, and changing a budget does not rewrite the entries already logged for the current week. A second savings goal can be added on request, but it is not part of the base build.
Is this project suitable for a final-year project?
Yes, Computer Science and IT students can use this project because it covers Android app development, local database design with Room and SQLite, user-interface design, and weekly data logic in one demonstrable app with a live demo that shows every figure updating together. The demonstration is easy to verify live: set the weekly budget, log an expense, move an amount to savings, and watch the budget, spending, savings, and remaining figures update together. The weekly reset rule and the local-only design also give clear design decisions to explain in a review.
Components & software requirements
- Kotlin · Android application code
- Android Studio · app development environment
- Room · on-device local database
- Material Design components · app interface
- HTML · CSS · JavaScript · interactive prototype of the same diary screens
- Git · version control
Delivery information
Built-to-order project. Delivery timeline is shared after order confirmation based on current queue.
Support terms
Complete documentation, setup guide, and viva preparation included. Support for setup and explanation provided.
Download free synopsis (PDF)
Enter your name and WhatsApp number — the synopsis PDF downloads immediately. We may send occasional project updates on WhatsApp; no spam.