尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Paire — dating app where women set the rules (www.paire.in)
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗"Find your Paire." Live at paire.in. Formerly Chitthi, and before that the working name Muse; internal IDs (com.muse.app, Firebase muse-352ba, folder names) are unchanged.
Paire is a dating app for adult men and women (18+), built for India: women set the rules, men get a fair chance. It is open to members across India. Members sign up in two quick steps and pick interests (music, film, craft…). Profile-based vibe ranking sorts people whose preferences match their own and explains shared choices. They can explore photo cards or Vibe-first cards, see who liked them for free, and chat after a mutual like, with optional AI icebreakers.
Also in the app:
docs/ccavenue.md), which replaces the earlier direct-UPI and Razorpay checkouts; the Android app uses Play billing via RevenueCat. Each is behind its own switch (docs/launch-web.md).docs/presence-and-paid-chat.md.The public name is still to be decided; see docs/product/brand-shortlist.md. The private website preview is https://muse-delhi-ncr.soundlemon8.chatgpt.site — review build, with public launch/provider/legal setup pending. Build and browser QA: docs/web-preview.md. Latest evidence and limits: docs/qa-2026-10-10.md.
| Part | Where | Stack |
|---|---|---|
| Mobile app | apps/muse-mobile | Expo SDK 54, React Native 0.81, Tamagui, React Navigation, Zustand, TanStack Query |
| Website + browser app (Vercel) | apps/web, vercel.json | Landing page, legal pages and the Expo web export at /app/ (docs/vercel.md) |
| Older Sites preview | apps/muse-site | Owner-private preview (superseded by apps/web) |
| Backend | firebase/functions | Cloud Functions (Node 22): discovery, swipes/matching, safety, account deletion, push |
| Security rules | firebase/rules | Firestore + Storage rules, with tests |
| Legal pages | firebase/hosting | Privacy policy, terms, guidelines, account deletion (Firebase Hosting) |
| E2E flows | e2e | Maestro |
The app and the functions are standalone npm projects, each with its own lockfile. The root folder has no dependencies.
./scripts/bootstrap-macos.sh # one-time toolchain (watchman, firebase-tools, maestro…)
(cd apps/muse-mobile && npm ci)
(cd firebase/functions && npm ci)
(cd firebase && npm ci) # rules test tooling
cp apps/muse-mobile/.env.example apps/muse-mobile/.env
Android builds need JDK 17 (JAVA_HOME) and the Android SDK (ANDROID_HOME).
npm --prefix firebase/functions run build
firebase emulators:start --project demo-muse # auth, firestore, functions, storage
npm --prefix firebase/functions run seed:emulator # demo members, password Password123!
cd apps/muse-mobile && npx expo run:android
Seeded logins: [email protected], [email protected] (already matched), [email protected], [email protected], [email protected], and [email protected] (no profile yet).
The android/ and ios/ folders are generated from app.config.js (npx expo prebuild). Change native settings in app.config.js or a config plugin in plugins/, never by hand.
Share the app with friends on their own phones, with no Firebase bill: your Mac runs the backend and a free Cloudflare tunnel makes it reachable.
./scripts/android/build-test-apk.sh # "Muse Test" app → dist/Muse-Test.apk
./scripts/test-backend.sh # prints an invite link to share
See docs/test-backend.md (what testers do, resetting passwords, limits, and how the gateway keeps the emulators safe to expose).
./scripts/verify.sh # lint, typecheck, unit, rules and functions end-to-end tests
E2E_PLATFORM=android ./scripts/verify.sh # plus Maestro UI flows on an emulator
See docs/testing.md.
./scripts/release-preflight.sh lists what is missing; docs/RELEASE.md walks through Firebase, signing, building the .aab and Play Console.
docs/product/india-v2-plan.md: India v2 problems → solutions → pricing (current product plan)docs/launch-web.md: web launch order and every environment variable (Firebase, Razorpay, Vercel)docs/presence-and-paid-chat.md: presence, the paid-chat gate, Unlimited Chat payments, switches, migration and rolloutdocs/ccavenue.md: CCAvenue payments (Unlimited Chat and Plus): flow, keys, switches, rollout and testsdocs/vercel.md: deploying the web app on Verceldocs/product/delhi-ncr-direction.md: research, issues/solutions, naming, safety/verification, matching, pricing, design and launch requirements.docs/architecture.md: data model, backend flows, securitydocs/RELEASE.md: Google Play release playbookdocs/safety.md: moderation and trust & safety operationsdocs/testing.md: test suites and how to run themdocs/test-backend.md: the free test server for your groupdocs/design-system.md: themes, type and componentsdocs/PRODUCT_BACKLOG.md: what's next and open decisionsdocs/product/market-strategy.md: India-first market review, launch plan and getting trafficdocs/product/costs.md: Play and Firebase costs, and developer-account optionsdocs/product/duos-prd.md: Duos (double dates with a friend) PRDdocs/product/naming.md: app name reviewPROJECT_STATE.md: what's done and what needs you; FIX_LOG.md: change historyProduction trust, billing and AI setup: integration guide. These integrations require provider/store configuration and live QA before launch.