Families were patching together too many disconnected tools
Scheduling in one app, chores on a whiteboard, finances in a spreadsheet, health in notes, and communication spread everywhere else - the overhead of stitching family life together was becoming its own job.
HOW IT WAS BUILT
One shared model across web, mobile, desktop, and backend
Storm's End is a pnpm monorepo with shared TypeScript types across a React web app, React Native mobile app, Electron desktop shell, and a NestJS backend with WebSocket sync.
The system now spans nine connected modules, background workers, role-based APIs, and shared business rules so the same family state can move cleanly between browser, phone, and desktop without becoming three separate products.
INSIDE THE PRODUCT
Core surfaces that define the experience
Planning Layer
Weekly command center
Schedules, anchor events, tasks, and recovery constraints all sit in one shared planning surface so the family can reason about time before the week breaks apart.
Designed to replace the spreadsheet + group text + mental math stack.
Family Roles
Different interfaces for different people
Parents can manage load and household systems, teens can see responsibilities and schedules, and younger kids get a lighter interface without inheriting adult complexity.
Same family state, different permissions and visibility rules.
Signal Layer
Life data becomes coordination data
Sleep, health, finances, and chores all contribute to a shared pulse so the app can surface overload, imbalance, and household drift earlier.
Events become signals, not just records.
KEY FEATURES
What makes it work
Conflict Detection Engine
Real-time calendar validation checks for double-booking, anchor overlaps, overwork violations, sleep boundary violations, and load inequity before plans ever settle into the week.
Role-Based Experience
Parents, teens, and children each get a tailored interface with different permissions, finance flows, chore systems, and visibility rules enforced at the API layer.
Pulse Intelligence Engine
Events, tasks, sleep, health, and financial activity all write into a shared signal layer so the product can generate evidence-based nudges, alerts, and milestones.
WORKFLOW
How the family loop works
Storm's End is designed around a weekly coordination cycle rather than isolated features, so each module improves the same shared picture of family life.
01
Capture the week
Schedules, appointments, obligations, and tasks enter the system from web, mobile, or desktop without splitting into separate copies of truth.
02
Resolve pressure early
Conflict detection and role-aware review catch overload, overlap, and inequity before they become household stress.
03
Sync the household state
Shared types, real-time events, and background jobs keep every client aligned so coordination survives device switching and context changes.