Difference between revisions of "Native Push (Client)"
(Created page with "{{UnderConstructionStart}} Just like the {{UBIK}} push service, {{UBIK}} native push also aims to ensure that the server side can actively deliver...") |
(No difference)
|
Revision as of 16:32, 10 October 2024
Just like the UBIK® push service, UBIK® native push also aims to ensure that the server side can actively deliver messages to the clients. However, it has a few major differences by comparison.
- The native push uses the existing 3rd party solutions/infrastructure and is, therefore, dependent on the availability of those.
- Android: Firebase Cloud Messaging.
- iOS: Apple Push Notification service.
- The native push is better supported by and integrated into the mobile platforms. So the delivery of the pushes is better guaranteed just like with other apps (e.g. email or online messaging apps).
 | Native push is only supported on the two mobile clients: Xamarin Android and Xamarin iOS. |
Push types
Currently, the only supported push type is text messages. Upon clicked, they simply launch the UBIK® client or bring it to the foreground if that's not the state of it yet.
Push settings
You can turn native push on/off in the app's General settings section.
Technical background
In order to properly determine which pushes to receive, the client requires access to (push topics from the server side.
