Push Notifications & Real-Time Alerts

​

Overview

• Fresh lead inquiries assigned by managers or ingested via Meta and Google Ads
• Escalated discount approvals and pricing waivers
• Daily morning follow-up call reminders
• Confirmed unit bookings and token deposit receipts
• Direct mentions and priority team chat messages

​

Notification Pipeline Architecture

​

Push Token Registration Lifecycle

1. Permission Request: Expo Notifications requests notification runtime permissions (POST_NOTIFICATIONS on Android 13+).
2. Token Generation: Expo registers with Firebase and retrieves a unique device push token.
3. Database Association: The mobile client sends the token to PATCH /api/users/push-token, saving it in PostgreSQL (User.pushToken).
4. Targeted Dispatch: Whenever system events affect that user, the BullMQ worker targets their specific hardware token.

​

Trigger Events & Notification Payloads

​

In-App Notification Center

// Inside apps/mobile/app/(dashboard)/_layout.tsx
<Pressable
  onPress={() => {
    Haptics.impactAsync(Haptics.ImpactFeedbackStyle.Light);
    setUnreadCount(0);
    router.push('/(dashboard)/notifications');
  }}
  className="w-9 h-9 rounded-xl bg-slate-50 items-center justify-center border border-slate-200/80 mr-2.5 active:scale-95 relative"
>
  <Bell size={18} color="#0f172a" />
  {unreadCount > 0 && (
    <View className="absolute -top-1 -right-1 bg-rose-600 rounded-full min-w-[16px] h-4 px-1 items-center justify-center border border-white">
      <Text className="text-[9px] font-black text-white">
        {unreadCount > 99 ? '99+' : unreadCount}
      </Text>
    </View>
  )}
</Pressable>

• Live Counter: Unread badge count increments in real time via Socket.IO events (new_notification).
• Interactive Deep Linking: Tapping a notification navigates directly to the associated lead profile, booking agreement, or approval sheet.

​

Build Configuration: Firebase & FCM v1

1. Firebase Project: Register an Android application under the package name com.anonymous.mobile (configured in apps/mobile/app.json).
2. Download File: Download google-services.json and save it to the apps/mobile/ root directory.
3. Expo Dashboard Credentials: In expo.dev, navigate to your project -> Credentials -> Android -> Push Credentials and upload your Google Service Account private key JSON for FCM v1 delivery.
4. Compile Build: Run npx expo run:android or EAS build to embed the configuration into the native APK.