Skip to content
Longport Whale
Message Push

Choose a Message-push Option

Compare Whale-managed push with Broker-owned push by path, responsibility, and integration steps

Whale SDK supports two message-delivery options. In both, Broker App ultimately receives the standard message body and passes it to Whale SDK. The difference is whether Whale delivers directly through cloud-push channels or first forwards the message to Broker Server.

Item Whale-managed push Broker-owned push
Path Whale → cloud push → device → Broker App Whale → Broker Server → Broker channel → Broker App
Broker Server work None Build receiving and downstream-distribution services
Channel credentials Broker securely provides them to Whale Broker retains them
Distribution control Whale-configured channels and policies Broker decides whether and how to notify
Best fit Lower integration cost and faster delivery Existing message center or custom distribution control

Option 1: Whale-managed push

flowchart LR
  A[Whale creates a business message] --> B[Whale cloud-push service]
  B --> C[Apple APNs]
  B --> D[Android vendor channels]
  C --> E[Broker App]
  D --> E
  E --> F[Whale SDK message handling]
Advantage

Lower Broker integration cost and no message-forwarding service to build.

Consideration

Broker must securely provide channel configuration: iOS APNs credentials and Android vendor App IDs, keys, or secrets.

Collect channel information

Broker prepares UAT and production details with the Push-channel information form, explicitly marking unused channels as none.

Configure Whale cloud push

The Whale project team configures the confirmed channel information in the corresponding environment.

Integrate Broker App

Broker App integrates the Whale SDK message API and tests notification permission, device token, foreground/background receipt, and notification navigation.

Option 2: Broker-owned push

flowchart LR
  A[Whale creates a business message] --> B[Broker Server endpoint]
  B --> C[Broker message center]
  C --> D[Broker push channel]
  D --> E[Broker App]
  E -->|Standard message body| F[Whale SDK message handling]
Advantage

Whale does not manage downstream channels. Broker controls templates, Customer preferences, whether to notify, and distribution policy.

Consideration

Broker Server must receive and distribute messages. Authentication, idempotency, durable storage, and monitoring are agreed per project.

Build the receiving endpoint

Broker Server builds an HTTPS endpoint reachable by Whale.

Configure forwarding

Broker gives the Whale project team the UAT and production endpoints, authentication method, network requirements, and contacts.

Test the server path

Follow Broker-owned push channels to test requests, responses, idempotency, and failures.

Integrate Broker App

Broker App passes the final standard message to Whale SDK and implements safe navigation and compatibility behavior.

Whale Docs