GrowthJar
Product developmentMake earning, saving and waiting tangible.
A native iPhone product for children and parents, connecting a playful pocket-money experience with practical approvals, jobs and family records.
01 / The business behind the work
Start with a family agreement.
Pocket money gives children a small, practical way to learn about earning and saving. GrowthJar makes that experience visible: coins, a jar and modelled growth give a child something tangible to follow when they choose to wait.
The product records a family’s agreement. It does not hold money or offer an investment service. That distinction shapes the language, the interactions and the separate responsibilities for a child and a parent.
A closer look
The experience, in view.
Open an image to inspect it in full.
02 / The work in practice
Playful for the child. Practical for the parent.
The native iPhone app pairs its child experience with a parent area for jobs, approvals, child profiles and records. Parents can set rates and durations, review balances and record money handed over. The design has to make those everyday details understandable without turning the child’s experience into an accounting screen.
SwiftUI supplies the native presentation and SwiftData the on-device models. The product also includes an optional family unlock through StoreKit, with purchases kept in the parent journey.
03 / The work in practice
Build the offer alongside the product.
The free-one-child and paid-family structure, support content and sharing plans are part of the product’s commercial design. They connect what a family first tries with the reason it might choose to use GrowthJar more widely.
GrowthJar is supporting evidence of BTR’s product and commercial engineering. It is not presented as an agentic service; its place here is the practical connection between useful software, clear responsibilities and an understandable offer.
Access & accountability
Where control matters.
Separate parent and child experiences, with purchases in the parent journey and on-device data models in the implementation.
The commercial purpose
Why it is worth building.
Give a family a useful everyday product, with a commercial model that follows how it is used. Adoption and financial outcomes are not claimed.
A similar challenge in your business?
Let’s talk it throughNext project / Growth & customer journeys
Wheelhouse
Help the right people find their next place to work.