Jump to: navigation, search

Changes


Native Push (Client)

1,483 bytes added, 10 October
Created page with "{{UnderConstructionStart}} Just like the [[Push_Service_(Client)|{{UBIK}} push service]], {{UBIK}} native push also aims to ensure that the server side can actively deliver..."
{{UnderConstructionStart}}

Just like the [[Push_Service_(Client)|{{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: [https://firebase.google.com/products/cloud-messaging Firebase Cloud Messaging].
** iOS: [https://developer.apple.com/notifications/ 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).

{{Attention|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 ([[SYSCLS_PUSH_TOPIC|push topics]] from the server side.


{{UnderConstructionEnd}}

[[Category:Client|Native Push (Client)]]
[[Category:Xamarin|Native Push (Client)]]
[[Category:Version 4.8|Native Push (Client)]]