Category
F&B
Platform
Website
Collaboration
Product Owner, Business Analyst, Developers
Year
2025 - 2026
TastyBite is a meal pre-ordering platform where parents pre-order meals and children collect them at the school canteen through the POS.
The product uses a Main and Sub account model: parents manage the Main account, while each child has a Sub account they spend from at the canteen.
As families with multiple children grew, managing each child's wallet separately became increasingly fragmented. We designed Family Wallet to bring funding, spending visibility, and allowance management into one place — while keeping individual control for each child.
Parents with multiple children had to top up each Sub account individually, track each child's balance separately, and manage their spending across different wallets. The existing model worked for one child, but became increasingly manual as more children were added.
The goal was therefore not simply to combine multiple wallets into one screen. It was to rethink how family funding and individual spending should work together.
The existing account structure already separated the parent from each child:
Main account — owned and funded by the parent
Sub account — assigned to each child for spending at the canteen
This raised an important product question:
If parents should only need to fund once, how can each child still have their own spending control?
Instead of treating the Family Wallet as a simple aggregation of existing wallets, I defined two separate concepts:
Funding should happen at the family level.
Spending control should remain at the child level.
This became the foundation for the rest of the experience.
We decided to make the Family Wallet the default destination for top-ups, rather than asking parents to choose a child every time they added money.
Parents fund one shared pool first. Daily Allowance then determines how much each child can spend from that pool.
This reduced the number of decisions required during top-up while preserving the individual spending control that the existing Sub account model provided.
We structured the Family module around three core areas:
Family Wallet
The shared balance and primary Top-up action sit at the center of the experience.
Family Members
Parents can see the children connected to the family and understand who they are managing.
Daily Allowance
Each child's spending limit is visible and adjustable without leaving the Family experience.
The goal was to make the relationship between shared money and individual spending immediately understandable rather than exposing the underlying account complexity.
The initial requirement only covered daily allowances. Rather than designing a pattern that would only work for one frequency, we structured the allowance experience so that weekly and monthly limits could be introduced later without requiring a fundamental redesign.
This was a deliberate scalability decision: solve today's requirement while leaving room for the product to evolve.
The Family model needed to remain coherent across four different surfaces:
Parent experience
Admin
POS
Kiosk
Each surface serves a different user and purpose, but they all depend on the same underlying wallet and family model. I therefore focused on keeping the product logic consistent, while adapting how that logic was presented to each user. This meant the work was not just about designing a new screen. It was about making sure one product model could work across the ecosystem.
I worked with the Product Owner, Business Analyst, and Developers throughout the design process to align on the wallet model, account relationships, and implementation considerations. The discussions were not limited to visual design. We had to make sure decisions around shared funding, individual allowances, and multiple product surfaces were practical within the existing TastyBite ecosystem.
This helped turn the Family Wallet from a UI concept into a feature that could actually ship.
Family Wallet v1 shipped with the shared wallet, Top-up, and Daily Allowance experience ready for the start of the school year. Parents now have one place to fund, track, and manage spending across their children instead of handling separate wallets individually.
Early feedback has been positive, although it remains qualitative at this stage. The Family experience is also planned to evolve further as the team learns from real-world usage.
The most important design work was defining how the wallet should behave, not how the screens should look. Separating shared funding from individual spending gave us a simpler experience for parents without removing the control required for each child.
This module strengthened my approach to product design: before designing the interface, define the model, the relationships, and the decisions the product needs to support.
