Family Growth Bank is an independently developed web application designed to help families manage responsibilities, recurring tasks, rewards, and everyday activities through a structured points-based system.

The project originated from real household challenges: keeping track of responsibilities, managing recurring activities, recognizing contributions, and making family tasks easier to organize and follow through.

I designed and developed the system independently, covering product requirements, business rules, frontend and backend development, database design, testing, deployment, and ongoing improvements.

An earlier version was put into real family use, allowing subsequent design decisions to be informed by actual feedback rather than assumptions alone.

The main challenge was translating everyday household activities into a consistent and maintainable software system.

Family tasks are not always simple checklists. They may involve recurring schedules, different members, assigned responsibilities, rewards, penalties, and changes over time.

The system needed to address several interconnected requirements:

Managing family members and user accounts

Organizing one-time and recurring tasks

Recording task completion and responsibility

Applying points-based rewards and penalties

Maintaining consistent points transaction records

Supporting reward redemption and virtual inventory

Managing notifications, pending actions, and activity history

Providing traceability for important business operations

A major engineering consideration was keeping these business rules consistent as the application evolved.

Defined the product requirements based on actual household workflows and recurring management problems.

Designed the core concepts of family members, accounts, tasks, rewards, and points transactions.

Translated these requirements into application modules, workflows, and data relationships.

Developed the frontend using Vue 3 and TypeScript, with Spring Boot providing the backend application.

Implemented functionality covering:

Account and family member management

Task management and recurring activities

Temporary rewards and penalties

Points tracking and transaction history

Bounty and incentive mechanisms

Reward store and virtual inventory

Family activity records

Messages, notifications, and pending actions

Exception handling and audit records

The application connects these features through shared business rules rather than treating them as unrelated screens.

Designed a modular monolithic backend using Spring Boot and Spring Modulith.

Separated the concepts of Account and Member to distinguish system authentication from family participation.

Implemented a points Ledger to record points changes consistently, providing a structured foundation for rewards, penalties, and related operations.

Used PostgreSQL for persistent storage and Flyway for database schema migrations.

Organized the backend around business responsibilities, using a modular monolithic architecture instead of introducing unnecessary distributed services.

This approach was selected to keep the application manageable while supporting multiple interconnected business domains.

The design emphasizes clear module responsibilities, consistent data handling, and maintainability as requirements change.

Handled development, testing, acceptance checks, and private deployment using Docker Compose.

After the earlier version entered real family use, collected feedback and revisited several aspects of the product, including:

Task entry points and workflows

Task categorization

Points presentation

Task execution rules

These improvements were driven by actual usage experience and the need to make the system easier to understand and operate.

Built an independently developed full-stack family management application integrating tasks, recurring activities, points-based incentives, reward redemption, activity tracking, and audit-related functionality.

The project demonstrates the ability to take an application from requirements and business modeling through architecture, implementation, deployment, and iterative improvement.

Beyond the individual features, the core engineering value lies in designing a consistent business system where multiple modules share reliable rules and data relationships.

The experience is directly applicable to custom business applications, workflow management systems, internal tools, and other software products with complex business requirements.

Vue 3 · TypeScript · Spring Boot · Spring Modulith · PostgreSQL · Flyway · Docker Compose · Modular Monolith · Domain Modeling