การจัดการการแจ้งเตือนขณะอยู่เบื้องหน้าและเบื้องหลัง

Your app can be in three states when a notification arrives: foreground (app is open and visible), background (app is running but not visible), or killed (app is not running at all). Each state has different handling requirements and different APIs to use.

Understanding which state applies is critical because the OS delivers notifications differently in each case and the user's tap response routes through different code paths depending on the app state at the time they tap.

Notifications.addNotificationReceivedListener fires when a notification arrives while the app is in the foreground. By default, notifications do not show a banner or sound when the app is already open — you must handle them in-app. The listener receives the full notification object including all content and data payload.

Use this to show in-app banners, update UI (e.g., refresh a chat thread), or play a custom sound — giving users the same experience as if the notification had arrived while the app was in the background.

Notifications.addNotificationResponseReceivedListener fires when the user taps a notification, regardless of whether the app was in the background or killed. The listener receives a response object that contains the notification, the action identifier (which button was tapped), and any user text input.

Use this to navigate to the relevant screen based on the notification's data payload. This is the most important notification handler because it drives the deep navigation behavior users expect when tapping a notification.

The data field in a push notification is your app's contract with itself — it determines what happens when the notification is tapped. Design a consistent schema that includes the destination screen name and all parameters that screen needs.

A well-designed data payload allows any notification to navigate to precisely the right screen with the right content without any guessing. Use type-safe constants for action types to prevent typos causing silent navigation failures.

By default in expo-notifications, notifications received while the app is in the foreground are silent (no banner, no sound). Control this with the setNotificationHandler set at app startup. The handler function is async — you can even make an API call to decide whether to show a notification based on user preferences.

Return shouldShowAlert: true to show the system banner even when the app is open. This is appropriate for notifications from other users (messages) but often not for your own app's activity notifications.

On iOS, you can configure background notifications (silent push notifications) that wake the app in the background to fetch data without showing a banner. Set content-available: 1 in the APNs payload. The app gets a short window (~30 seconds) to fetch data.

Background fetch is useful for pre-loading content before the user opens the app from a notification, ensuring the screen is ready instantly. Handle it with expo-notifications' background notification tasks using Expo's task manager.

Notifications can include action buttons that let users respond without opening the app. For example, a message notification might have 'Reply' and 'Mark Read' buttons. Configure categories with Notifications.setNotificationCategoryAsync and reference the category in your push payload.

The tap response listener's response.actionIdentifier tells you which button was tapped. For text input actions, response.userText contains what the user typed directly from the notification.

The badge count is the red number on your iOS app icon. Set it by including a badge number in your push payload, or update it from within the app using Notifications.setBadgeCountAsync(count). Reduce the badge when the user reads notifications or visits the relevant screen.

A common pattern: server sets badge to unread count when sending a push, and app calls setBadgeCountAsync(0) when the user opens the inbox. Always fetch the true unread count from your server rather than incrementing a local counter, since multiple devices must stay in sync.

After reading a notification in-app, you should dismiss the corresponding notification from the notification center so it doesn't mislead the user. Use Notifications.dismissNotificationAsync(identifier) for a specific notification or Notifications.dismissAllNotificationsAsync() to clear all.

Call dismiss in the notification response handler after navigating to the relevant screen, or in useEffect on the target screen when it mounts. The notification identifier is available in the response object.

Retrieve all currently displayed notifications in the notification center with Notifications.getPresentedNotificationsAsync(). Use this on app launch to handle any notifications the user hasn't tapped yet, or to display an unread count badge based on actual notification center contents.

On app foreground, you can also loop through pending notifications and dismiss ones that are now stale (e.g., expired promotions or events that have passed).

A production-ready notification setup combines all the pieces: set the handler at startup, register listeners in a custom hook, and wire them to navigation. The custom hook handles both foreground (show banner, update state) and tap responses (navigate), and always cleans up listeners on unmount.

This architecture keeps notification logic centralized, testable, and separate from individual screen components.

In this lesson you learned: addNotificationReceivedListener handles notifications arriving while the app is in the foreground, addNotificationResponseReceivedListener handles user taps on notifications from any app state and should navigate to the relevant screen, and action buttons with categories enable users to reply or take actions directly from the notification without opening the app. Next up we configure notification channels and add rich content like images and action buttons.