Couple_Sync

Couple Sync is a privacy-first decentralized app on ICP that turns the invisible emotional labor of relationships into a shared, rewarding journey.

Comment 2

Couple Sync

💬 3-Line Pitch

  • Headline: Couple Sync: Gamifying Shared Emotional Labor
  • Subhead: A decentralized, privacy-first dApp on the Internet Computer that turns daily relationship maintenance into a rewarding, gamified treasure hunt.
  • CTA: Try our interactive demo and unlock your first shared relationship milestone today.

📋 4-Line Problem Frame

  • User: Couples seeking to build and maintain healthy, consistent relationship habits.
  • Problem: The "invisible emotional labor" of relationship maintenance falls disproportionately on one partner (statistically women), leading to burnout and inequality.
  • Constraints: We must protect highly sensitive daily relationship data, operate seamlessly without complex Web3 onboarding, and mathematically prove a 7-day retention loop.
  • Success Test: Both partners can independently complete daily check-ins to unlock a shared, gamified "Surprise Reveal" reward at the end of a 7-day streak.

📖 Project Story

Inspiration

Relationship maintenance is often referred to as "invisible emotional labor," and for the #75HER Challenge, we wanted to address UN SDG 5 (Gender Equality) by taking this invisible work and making it visible, equitable, and rewarding.

Existing relationship apps often feel like clinical therapy checklists or heavy productivity trackers. We wanted to build something that felt like a gift. Couple Sync was inspired by the idea that consistency is the real romance. By transforming small, daily connection rituals into a gamified "treasure hunt" with a shared ledger of effort, we created a platform where emotional equity is celebrated, not just tracked.

🔐 Solo vs. Synced Modes Solo Mode (Default): Designed for individuals to build personal consistency or for partners to explore the app before inviting their significant other. All relationship data remains private and cached locally on the device.

Room Sync (Web3): Once ready, users can generate a 6-digit room code to link devices via the Internet Computer Protocol (ICP). This enables shared ritual tracking and the 7-Day Reveal Ceremony for mutual rewards.

🚀 Resilient Sync Architecture I engineered a Local-First Solo Mode using localStorage caching. This ensures that even if a partner hasn't joined the room yet or the network is latent, a user can maintain their 7-day ritual streak without interruption. The app gracefully transitions from Solo to Synced once an Internet Computer canister handshake is established.

✨ Why This Matters Low Friction: Users can start their rituals instantly without waiting for a partner to onboard.

Privacy-Centric: Data is not pushed to a shared ledger until the user explicitly chooses to "Sync".

Inclusive Design: Acknowledges that emotional labor often begins with individual accountability and supports partners in different stages of connection.

How we built it

Couple Sync was prototyped using Caffeine.ai, an agentic "vibe-coding" platform, and is built on the Internet Computer Protocol (ICP).

The application architecture utilizes:

  • Frontend: A responsive UI built with React, TypeScript, and Tailwind CSS.
  • State Management: @tanstack/react-query handles the deterministic daily ritual logic, ensuring both partners see the exact same prompt on the same day without needing a central database.
  • Smart Contract/Backend: Motoko on ICP.
  • Deployment: Hosted as an immutable frontend canister on the Internet Computer.

To create the gamified loop, we engineered a deterministic hash-based lookup for the daily rituals and a multi-stage CSS animation sequence for the "Day 7 Surprise Reveal Ceremony."

⚠️ Risk Log & Challenges We Ran Into

