Skip to content
Ritesh FirodiyaGet in touch

Work / Plan-Kid / Wiki / Concepts

product-boundary

Conceptcanonicalverified 2026-07-27

CONCEPT.PRODUCT-BOUNDARY

Product boundary

slug: pattaya repo_shape: single-app (planned; not yet code)

Included in scope

  • mobile app experience for iOS + Android (React Native + Expo, planned Phase 3)
  • product artifacts in .context/wiki/
  • design prototypes in .context/designs/
  • India-first, English + Hindi; global expansion post product-market fit

Excluded from scope

  • web app (mobile-only)
  • admin dashboard, doctor-facing portal (Year 2+)
  • community / forum / UGC surfaces (business trap — see [[ai-not-community]])
  • doctor / product marketplace (Momspresso failure — see [[2026-07-27-no-community-no-marketplace]])
  • ads (breaks medical-adjacent trust)
  • diagnosis, dosage, or clinical decisions (see [[no-medical-advice]])
  • self-serve solo mode as a first-class experience (see [[couples-first]])
  • filing, form-submission, or provider-integration surfaces
  • app store, marketing landing, or blog (Year 2+)

Vocabulary

  • Household — the billing entity. One paid seat covers both partners.
  • Partner — an individual user account belonging to a Household.
  • Stage — the current life-cycle position: pre-decision · trying · pregnancy · postpartum · parenting.
  • Pillar — one of the four product surfaces: Knowledge · Journal · Motivation · Tracking.
  • Card — a single unit of curated knowledge content.
  • Ritual — the weekly 5-minute in-app couple reflection.
  • Briefing — the AI-generated daily home surface for the household.
  • Indian context — a toggle available on every Knowledge Card to swap medical guidance for garbhsanskar / Ayurveda / joint-family / regional-diet context.

Every project of mine is written down like this.

Read the résumé