Urban Airship

This section will guide you through the essentials to get For Apps integrated with Urban Airship (UA).

1. Overview

In Loco For Apps depends on two processes in order to deliver push notifications through the UA platform: registration and message sending.

Registration

The registration step serves to create an endpoint between the For Apps backend and your user's device, so For Apps can send push notifications to the device through Urban Airship. This endpoint is represented by a Channel ID, generated and refreshed by Urban Airship. This step will guarantee that For Apps always has the latest Channel ID.

The registration step takes place when the app opens. The Urban Airship SDK registers itself with the Urban Airship backend, thus generating a Channel ID. This Channel ID should be passed to the For Apps SDK, which updates the For Apps Backend.

The step above is repeated every time a Channel ID is refreshed by UA.

Message Sending

The message sending step includes the visit detection, visit processing and sending the push notification. The For Apps SDK detects that a user is visiting a point of interest and communicates the For Apps API. The For Apps API then enhances the location information and checks if the push notification should be sent. Then the For Apps API, using the Channel ID, publishes notifications via Urban Airship and the message is delivered to the user.


What's Next

UA Setup

Urban Airship


This section will guide you through the essentials to get For Apps integrated with Urban Airship (UA).

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.