Files

ramadhan sjamsani a7a2a32d27 Phase 1 scaffold: auth for all apps

- Backend: Fastify with two listeners (public + internal), routes, services, DB migration + seed
- client_app: Flutter with BLoC, all auth screens (welcome, display name, register, OTP, force-register)
- mitra_app: Flutter with BLoC, OTP-only login
- control_center: React + Vite, email/password login, mitra/user management, anonymity settings
- Docs: phase1 plan, API contract, client app mockup
- CLAUDE.md and shared memory for all subprojects

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-05 10:08:42 +08:00

1011 B

Raw Blame History

Halo Bestie — Mitra App

Flutter mobile application for mental health professionals (mitra/partners).

See root CLAUDE.md for full project context and architectural decisions.

Stack

Framework: Flutter (iOS + Android)
Auth: Firebase Auth — Google Sign-In, Apple Sign-In, Phone OTP
- Fully native UI — no WebView, no Firebase-branded screens
- Use firebase_auth + google_sign_in packages
API: Calls public Fastify backend (/api/mitra/ and /api/shared/ routes)

Key Concepts

Users are mitra — trained mental health professionals
Core flow: register + credential verification → set availability → accept sessions → chat with client → receive payment
Mitra accounts require approval from control center before going live

Conventions

Never call /api/client/ or /internal/ routes from this app
All API calls must include Firebase JWT token in Authorization header
Mitra role must be verified server-side on every relevant request

1011 B Raw Blame History

Halo Bestie — Mitra App

Stack

Key Concepts

Conventions

1011 B

Raw Blame History