UnifiedPush Server
  • Documentation
  • GitHub
  • Help

›Introduction

Introduction

  • Overview
  • Useful Terminology
  • Push Notifications
  • How the UnifiedPush Server works
  • Use-cases and scenarios

Running Unified Push

  • Running Unified Push
  • JMS Broker Configuration

Configuring Variants

  • Getting Started
  • Android Variant
  • iOS Variant
  • WebPush Variant

Configuring Clients

  • Android Client
  • iOS Client
  • Webpush Client
  • React Native Client
  • Cordova Client

Unified Push Server SDK

  • Java Sender API
  • Node Sender API
  • RESTful Sender API

Maintaining Unified Push

  • Maintaining Unified Push

Use-cases and scenarios

Different use-cases and scenarios are supported. Below are a few to give an idea how the UnifiedPush Server can be used:

  • MyWarehouseInc-backend can send notification messages to different groups (e.g. discounts for only iOS (or only Android) users)
  • MyInsuranceCorp-backend can send “notification messages” to different variants of its mobile Applications:
    • App for the Customers
    • App for the employed Sales Agents
  • Publishing Company:
    • MyPublishing-Company-backend sends update “notification messages” to all of its apps (free and premium - regardless of the mobile OS)
    • Targeting: Sending push messages to different groups of users. For instance, availability of “advanced content” is only notified to the paying customers (e.g. those that run the premium app).
  • A company has different backends (small/simple apps for different tasks) - and these different backends could be able to reach all (or some) of the company’s mobile apps.
← How the UnifiedPush Server worksRunning Unified Push →
Docs
Getting Started
Community
HelpAeroGear mailing listStack Overflow
Social
UnifiedPush Server
Follow @aerogears
Copyright © 2020 the AeroGear team