Notifications - Mobile App Quick Start Guide



Basics 

To get started with push notifications for mobile you will need an account on xtremepush and a mobile app project. You can login at dashboard.xtremepush.com. Once logged in if you don't have one ready to use, add a NEW mobile App project.

add-project.png

Don't have a login?

If you are already a customer all accounts come with multi-user access and the person(s) in your organisation who is responsible for administration of user access will be able to provide appropriate user access to users who are; involved in the integration process, running campaigns etc. If you need help please contact your account manager or submit a support ticket.

If you are not a customer please request a demo.  

If you are creating a New mobile App project you will need to enter the following details and click save to initialise your project: 

  • Title: Name used to identify project on the platform, something obvious to help you find it.  
  • Description: A short description of what the project is for.
  • Timezone: The timezone used for analytics in the project. Important this will dictate the starting point for analytics like daily users. You can set this to the local timezone of platform users if this makes sense. Default is UTC, which is a good compromise if users are likely to be spread across different timezones. 
  • Icon: Helps to identify project on the platform, use app icon to help you find it.   

New_App.png
 

Android

To enable notifications for an Android App you will also need an android developer accounts. From this account you will generate credentials required to send notifications to Android devices. These will then be uploaded to your project on xtremepush. Details on how to do this in Docs here:

Once basic prerequisites and credentials have been setup you are ready to integrate the SDK. The next steps are to import the SDK into you Android App and then make some minor updates to your App code to complete the integration:

 

iOS

To enable notifications for an iOS App you will also need an iOS developer accounts. From this account you will generate credentials required to send notifications to iOS devices. These will then be uploaded to your project on xtremepush. Details on how to do this in Docs here:

Once basic prerequisites and credentials have been setup you are ready to integrate the SDK. The next steps are to import the SDK into you iOS App and then make some minor updates to your App code to complete the integration:

 

Support for Mobile Frameworks 

 If your app is not fully native but built with a mobile framework you will need the iOS and Android prerequisites outlined above but your code changes will relate to the specific mobile framework you are using. We support a range of popular mobile frameworks including:

 

Notifications in Test and QA Environments

Most enterprises have multiple backend environments and builds of mobile apps for various stage of their development cycle (e.g. Test, Staging, Production). To map their dev process on the xtremepush platform enterprises typically hook the various builds of their App into matching projects on the platform. This is very flexible and can generally map to any process for example some enterprises have up to 5 projects to fit their own dev cycle (Dev Test, QA, UAT, Pilot, Prod)

The projects are logically separated by the application keys (found in project settings and used when integrating) so if you are sending notifications in a test environment there is no possibility you will send them out on the production app. This allows you to reuse your iOS and Android push credentials across the different projects for different builds of the same App:

  • For Android you can use the same FCM credentials in all your builds
  • For iOS you can use the same APNs production cert in all your builds.

Your user’s roles and access to projects can be managed using our UAM capabilities:

For further segregation and simplicity we can also create separate account for non production builds of your App so that the production app is further separated from non prod envs. Any API integrations with your backend are also kept logically separate by the different application tokens found in each project. This allows you to also map your backend envs to the appropriate project on our platform.

Have more questions? Submit a request

0 Comments

Article is closed for comments.