Building with AI agents is incredibly fast, but it introduces heavy "AI Technical Debt."

  • Risk 1: AI Code Hallucinations & UI Regressions. Midway through the sprint, our AI coding agent began hallucinating CSS classes (creating invisible white-on-white text).
    • Resolution: We implemented strict negative prompting to halt the hallucinations and manually rebuilt the Tailwind UI to guarantee WCAG-compliant color contrast (using rose-500 and rose-700 against light backgrounds) to ensure total accessibility.
  • Risk 2: Motoko Backend Connectivity & ICP Network Timeouts. Live cross-device syncing relies on network consensus, which is risky for a live demo.
    • Resolution: We executed a hard pivot to a Privacy-First architecture. Because daily relationship reflections are highly sensitive, we intentionally left the Motoko backend actor empty (actor {}) for V1 and routed all state persistence to versioned localStorage namespaces (couple-sync-completions and weeklySurprise). We engineered a "Demo Fallback" state that catches network timeouts and gracefully mocks the data, creating a zero-knowledge environment where user data never leaves their device.
  • Risk 3: Testing Time-Locks. Testing a 7-day loop in 96 hours is impossible.
    • Resolution: We engineered a hidden Developer Test Mode (activated via a triple-tap on the logo) that bypasses the time-locks, allowing QA and judges to seamlessly evaluate the Day 7 Surprise Reveal.

What we learned

We learned that the most responsible technical choice is sometimes stepping back from complex architecture to protect user privacy. We also learned the absolute necessity of strictly auditing agentic AI outputs. "Vibe-coding" requires constant human oversight to ensure code remains accessible, clean, and aligned with the intended user experience.

🌐 Current Deployment Status & Architecture

The frontend React prototype is successfully deployed and accessible via our live link for judges to test.

Current live build leans entirely on our Zero-Knowledge Local Fallback architecture. This safely simulates the future Motoko canister interactions locally, allowing you to experience the complete gamified UI and daily check-in loop without requiring an immediate mainnet connection.

  • Frontend: React, TypeScript, Tailwind CSS
  • Backend Strategy: Internet Computer Protocol (ICP), Motoko (Simulated via Local Fallback MVP)
  • State Management: Custom hooks with strictly scoped chronological modulo math
  • Prototyping Tooling: Caffeine.ai

🚀 What's Next for Couple Sync

1. Content & Gamification Expansion Right now, our prototype features curated monthly milestones and badges for Q1 (January through March). The immediate next step for the frontend is designing and implementing the full 12-month calendar of dynamic relationship content, ensuring the gamified loop stays fresh for an entire year of connection.

2. Smart Contract (Canister) Mainnet Migration We will migrate the currently simulated streak verification logic into a fully realized Motoko smart contract (canister) on the Internet Computer (ICP). By leveraging ICP's advanced cryptographic privacy features, we can build a true trustless ledger for emotional equity.

3. Minting Soulbound Tokens (SBTs) Once the backend canister is fully integrated on-chain, we will implement a minting feature using the ICRC-7 NFT standard. When couples complete their 20-day streak, the dApp will automatically mint their Monthly Bond Badges as a Soulbound Token (SBT) directly to their ICP wallets using Internet Identity. This allows partners to build a decentralized, immutable gallery of their shared relationship milestones.

4. Advanced "Mutual Gift" Logic We plan to build out edge-case logic for the Weekly Surprise picker, including a network-synced "coin toss" tie-breaker for weeks when both partners submit a grand gesture for the weekend.

5. Opt-In Push Notifications To further reduce the mental load of remembering to check in, we aim to implement privacy-preserving, opt-in daily reminders to prompt partners to log their daily connection rituals.

📚 Evidence Log

  • Code Generation: Caffeine.ai
  • Frontend Framework: React, TypeScript, Tailwind CSS
  • Blockchain/Protocol: Internet Computer Protocol (ICP), Motoko
  • Repository: GitHub - Couple Sync
  • Assets: Custom UI/UX badge graphics (Luck of Love, New Year Devotion).

*Couple Sync was developed as a solo project by Misty Waters

Built With

+ 8 more
Share this project:

Updates

posted an update —

Quick tip for testing the Couple Sync live demo!

Since the real app uses a strict 24-hour lock so couples can't peek at their clues early, I built a bypass specifically for judging. To test the full 7-day loop:

Open the live link.

Triple-click the "Couple Sync" logo at the top of the screen to unlock Developer Mode.

You can now fast-forward through a simulated week, unlock the daily hints, earn the Weekly Badge, and trigger the final Friday Surprise Reveal.

Thank you so much for your time and feedback! Let me know if you have any questions.

Log in or sign up for Devpost to join the conversation.