I found Piggy Bank Allowance - Bomad most useful as a simple family tool for turning pocket money into something children can see and understand. Instead of handing over cash and hoping everyone remembers what happened, it gives allowance a more visible structure through virtual saving and spending jars or pots. I would recommend it to parents who want to introduce basic money habits without starting with a complicated banking product.
The app sits in the parenting category, and its focus is deliberately narrow: tracking children’s allowance and representing virtual pocket money. That narrow focus is a strength when you want a straightforward routine, but it also means you should not expect a complete household finance system. In my experience, the best results come when the app supports a conversation between parent and child rather than trying to replace that conversation.
Where families can get stuck before the routine feels natural
The first hurdle is usually not the money itself. It is agreeing on what the virtual balance means. A child may see a number in a jar and assume the money is immediately available to spend, while a parent may intend it as a record of money that will only be paid later. Before entering the first allowance, I would decide whether the app is recording real money already owed, money that has been paid, or a mixture of both. Keeping that rule consistent prevents arguments later.
The jars or pots also need a family explanation. A spending pot can represent money that the child may use soon, while a saving pot can represent a goal that requires patience. Those labels are helpful, but they do not automatically teach the difference. I found it more effective to agree on a small purpose for each one, such as everyday treats for spending and a larger planned purchase for saving. That gives every balance a reason instead of turning the app into a collection of unexplained numbers.
Another point of friction is shared responsibility. If a child expects the parent to update everything but the parent only opens the app occasionally, the record quickly becomes less trustworthy. On the other hand, giving a young child complete control over entries may create accidental changes or confusion. The right arrangement depends on the child’s age and confidence. For younger children, I would make updates together. Older children can take part in the routine while the parent checks the result.
This is also where the app differs from a physical piggy bank. A real container provides an immediate physical sensation: coins go in, and the child can see or touch them. The virtual approach is cleaner and easier to review, but it requires deliberate use. If the phone is not nearby when allowance is discussed, the family may postpone the update and forget it. I would treat the app as a short weekly ritual rather than something that should be opened for every tiny decision.
What I would agree on before entering an allowance
- Payment timing: decide whether an entry is made when money is promised or when it is actually handed over.
- Jar purpose: explain what spending and saving mean in your household.
- Responsibility: choose who records changes and who checks them.
- Corrections: agree that mistakes are fixed openly rather than hidden through extra entries.
That short conversation solves more problems than repeatedly correcting a balance. The app can display the record, but the family still has to define the rules behind it.
Setup checks that make the first week easier
When I set up a parenting app, I prefer to begin with the smallest useful routine. With this one, I would start with one child, one regular allowance, and the two basic purposes already suggested by its jar-and-pot approach: spending and saving. Adding every possible chore, exception, or family rule at the beginning can make a simple idea feel like paperwork. Once the child understands the movement of money, you can make the routine more detailed if that is genuinely useful.
The app is free to install, which makes it easy to try without committing money at the start. It has optional in-app purchases ranging from around two dollars to around thirty dollars per item, so I would still review any purchase screen carefully before handing the phone to a child. That is particularly important in a family setting, where a child may tap through a screen without understanding that a transaction is involved.
Its content rating is Everyone, which fits the family-friendly purpose, but an age label should not be mistaken for a parenting recommendation. A preschool child may understand a physical coin better than a digital balance, while a school-age child may enjoy watching a saving goal take shape. I would introduce it when the child can understand that a virtual entry represents a real family decision, not simply when the child can operate a phone.
The current version is 2.0.266 and the minimum operating system is version 9. Before troubleshooting, I would check that the device meets that requirement and that the app has been updated through the normal store process. A surprising number of setup problems come from using an older device, switching between family members’ phones, or assuming that an entry made on one device will automatically appear somewhere else without first checking how the family intends to use the app.
I would also prepare the allowance schedule outside the app. Write down the amount, the usual day, and the reason for any exceptions. This is a practical safeguard: if the balance looks wrong, you can compare it with a simple family record instead of guessing. The app is most valuable when it reduces memory work, not when it becomes the only place where the household knows what was agreed.
A low-friction first session
- Explain the difference between spending money and saving money in everyday language.
- Enter one normal allowance rather than trying to model the whole past.
- Ask the child to describe what each virtual pot is for.
- Check the displayed balance together.
- Wait through one ordinary allowance cycle before adding extra rules.
This approach also makes it easier to spot a genuine usability problem. If the child cannot explain why a balance changed, the issue may be the family’s process rather than the interface. If the parent cannot reproduce the same result from the agreed routine, the setup needs simplifying before more entries are added.
Recovering when the balance or routine goes wrong
The safest way to recover from an incorrect balance is to stop making new changes until you know what went wrong. I would first compare the current jars or pots with the family’s written allowance note, then list the last change everyone remembers. Avoid trying to repair the total by adding a random adjustment. That may make the number look right while leaving the history impossible to understand.
If a child says money has disappeared, I would ask three separate questions: was the allowance entered, was it moved between saving and spending, and was anything actually spent? Separating those events prevents a common mistake in which a transfer is treated as a new payment or a purchase is counted twice. Even with a simple virtual tracker, clear language matters more than speed.
For an accidental tap or mistaken entry, use the app’s available editing or correction path if it offers one, and make the correction with the child present. I would not quietly change the balance after the fact. The educational value of the tool comes partly from showing that records can be checked and repaired honestly. If the app does not make the correction obvious, keep a brief note of the intended balance and contact the developer, Graeme P, through the normal app-store support route rather than repeatedly experimenting with entries.
A useful recovery habit is to take a pause at the end of each allowance session. Ask the child to read back the new spending and saving amounts. This catches misunderstandings immediately, when the reason for the change is still fresh. It is more reliable than waiting until a planned purchase several weeks later, when nobody remembers whether the money was moved, spent, or never entered.
Families using more than one device should be especially disciplined. Choose one device as the place where changes are normally made, even if another phone is used for checking. Without a shared routine, two people can update the record based on different assumptions. That is not necessarily an app failure; it is a synchronization-of-people problem. A single editor or a quick verbal confirmation can prevent duplicate records.
When a missing update is not a broken app
If a balance appears unchanged, I would first check whether the allowance was actually recorded, whether it was assigned to the intended jar, and whether a different child or account was selected during the session. I would then close and reopen the app and confirm that the device is running a supported operating system. These are ordinary, low-risk checks that do not alter the family’s records.
I would avoid deleting and reinstalling the app as a first response. Reinstallation can create a new problem if the family has not established how its records are retained or restored. Before taking any destructive step, write down the balances and the dates of the last agreed entries. If the issue remains, use the app store’s official support options and describe the exact sequence: what was entered, where it was expected to appear, and what appeared instead.
When the app is not the cause
Allowance disputes often look like technical problems because the disagreement appears beside a number on a screen. In reality, the family may be using different definitions of “paid,” “earned,” and “available.” For example, a parent may enter money on the usual allowance day, while the child believes it should only appear after a chore is completed. No tracker can resolve that difference without a clear household rule.
The same applies to spending. If a child moves money mentally from saving to spending before the family has agreed to the purchase, the virtual pots may look inaccurate even though they are reflecting the last recorded decision. I would use the app to make the disagreement visible, then settle the rule away from the screen. The app should document an agreement, not silently decide which person is right.
There are also situations where another method is better. A physical piggy bank may be more motivating for a child who learns through touch and visual objects. A spreadsheet may suit a parent who wants custom categories, detailed history, or broader household budgeting. A dedicated banking product may be more appropriate for families who need real transactions, card controls, or supervised access to actual funds. Piggy Bank Allowance - Bomad is better viewed as a focused allowance companion than as a replacement for those tools.
I would also skip it if you want automatic financial administration. The appeal here is the shared routine of recording and discussing pocket money. If your goal is to connect directly to bank accounts, automate transfers, or manage several complex income sources, a general finance app will probably fit better. Likewise, if the child is too young to understand virtual money, the extra screen step may add work without adding learning.
For families with several children, the main question is not simply whether each child can have a balance. It is whether the household can maintain separate, accurate routines without confusing one child’s spending pot with another’s saving plan. I would test the process with one child first, then add another only after the first workflow feels dependable. Clear names and a consistent update order become increasingly important as the family grows.
My practical verdict after using it as a family routine
Piggy Bank Allowance - Bomad works best when you want to turn pocket money into a calm, visible teaching moment. Its strongest idea is the separation between saving and spending jars or pots, because that gives a child an immediate way to discuss short-term choices and longer-term goals. I like that it stays close to the everyday allowance problem instead of trying to become a full financial dashboard.
The average rating is 4.4 from over 600 ratings, and the app has passed 50 thousand installs, which suggests that many families have found the basic concept useful. Those figures do not remove the need to test the workflow in your own household, but they make the app worth considering if you want a free starting point. The developer is Graeme P, and the app’s focused design feels more suitable for family habit-building than for advanced money management.
My main advice is to establish the family rules before relying on the displayed balance. Decide what an entry means, keep one person responsible for routine updates, and use the saving pot for a specific goal rather than an abstract promise. If something looks wrong, pause, compare the record with your agreed allowance schedule, and correct the smallest identifiable mistake. The most important feature is not the number on the screen; it is the shared habit of checking what that number means.
For a child who is ready to connect virtual records with real pocket money, I would give it a fair trial. For a family seeking automated banking, detailed budgeting, or a tactile learning experience, I would choose a different tool. Used within its limits, this parenting app offers a practical middle ground: more structured than loose verbal promises, but simpler and less intimidating than a full financial service.
