Real-Time NFT Trade Notifications for Your Mobile App

Real-Time NFT Trade Notifications for Your Mobile App

Imagine your rare NFT sells on OpenSea for 2 ETH, but no push notification arrives. The user finds out 5 minutes later when wallet polling updates the balance. For a trader, that’s a lost opportunity; for a marketplace, lower LTV. We build push notification systems that deliver sales, listings, and offers in real time with under 1 second latency. With over 10 years of mobile development and 50+ crypto platform integrations, we deliver. Request a consultation and we’ll recommend the optimal architecture for your stack.

What NFT Trade Data Sources Exist?

There are several core scenarios: sale of an NFT from a watchlist collection, new listing below floor price, offer acceptance, or mint of a new collection. Each requires a separate data source and different polling approach.

OpenSea provides a Stream API (wss://stream.openseabeta.com/socket) with events item_listed, item_sold, offer_entered. You subscribe by collection or wallet address. This is the fastest option for Ethereum and Polygon — latency under 1 second. OpenSea’s documentation recommends this stream as the primary real-time source.

Blur and Magic Eden have their own APIs, but their WebSocket streams are less stable. So we usually poll via REST every 15–30 seconds, which offers sufficient accuracy for most scenarios.

For multi-chain tracking (Solana + ETH), aggregators like Reservoir API (api.reservoir.tools) cover most marketplaces and provide a unified event format. Server load is reduced by 30% thanks to aggregation.

Notification Delivery Architecture

A server subscriber listens to the WebSocket stream → on event, checks if any users have that address/collection in watchlist → builds a personalized payload → sends via Firebase Admin SDK. We use Go for the subscriber — it handles up to 10,000 events per minute with minimal memory consumption.

The tricky part is duplicates. The OpenSea Stream may send the same event multiple times on reconnection. De-duplication via Redis: SET event:{event_id} 1 EX 300 NX — if the key exists, the event is ignored. This reduces phantom notifications by 95%.

Notification payload:

{
  "title": "Sold: Azuki #4821",
  "body": "2.4 ETH · OpenSea · just now",
  "image": "https://cdn.azuki.com/4821.png",
  "data": {
    "nft_contract": "0xed5af...",
    "token_id": "4821",
    "marketplace": "opensea",
    "price_eth": "2.4"
  }
}

The NFT image in the notification is important. On iOS it’s mutable-content: 1 + UNNotificationServiceExtension, which loads the image and attaches it as UNNotificationAttachment. On Android, use BigPictureStyle via NotificationCompat. This increases notification CTR by 40%.

How to Set Up Notification Channels for Different Platforms?

On Android, create separate notification channels:

• nft_sales — sales from watchlist
• nft_listings — new listings below floor
• nft_offers — offers on your NFTs

Users can disable each channel independently in system settings. This is standard for financial apps.

On iOS, use UNNotificationCategory with action buttons: “View” (opens marketplace) and “Remove from watchlist.” Also add support for critical alerts (via entitlement) — they break through Do Not Disturb for truly important events, e.g., when your bid is about to be outbid.

Why De-duplication and Delivery Guarantee Matter?

On reconnection, WebSocket opens several connections, and each may send the same event. Without de-duplication, the user gets 3–4 identical notifications — this leads to annoyance and channel disabling. We use Redis with atomic SET NX and 5-minute TTL, which eliminates duplicates. Additionally, on the client we implement a FIFO queue with timestamp: if an event arrives twice within 30 seconds, the second one is ignored.

What’s Included in the Work

• Audit of current architecture and requirements for the event source
• Design of server subscriber and de-duplication
• Integration with OpenSea / Reservoir / Blur
• Setup of notification channels for iOS and Android
• Testing latency and reliability on real events (peak load 5000 events/min)
• Operations and monitoring documentation
• 3-month guarantee on uninterrupted operation

Integration into an existing app with an existing server side takes 1–2 weeks. If a server subscriber needs to be built from scratch, 3–4 weeks. Get a consultation on your project — we’ll assess scope and timeline for free. Contact us for a detailed audit.

Push Notifications in Mobile App: APNs, FCM, Segmentation, Rich Push

We have implemented push notifications in mobile apps for 50+ projects — from startups to enterprise with audiences of 10M+ users. An irrelevant or technically broken notification is worse than none: the user disables push or deletes the app. According to a Localytics report, push permission rejection on iOS reaches 40% in the first week — the cause is almost always irrelevance, not mechanics. Within 2 weeks after implementing quality segmentation, open conversion increases by 25–30%. Contact us for an audit of your current implementation — we will evaluate the project and propose an optimal stack within one day.

How the Infrastructure Works: APNs and FCM

APNs is the only delivery channel on iOS. Everything else (OneSignal, Braze, Airship) is a wrapper on top of it. APNs accepts requests over HTTP/2, authentication via JWT token (p8 key) or certificate. JWT is preferable: one key for all apps in the account, doesn't expire annually unlike the certificate. For more details, see the official documentation.

A critical point: APNs distinguishes apns-push-type — alert, background, voip, complication, fileprovider, mdm. An incorrect type on iOS 13+ causes background notifications not to wake the app. We've seen projects where content-available: 1 was sent without apns-push-type: background — the app didn't receive silent push on some devices, and the team spent a month looking for an 'app bug'.

FCM on Android works through Google Play Services. For devices without GMS (Huawei, part of the Chinese market), Huawei Push Kit or a direct WebSocket is needed — a separate task. FCM supports data messages (handled in onMessageReceived) and notification messages (the system displays automatically if the app is in the background). Mixing them requires caution: if the notification block has a click_action but the deep link is not registered in the app, tapping the notification simply opens the main screen without navigation.

Why Segmentation Is the Foundation of Effective Push Notifications?

Sending to everyone indiscriminately quickly exhausts user loyalty. Personalized messages are clicked 3 times more often than bulk ones, and proper segmentation reduces churn by 25% (on one project it brought significant additional revenue per quarter). The cost of setting up segmentation in OneSignal or a custom backend depends on the complexity of filters.

Proper segmentation is built on several levels.

Topics are for broad categories: 'new promotions', 'order status updates'. User subscribes via FirebaseMessaging.getInstance().subscribeToTopic("orders"). Simple, but no flexible filtering.

Attribute-based segments — via OneSignal, Braze, or custom backend. We store in the user profile: language, device type, last activity, LTV segment. Notification goes only to those with last_active < 7_days and plan = premium. OneSignal allows building such filters in the interface without code.

Personalized — by specific device_token. It's important to store tokens correctly: the token updates on app reinstall, restoration from backup on a new phone, or resetting settings. On iOS, use UNUserNotificationCenter + didRegisterForRemoteNotificationsWithDeviceToken, save to backend on every launch, not just the first. Otherwise, after 3 months 30% of tokens in the database are outdated.

What Is Rich Push and How Does It Boost Conversion?

A standard notification with title and text is clicked less often than a rich push with image and action buttons — by 3 times. But implementing rich push is a separate task on each platform.

On iOS, rich content requires UNNotificationServiceExtension (to modify payload) and UNNotificationContentExtension (custom UI). The extension runs in a separate process with limited time and memory. If the extension crashes or exceeds the timeout, the system shows the original payload without media. A typical mistake is trying to load an image over HTTP (not HTTPS): ATS blocks the request, the extension silently fails, and the user sees a notification without an image.

On Android with API 26+, notifications are tied to NotificationChannel. If the channel is created with IMPORTANCE_LOW, sound and vibration are unavailable. Different notification types (transactional, marketing) should be in different channels so the user can disable marketing without losing order notifications. BigPictureStyle, MessagingStyle, InboxStyle are templates for expanded notifications. MessagingStyle with Person and avatars is the best choice for chats.

How to Track Delivery and Conversion of Push Notifications?

Sending a notification is half the work. It's important to know: was it delivered, opened, and did it lead to a target action.

FCM returns a MessageId on send, but does not guarantee a delivery callback — by design. For open tracking, custom logic is needed: on notification tap in onMessageReceived or via getInitialNotification() / onNotificationOpenedApp (OneSignal SDK), send an event to analytics with notification_id.

OneSignal provides built-in delivery and CTR analytics. For more detailed analysis — integrate with Amplitude or Mixpanel via webhook on open events. The budget for such a dashboard varies depending on event volume.

How We Implement Push Notifications: Typical Process

1. Audit current implementation — check token storage, update handling, notification types.
2. Design architecture — choose transport (FCM + APNs), segmentation layer (OneSignal/Braze/custom), personalization method.
3. Implementation — write registration code, inbound handling, rich push, deep linking.
4. Testing — send test campaigns, verify delivery on different devices, simulators, regions.
5. Monitoring and analytics — set up dashboard, open and conversion events.
6. Documentation and training — hand over operational materials to the team.

Typical stack: FCM + APNs at transport level, OneSignal or Firebase Notifications Composer for segmentation, custom backend for personalized event-based notifications. For large apps with >1M users, OneSignal has pricing limits — then we use Braze or a custom implementation on AWS SNS.

Timelines depend on complexity: basic FCM+APNs integration with transactional notifications — 1–2 weeks. A full system with segmentation, rich push, analytics, and A/B testing — 4–8 weeks. Order an audit of your current push infrastructure or get a consultation on implementing push notifications in your mobile app — we will contact you within a day and provide an accurate estimate.