La Red de Casa
A household scheduling app for trips, cars and drivers, with parent approval, recurring bookings and double-booking prevention.
- separate application services
- Web + API
Implementation and original delivery are documented. A walkthrough is available on request; the public entry did not complete loading in the October 20 check.
Problem
A family coordinated trips, drivers and cars through scattered messages. A useful schedule needs to express who can request a trip, who approves it and whether a vehicle or driver is already assigned.
Constraints
- Make the main workflow usable on a phone.
- Require parent approval and prevent conflicting bookings.
- Handle edits and notifications without spamming the household.
Decisions
Model the approval, not just the calendar
A booking is a workflow with request, review and assignment. Permissions and conflict checks belong in the service boundary, with the interface reflecting the saved state.
Make notifications bounded
Editing a trip should not trigger repeated noisy messages. The project includes notification rate limits and recovery/error handling alongside the scheduling features.
Outcome
Delivered an installable web app, a separate API, household onboarding guidance and a deployment runbook. This case preserves the engineering evidence even when an external demo is unavailable.
Evidence
- Implementation, onboarding and deployment documentation.
- Documented permission, conflict and notification behavior. Request a guided walkthrough.
Stack
Next.js · TypeScript · Express · PostgreSQL · Render · Vercel