JPush notifications
Use JPush to send notifications to your Android and iOS applications. NextAppMarket provides the credentials assigned to your app; your team integrates the SDK, registers devices, and controls the experience after a notification is received or opened.
Follow the integration path
- Confirm the assigned credentials.
- Integrate the Android or iOS SDK.
- Register one device and send your first notification.
- Bind devices to users.
- Add notification navigation and test delivery across app states.
Understand the identifiers
| Identifier | Meaning |
|---|---|
| AppKey | The JPush application your SDK and sender use. |
| MasterSecret | The server credential used to authorize JPush REST API calls. |
| Registration ID | The identifier returned for a registered app installation. |
| Alias | An application-defined targeting value, often used to group a user's devices. |
| Tag | An application-defined label used to select a group of devices. |
| Message ID | The reference returned for a push request. |
An AppKey identifies the application; it does not identify a signed-in customer. Keep your own device-to-user association and refresh it when the login state changes.
Choose what to send
A notification is intended for user-visible delivery. A custom message is data handled by your application. Their delivery and presentation behavior differ across platforms and app states. Begin with a visible notification to one registration ID before adding audience rules or custom-message handling.
A successful push request means the service accepted it. Device delivery, display, and opening are later outcomes. Your application's own data remains the source of truth when the customer opens the notification.
Reference: JPush product documentation.