Make sure the following guides have been completed before continuing with this article:
Urban Airship provides multiple SDK libraries for a variety of platforms. These libraries are required in order to properly integrate Urban Airship features within your app such as receiving push notifications, adding or removing audience segmentation data, and uploading device analytic information.
Our library of SDK integration guides provide documentation for the following supported platforms:
To stay on top of the latest SDK releases, you can sign up for Web Push Notifications via our docs. Here is the icon you can click to receive these notifications:
Below are links to the iOS and Android SDK changelogs. These provide details on what version of the SDK must be used to utilize certain features. It also outlines any bug fixes that have been released. It is recommended that the SDK is updated every 3-6 months. Subscribing to updates via bintray or setting up reminders on a personal calendar are also recommended.
How does it all work?
The SDKs that Urban Airship provides will take care of device registrations and updates automatically for you, so there is no need for custom integrations to enable push notification for iOS, Android or Amazon. In addition, the SDK will manage any changes to device information and send that data to your Urban Airship project so you can always message your device(s). In addition, any analytic information such as app opens or device information will be populated in your Urban Airship project for further data analysis.
If an SDK is implemented properly, it should only be as big as it needs to be based on the features that you’re using. For Marketers learning about SDKs, check out “What Makes A Good Mobile SDK.”
Implementation best practices:
Make sure you test & setup logging (click here for more details). Anytime you make any changes or updates to the SDK, make sure you test on a development device to ensure your integration was successful. Setting up internal logging will be incredibly valuable when troubleshooting any issues that might occur. In addition, you’ll want to make sure any analytic information is still flowing to your Urban Airship Project before you send the app to Production.
Tech Support best practices:
- What is the size of the Urban Airship SDK?
- Best practices for using the API and why you should log your activity.
Now that you have the SDK integrated into your app, it is time to start implementing Tags, Named Users, and Custom Events to give your app a little more power to be able to engage your users. First, you’ll want to begin with tags to start grouping your users into different segments.