Overview
Becoming helps people define where they want to go, divide the year into manageable seasons and connect long-term direction to everyday habits.
Problem
Most habit trackers focus on streaks without preserving the larger reason behind the habit. I wanted the data model and interface to connect daily action to a broader season and yearly vision.
What I built
- A multi-model data layer for users, seasons, habits and daily check-ins.
- Server-action writes and dashboard reads with type-safe Prisma queries.
- Authentication, seed scripts, migrations and production deployment.
Engineering decisions
I configured Prisma 7 against PostgreSQL on AWS Aurora, handled SSL/TLS connection requirements and kept database access behind server actions. The schema separates long-lived goals from daily records so each can evolve without flattening the product into a single checklist.
What I learned
This project strengthened my understanding of relational schema design, production database configuration and the practical difference between getting a feature working locally and making it reliable after deployment.