Skip to main content

Mobile API coverage

Updated: 2026-05-24

This file is the current mobile/API integration snapshot. Older audit files in docs/ are historical unless they have a newer date.

Wired to Golden Lotus Shop API​

  • Password auth, registration, password reset, logout, profile, and lotusMobileAuthConfig.
  • Home CMS: banners, events, articles, service sections.
  • Branch list and branch detail/map content.
  • Spa services, booking form options, booking availability, create booking, next booking, and booking history.
  • Membership tier, point summary, and point ledger.
  • Voucher packages, my voucher redemptions, redeem voucher, and signed QR payload.
  • Event registration.
  • Notification inbox, mark read, and mark all read.
  • Push device registration via registerLotusDevice; mobile can register Expo token or Android native FCM token depending on EXPO_PUBLIC_PUSH_TOKEN_PROVIDER.
  • Referral summary.
  • Social feed, my social profile, and create social post.
  • Profile payment methods.
  • App settings/privacy preferences.
  • Lucky Wheel active wheel, my state, spin history, and spin mutation.

Mobile screens currently backed by API clients​

  • Auth/login/register/forgot password.
  • Home, news/articles, events and CMS content.
  • Services and booking flow, including grouped service picker display.
  • Booking history/detail.
  • Membership rank, points, point history and member QR screen.
  • Voucher packages, voucher wallet, QR payload and redemption flow.
  • Branch map/list.
  • Profile edit, app preferences, payment methods and referral summary.
  • Notifications inbox and deep-link navigation.
  • Social feed/create/profile.
  • Lucky Wheel route /lucky-wheel.

Remaining non-code/provider work​

  • Google/Apple login and OTP remain disabled by lotusMobileAuthConfig; mobile now hides the placeholder social buttons when backend reports supportsSocialLogin: false.
  • Push token capture is implemented in the app, but real device/provider UAT is still required for both Expo token and Android native FCM token paths.
  • Backend push delivery still depends on real Firebase/Expo credentials being configured in deployment env.
  • QR screen now calls the signed QR payload API and uses react-native-qrcode-svg. Staff/POS scanner UAT is still required.
  • Payment methods are read from backend. Adding a real card/wallet method still needs payment provider tokenization UI and gateway config.
  • Provider channels requested by business but not production-ready end-to-end: Google/Apple social auth, SMS OTP provider, payment gateway, Zalo/Viber/WhatsApp/Kakao campaign delivery.
  • Large lists and campaign/audience operations need UAT with real data volumes; some backend list filters are intentionally simple for MVP/UAT.