Loading page content
A habit app built around relationships rather than streaks
Most habit apps are built around the habit: a thing you do, a streak you protect, a number that goes up. This one is built around people. A user names the relationships they want to maintain, and the app helps turn a vague intention towards a specific person into something small and concrete that actually happens this week.
That sounds like a wording difference and is a structural one. The unit of the data model is a relationship, not a task. Reminders are per person rather than per habit. And because acts of service are often better done together, a user can open an initiative and invite others into it.
I built both halves — the React Native app and the Node.js backend behind it.
Full-stack: the React Native frontend, the Node.js API and data model, notifications, and the real-time parts where an initiative updates for everyone who joined it.
A React Native client over a Node.js API, with Firebase for messaging and notifications and Socket.IO where shared initiatives need to update without a refresh. Relationships are first-class records; suggestions and completed actions hang off them, which is what makes per-person reminders and per-person history straightforward rather than a query fought against a task-shaped schema.
A habit product whose data model matches its idea — organised around the people a user is trying to look after, rather than around streaks.
If this sounds familiar
Building something similar?
Most of these problems show up again in different clothes. Describe yours and I will tell you what I would look at first.