Problem
In a six-person home, chores, groceries, shared spending and house issues were scattered across chat and memory, making fairness difficult to see and even harder to discuss.
Back to selected work
Flagship full-stack shared-living product
HouseFair
Full-stack product engineering across UX, transactions, household-scoped data, authentication, testing, PWA delivery and honest launch gates.
Actual productHouseFair
ReleaseFree early access
DeliveryPassing GitHub Actions
QualityMobile Playwright suite
BoundaryHousehold-scoped data
01
Context and ownership
The problem, the decisions I owned and the boundary of my contribution.
My role
I built the product end to end, then moved it from a single-house workflow to a multi-household system with authentication, scoped data access, private storage and a mobile-first PWA experience.
02
System and engineering decisions
A recruiter-readable map of the product path, followed by the implementation choices behind it.
01Next.js PWA
02Validated server routes
03Household access resolver
04PostgreSQL RLS and private storage
Key product decisions
- Recurring chores, swaps, carry-over and camera-based proof
- Shared groceries, shopping mode and restock suggestions
- Expense splits, IOUs, settlements, receipts and budgets
- Calmer reminder, cleanup request and formal issue paths
- Explainable, recommendation-only fairness planning
- Next.js 16
- React 19
- TypeScript
- Supabase Auth
- PostgreSQL and RLS
- Zod
- Stripe foundation
- Playwright
- Vercel
03
Verification and release boundary
How the build is checked, delivered and kept honest about what is production-ready.
Automated verification
- Twelve mobile Playwright checks pass across Android and iPhone PWA viewports
- Regression paths cover identity, tasks, proof, groceries, money, notifications and settings
- GitHub Actions runs lint, production build and the mobile suite
- The latest CI run is passing
Deployment
Deployed on Vercel as a controlled free early-access build with an installable PWA shell.
Security
Every commercial request resolves the authenticated user, active household and membership. Zod validation, route authorization, rate limits, private Storage and PostgreSQL RLS create layered boundaries.
04
Tradeoffs and next work
What remains incomplete is shown deliberately, because engineering judgment includes knowing what not to claim.
Current tradeoffs
Paid access remains off until SMTP, full Stripe test-mode verification, legal copy, external monitoring and physical-device checks are complete.
Next improvements
- Complete physical-device install, camera and notification checks
- Add external error monitoring
- Finish paid-access operational verification
What this proves