A roommate coordination platform for iOS: shared statuses, live lists, recurring chores, and a day-timeline calendar.
Visit roomaid.app
Every roommate can share where they are and what's next, visible to the whole space at a glance.
Shopping and to-do lists that sync in real time across the household, so the whole space always sees the current state.
Lightweight check-ins and nudges keep chores and errands moving without anyone having to play the nag.
Pets, rooms, and items like vehicles and appliances are first-class subjects in a space, each with its own events and responsibilities.
Per-roommate profiles and schedules make it clear who is around, when, and who owns what.
A from-scratch recreation of the native iOS day-timeline calendar, embedded in the app as a view-only surface and built to lay out overlapping events correctly.
I designed the event sourcing for the Vapor backend myself. Every change in a space is recorded as an immutable event, which buys the classic event sourcing benefits: full replay, easier debugging, and the ability to add features that read history the original code never captured.
Recurring chores, bills, and events are powered by a custom recurrence engine built on RRULE, the recurrence-rule standard from the iCalendar spec (RFC 5545) that underpins most calendar systems.
The day-timeline view is a from-scratch layout engine that recreates the native iOS calendar's look and behavior, including correct placement of overlapping events, purpose-built for embedded, view-only use inside the app.
The backend is structured around Swift actors and modern Swift concurrency, keeping shared state safe without a tangle of locks.
Swift macros cut boilerplate across features, targeted dependency forks fill gaps where libraries fell short, and automation scripts handle local setup and service orchestration.
The codebase is modular enough that a second product, Hellopost, was assembled from the same foundation and is live on the App Store. How that foundation is kept coherent across several products at once is written up on the blog, in "Building shared infrastructure across independent iOS products."