The starting point
Partners may lack a lightweight shared structure for discussing preferences, communication, attachment, values, and daily connection. The product attempts to turn independent answers into private couple comparisons, prompts, and ongoing shared activity.
This public-source family case study consolidates the related fvckfac3/app and fvckfac3/bond-app repositories without treating their roadmap or product claims as operational proof. The shared product direction is structured partner reflection, conversation, assessment, check-ins, goals, and shared memories, with possible clinician/institutional workflows. All listed service opportunities are proposals, not shipped functionality.
What’s implemented
- Supabase email/password login, session persistence, onboarding, profiles, dashboard, and progress
- Pair-code lookup, partner linking, couple-unit creation, and streak paths
- Assessment resume, answer auto-save, submission, partner-completion checks, couple-result creation, and result-comparison UI
- Daily check-ins with connection score, mood, and appreciation persistence
- Activities/history, learning modules/topics, daily questions, shared bucket list, Memory Lane, image selection, and notification configuration
- AI/analyzer entry points and authenticated insights API
- Subscription plan/cancel/success UI plus Stripe checkout/status/webhook routes
- Clinician/institutional web foundations including invites, requests, audit, and tier/status UI
- SQL schema/indexes/RLS for users, couples, sessions, results, check-ins, and streaks
Technical approach & boundaries
Technology
- Expo 55, React Native 0.83, React 19, TypeScript, Expo Router, React Navigation
- Zustand, React Query, Reanimated/Moti, React Native Paper
- Supabase Auth/Postgres/JS/SSR, AsyncStorage, SQL schema and RLS
- Python FastAPI/Pydantic backend with Supabase, analyzer, authenticated insights, payments, and Stripe webhook routes
- Expo Notifications/Image Picker; Sentry/PostHog packages
- Next.js 14/React 18 clinician web with Tailwind, Supabase SSR, and Vitest
- Separate React/CRA/CRACO web surface with Tailwind/Radix dependencies
Limitations & readiness
- Active build / substantial public implementation; device/emulator setup, Supabase schema and seed data, environment configuration, and backend services remain prerequisites. Production deployment, customers, compliance, clinical validation, and outcomes are unverified.
- No verified deployment, clients, customers, SLA, uptime, telemetry, compliance, clinical validation, or outcomes
- The earlier app repository's web frontend is scaffold-level and its root README is a placeholder
- Some advertised questionnaire banks are truncated; scoring is simplified and compatibility is hard-coded in the earlier source
- A session-select RLS policy may block partner-session access in the earlier source
- Mobile experience requires Expo Go/device/emulator; browser support is limited
- Schema, assessment seed data, env configuration, and backend services are setup prerequisites; screens can be empty without seeds
- AI depends on an external key/model with unverified privacy, cost, availability, and quality controls
- Payment lifecycle, deployment, and cancellation/refund behavior are unverified
- A draft license expressly says HIPAA compliance is not established
Inside the idea.
Public project notes and a separate visual interpretation.
Statusin developmentCategorysystems
Stack
- Expo 55, React Native 0.83, React 19, TypeScript, Expo Router, React Navigation
- Zustand, React Query, Reanimated/Moti, React Native Paper
- Supabase Auth/Postgres/JS/SSR, AsyncStorage, SQL schema and RLS
- Python FastAPI/Pydantic backend with Supabase, analyzer, authenticated insights, payments, and Stripe webhook routes
- Expo Notifications/Image Picker; Sentry/PostHog packages
- Next.js 14/React 18 clinician web with Tailwind, Supabase SSR, and Vitest
- Separate React/CRA/CRACO web surface with Tailwind/Radix dependencies
Implemented notes
- Supabase email/password login, session persistence, onboarding, profiles, dashboard, and progress
- Pair-code lookup, partner linking, couple-unit creation, and streak paths
- Assessment resume, answer auto-save, submission, partner-completion checks, couple-result creation, and result-comparison UI
- Daily check-ins with connection score, mood, and appreciation persistence
- Activities/history, learning modules/topics, daily questions, shared bucket list, Memory Lane, image selection, and notification configuration
- AI/analyzer entry points and authenticated insights API
- Subscription plan/cancel/success UI plus Stripe checkout/status/webhook routes
- Clinician/institutional web foundations including invites, requests, audit, and tier/status UI
- SQL schema/indexes/RLS for users, couples, sessions, results, check-ins, and streaks
Repository links
Conceptual provenance. The alternate view is an original portfolio diagram based only on this public project record. It is not a product screenshot, live data, or a claim about a shipped interface.
BEYOND THE ORIGINAL PROJECT
What this could become for you.
These are proposed client adaptations—not claims that they have already been delivered.
Potential engagements & deliverables
- MVP hardening with complete questionnaires, scoring, tests, seeded Supabase data, and a release candidate
- white-label couples assessment with configurable catalog, branding, pair onboarding, RLS review, and result screens
- coach/clinician companion with consented workspace, progress/cohort views, content library, role model, audit events, exports, and review checklists
- AI integration hardening with validation, redaction/retention policy, fallbacks, evaluation fixtures, metering, and prompt UX
- subscription implementation with Stripe mapping, entitlements, idempotent webhooks, cancellation/refund handling, and QA
- mobile launch readiness with Expo/EAS builds, accessibility/security/privacy review, device QA, crash review, and store assets
- reusable engagement module for Bucket List, Memory Lane, daily questions, notifications, cadence configuration, and analytics events
Related work
- Consolidated public family record: fvckfac3/app is the earlier mobile-MVP/prototype; fvckfac3/bond-app is the broader active build with clinician/institutional foundations.
- No AppArchitect reference is observed.