ramadhan sjamsani
a7a2a32d27
- 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>
16 lines
763 B
Markdown
16 lines
763 B
Markdown
---
|
|
name: Client App Context
|
|
description: Stack, purpose, and API conventions for the Halo Bestie client Flutter app
|
|
type: 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.
|