Onboarding Screen

Flow

• User provides first/last name, gender, DOB, status (initiated/ashraya/missionary/volunteer).
• Validations enforce minimum length and required fields; DOB cannot be in the future.
• Maps selections to ashraya level IDs and appGroup (FTM/VOL/none).

Logic & Mechanism

• Status toggles set internal flags that feed into target calculation later.
• Age calculation uses current date to derive ageYears.

Error Handling

• Inline error strings for empty/short fields; Cupertino dialog for missing/invalid data.
• DOB future check blocks continuation.

How It Works

• On continue, builds a DevoteeDraft carrying basic profile/state for next screens.
• Spiritual status maps: Initiated → Initiated targets; Ashraya levels → level-specific targets; Volunteer → volunteer targets; otherwise adult default.
• Kid/youth handling: age < 15 gets kids default; youth (≤18) in Ashraya get kid Ashraya targets (Shraddhavan/Sevak) with kirtan minutes.

Contact & Profile Details

Flow

• Collects email, phone/WhatsApp, address, education, course, university, graduation year, designation, company.
• Country selection seeds dial code; user can override or remove it.
• University picker shows a searchable bottom sheet; “Other” allows custom entry.

Logic & Mechanism

• Phone formatter applies masks per country but respects custom “+” input.
• University list filtered client-side; helper text shown inside the sheet.

Error Handling

• Required fields set inline errors; ZIP/state/country sanity checks.
• Phone digit length checked against country expectation.

How It Works

• Builds DevoteeDraft with contact/education data; passes forward to mentor/credentials flows.

Mentor & Children Screen

Flow

• Select mentor/guide (from Supabase mentors table, ordered by sort_order).
• Add children/dependents with name, relation, gender, DOB, grade, Ashraya participation.
• Toggle child consent for under-13 entries; optional Krishna Life flag maps appGroup.

Logic & Mechanism

• Mentor/guide options fetched from Supabase; list filtered into roles.
• Family members stored in DevoteeDraft JSON; Ashraya level and partOfAshraya influence targets.
• Kids/youth (≤18) get kid targets; Ashraya kids get kid Ashraya targets (includes kirtan minutes).
• Labeling updated to “Children” with “Add child profile.”

Error Handling

• Validation for relation/gender consistency, DOB not future, required fields per member.
• Consent required for under-13; dialog prompts on incomplete family rows.

How It Works

• Final DevoteeDraft carries mentor/guide IDs, family JSON (with consent if under 13), and appGroup.
• Kid targets: kids default (2 rounds, 20m reading/hearing, 15m kirtan), kid Ashraya Shraddhavan (2 rounds, 15m reading/hearing, 10m kirtan), kid Ashraya Sevak (4 rounds, 20m reading/hearing, 15m kirtan).
• Youth Ashraya (≤18) with levels “shraddhavan”/“sevak” also receive kid Ashraya targets to include kirtan.
• Non-Ashraya kids (under 15) use kids default targets (2 rounds, 20m reading/hearing, 15m kirtan, no seva/month). Adults not in Ashraya/initiated use the adult default (4 rounds, 30m reading/hearing, 6h seva/month). Volunteers use volunteer targets (0 rounds, 10m read/hear, 12h seva/month).

Home (Practice & Overview)

Flow

• Profiles: primary + dependents (from family JSON; fallback to parent_id dependents if JSON empty).
• Practice tab: Japa (toggle or time), reading/hearing, kirtan, seva, arati/guru-puja.
• Overview tab: progress rings for rounds, association, seva; calendar tab loads Vaishnava days.

Logic & Mechanism

• Targets resolved via getTargetsForPerson: initiated → initiated targets; youth (≤18) Ashraya → kid Ashraya targets; non-Ashraya kids → kids default.
• Japa input: toggle rounds for youth/adult Shraddhavan/Sevak/Sadhak (and kids default); time entry for others.
• Svadhyaya progress uses reading + hearing + kirtan (capped to target for OR-style sources like kids/default/ashraya).
• Seva services loaded from Supabase table `seva_services` (active, ordered by sort_order); defaults used if fetch fails.
• Spiritual status targets: Initiated (16 rounds, 30m read/hear, 24h seva/month), Ashraya levels (Shraddhavan 1 round /15m read/hear /2h seva; Sevak 4 rounds /20m read/hear /4h seva; Sadhak 8 rounds /30m read/hear /8h seva; Vandana 12 rounds /30m read/hear /12h seva; Upasak 16 rounds /45m read/hear /16h seva; Charanashraya 16 rounds /60m read/hear /20h seva; Full-time missionary 16 rounds /60m read/hear /40h seva).
• Volunteer targets: 0 rounds, 10m read/hear, 12h seva/month. Adult default: 4 rounds, 30m read/hear, 6h seva/month. Initiated always uses initiated targets.

Error Handling

• Mounted checks added around async calendar/seva fetches to avoid setState after dispose.
• Supabase fetch failures fall back to local defaults (calendar sample, default seva list).

How It Works

• Daily tracking saved per profile; progress rings average rounds/association/seva.
• Calendar notifications scheduled from fetched or fallback data.

Settings & TOTP MFA

Flow

• Notifications toggle, legal links, about/support, sign out.
• TOTP: enroll → show QR + URI + secret → verify code → enable; disable unenrolls factor.

Logic & Mechanism

• Before enrolling, removes unverified TOTP factors and uses unique friendly names to avoid conflicts.
• Shares TOTP URI via link copy/key copy/share (with sharePositionOrigin for iPad).

Error Handling

• MFA errors surfaced via SnackBar; specific conflict messaging for existing TOTP.
• Share failures handled with SnackBar; copy actions confirm via SnackBar.

How It Works

• Uses Supabase MFA APIs (enroll, challenge, verify, list, unenroll).
• Legal links point to hosted Privacy/Terms pages.