Message:

Subscribe rss
Blog categories
All | Backendless features
Rethinking Device Registrations for Push Notifications
September 26, 2017 by markpiller
Spread the love

Backendless Push Notifications are getting a much-needed facelift. Today, with the release of version 4.3.0 you will start noticing some improvements. Specifically, you will see the  DeviceRegistration data table:

devicereg table - Rethinking Device Registrations for Push Notifications

The new table provides a single, unified view of all devices registered to receive push notifications. The table contains important information such as device ID, deviceToken, a name of the messaging channel. Since the data about registered devices is now stored directly in the Backendless database, it opens up the following possibilities:

  • Registered devices can now be exported/imported into Backendless apps
  • You can create relations between other objects and registered devices (and vice versa)
  • Devices can be registered using the Data Service API or directly via the console.
  • You can run searches for the devices using the console or the API.

Another very useful feature, I am sure you will enjoy, is the automatic linking between the registered devices and the user objects. Suppose your app registers the device for push notifications. If there is a logged in user at the time when the device is being registered, Backendless will automatically link the device with the user in the database (via a 1:1 relation):

device to user mapping - Rethinking Device Registrations for Push Notifications

There are no changes (yet) when it comes to sending push notifications. The API and the console have not changed, but there will be many more very exciting features coming soon.

Enjoy!

 

 

Share this post
Tweet about this on TwitterShare on FacebookGoogle+