← Home

2026 · personal · private

Loveen러빈

A 1:1 couples app, from planning documents to native code

Role
Planning, design, implementation
Period
2026.07: ongoing
Status
Phase 1 in progress
Stack
Swift, Kotlin, NestJS, Prisma, PostgreSQL, Socket.IO
Links
GitHub

Why

“A closed space where two people record, care for and move through their relationship.” The hypothesis: the messenger is the entrance, the archive is the lock-in, the calendar is the return trigger, the map is the expansion.

What I made

  • Ten documents: Product plan, roadmap, technical architecture, critical design risks (break-up flow, data model, onboarding), Phase 1 feature spec, decision records (E2E, deletion policy, minimum OS), ERD, screen flows, API spec (REST + WebSocket events), schedule and staffing estimates.
  • Monorepo: NestJS 10 + Prisma 5 + PostgreSQL 16 + Redis 7 + MinIO + coturn backend, a Socket.IO gateway (chat, shared drawing, call signaling), SwiftUI iOS (16+), Kotlin/Compose Android (minSdk 26).
  • Phase 1 wireframes (HTML) and a nine-slide pitch deck.

Decisions

  • Two native apps (Swift + Kotlin). Messaging, calls and photo archiving lean heavily on platform APIs, so cross-platform would have cost more than it saved.
  • Break-up flow first. It is the hardest edge case in a couples app, so it was settled at the data-model stage.

Status

Planning and design complete, Phase 1 implementation in progress. The HANDOFF document is the single source of truth for current state.