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

763 B

name, description, type
name description type
Client App Context Stack, purpose, and API conventions for the Halo Bestie client Flutter app project

Flutter mobile app (iOS + Android) for end users seeking mental health support.

Stack: Flutter, Firebase Auth (firebase_auth + google_sign_in), Xendit (payments)

Auth: Google Sign-In (native), Apple Sign-In (native), Phone OTP — fully native, no WebView, no Firebase-branded screens. JWT sent as Authorization: Bearer on every API call.

API: Calls /api/client/ and /api/shared/ routes only. Never call /api/mitra/ or /internal/.

Domain: Client = user seeking mental health support. Flow: register → match with mitra → book session → chat → pay. Trial period available for new users.