Phere

Har Rupaya, Har Rishta.

Phere is a mobile-first wedding finance and planning app for Indian families. It turns scattered WhatsApp messages, notebooks, receipts, and Excel files into one shared digital khata for expenses, shagun, lena-dena, saman, vendors, guests, RSVP, reports, and AI-assisted entry.

Product Snapshot

Area	Detail
Product	Indian wedding expense tracker and planning PWA
Users	Families managing wedding budgets across multiple people and payment sources
Core promise	One dashboard. One truth. Works offline. Syncs when signed in.
Current version	3.0.0
Platforms	Web PWA, Capacitor Android, Capacitor iOS

Tech Stack

Layer	Technology	Purpose
App shell	React 18 + Vite	Mobile-first PWA shell and lazy-loaded feature modules
Styling	Tailwind CSS 4 + CSS variables	Modern Heritage design system and theme tokens
State	React state + Zustand	Main app state in Phere.jsx, smaller shared settings store
Storage	window.storage + localStorage	Offline-first persistence
Cloud	Supabase	Auth, Postgres, RLS, JSONB data, realtime, edge functions
AI	Groq through Supabase Edge Functions	Natural language parsing and assistant flows
OCR	Tesseract.js + local helpers	Receipt scanning support
Reports	xlsx, jsPDF, html2canvas, Recharts	Exports, print flows, analytics
Mobile	Capacitor	Android and iOS wrappers

What Phere Does

• Tracks wedding expenses with category, vendor, status, payment mode, source, due date, receipts, installments, and invoice-style records.
• Records shagun, lena-dena, vendors, guests, RSVP, saman lists, payment sources, wedding functions, and reports.
• Supports offline-first usage through local storage, with optional Supabase auth, cloud persistence, realtime family sync, and recovery flows.
• Uses AI for natural language entry such as 50000 mandap ka advance diya aaj.
• Uses OCR helpers for receipt scanning and report/export flows for PDF, Excel, and WhatsApp sharing.
• Uses a Modern Heritage UI direction: deep maroon, champagne gold, warm cream, readable finance-first layouts, and mobile-first interactions.

Product Map

Phere should feel warm enough for a wedding product and precise enough for money management. The UI favors fast entry, strong financial status visibility, clear pending states, and family-friendly language.

Architecture

Phere is intentionally client-heavy. The app works locally first, then uses Supabase as an optional cloud layer for authentication, storage, realtime sync, row-level security, and edge functions.

Feature Modules

Module	Purpose
Dashboard	Budget summary, wedding progress, financial overview, shortcuts
Kharcha	Expense capture, receipts, OCR, installments, vendors, payment status
Shagun	Gifts and cash received, relationship metadata, side tracking
Lena-Dena	Receivables and payables, settlement history, reminders, aging
Saman	Shopping lists, item status, assignees, conversion to expenses
Vendors	Contacts, ratings, payment terms, linked invoice history
Guests + RSVP	Guest list, invite flows, public RSVP route
Payment Sources	Cash, bank, UPI, card, gold, loan, and other balances
Reports	PDF, Excel, WhatsApp, charts, and printable summaries
AI Assistant	Natural language entry and query flows
Pandit AI	Wedding ritual and tradition assistant
Settings	Profile, members, categories, functions, theme, backup, legal

Repository Structure

Shaadikhata/
|-- Phere.jsx
|-- src/
|   |-- pages/
|   |-- components/
|   |-- hooks/
|   |-- lib/
|   |-- context/
|   `-- i18n/
|-- supabase/
|   |-- migrations/
|   `-- functions/
|-- public/
|-- docs/
|-- android/
`-- ios/

Local Setup

git clone https://github.com/BAKUGOS1/Phere.git
cd Phere
npm install
cp .env.example .env
npm run dev

The app can run without Supabase credentials for local UI work. It falls back to local storage and skips cloud-only flows.

Environment

Frontend .env:

VITE_SUPABASE_URL=https://your-project.supabase.co
VITE_SUPABASE_ANON_KEY=your_anon_key_here

Supabase Edge Function secrets:

GROQ_API_KEY=your_groq_key
RESEND_API_KEY=your_resend_key

Do not put provider secrets in frontend VITE_ variables. Anything prefixed with VITE_ is bundled into the browser.

Development Commands

Command	Purpose
npm run dev	Start the Vite dev server
npm run build	Build production assets
npm run preview	Preview the production build locally
npm run cap:sync	Sync web assets into Capacitor projects
npm run cap:android	Open Android project
npm run cap:ios	Open iOS project
npm run cap:build	Build web assets and sync Capacitor

Deployment

1. Create the Supabase project.
2. Apply supabase/schema.sql.
3. Apply migrations in order from supabase/migrations/.
4. Make sure supabase/migrations/004_family_sharing_setup_repair.sql is included for family-sharing projects and older production databases.
5. Set Supabase Edge Function secrets for Groq and Resend.
6. Deploy Edge Functions:

supabase functions deploy groq-proxy
supabase functions deploy pandit-ai
supabase functions deploy notify-feedback
supabase functions deploy send-email

7. Deploy the frontend to Vercel or Netlify with VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY.

See DEPLOYMENT_GUIDE.md for the detailed production walkthrough.

Fresh Feature Ideas

• Shared family approvals for large payments and high-risk edits.
• Vendor booking timeline with due reminders and document uploads.
• Wedding day command center with live pending checklist and settlement queue.
• Smart budget suggestions based on category burn and remaining functions.
• Post-wedding archive mode with final ledger, exports, and keepsake snapshot.
• Region packs for rituals, checklist templates, and invitation defaults.

Documentation

Document	Purpose
Architecture	Current technical architecture and engineering decisions
Roadmap	Shipped work, near-term priorities, and fresh feature ideas
Integrations	Active integrations and future-compatible options
Deployment Guide	Production deployment and operational checklist

License

MIT. Use it, fork it, adapt it for your own family wedding, and keep the money trail clear.