Native Push (Client) - Revision history

CWI at 12:38, 24 September 2025

2025-09-24T12:38:09Z

CWI at 13:50, 22 September 2025

2025-09-22T13:50:57Z

CWI at 13:59, 18 September 2025

2025-09-18T13:59:07Z

CWI at 10:23, 18 September 2025

2025-09-18T10:23:42Z

LGE at 13:40, 11 October 2024

2024-10-11T13:40:16Z

LGE at 13:21, 11 October 2024

2024-10-11T13:21:07Z

LGE at 08:00, 11 October 2024

2024-10-11T08:00:09Z

LGE at 07:50, 11 October 2024

2024-10-11T07:50:25Z

LGE: Created page with "{{UnderConstructionStart}} Just like the {{UBIK}} push service, {{UBIK}} native push also aims to ensure that the server side can actively deliver..."

2024-10-10T16:32:10Z

Created page with "{{UnderConstructionStart}} Just like the {{UBIK}} push service, {{UBIK}} native push also aims to ensure that the server side can actively deliver..."

New page

{{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)]]

@@ Line 26: / Line 26: @@
 {{Attention|If you clear the app data or reinstall the app, all existing push topic subscriptions will be reset and you won't receive any pushes until you login with native push enabled again.}}
 [[Category:Client|Native Push (Client)]]
 [[Category:Mobile|Native Push (Client)]]
 [[Category:Version 4.8|Native Push (Client)]]

← Older revision		Revision as of 13:50, 22 September 2025
Line 30:		Line 30:
	[[Category:Mobile\|Native Push (Client)]]		[[Category:Mobile\|Native Push (Client)]]
	[[Category:Version 4.8\|Native Push (Client)]]		[[Category:Version 4.8\|Native Push (Client)]]
		+	[[Category:Version 5.1\|Native Push (Client)]]

@@ Line 5: / Line 5: @@
 * 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.}}
+{{Attention|Native push is only supported on the two mobile clients: Mobile Android and Mobile iOS.}}
 {{Attention|You can terminate the app (swipe it away in the task list) or even restart the device, and the native pushes will still arrive. But on some Android devices, you will no longer receive pushes if you "Force stop" it in the app settings.}}
@@ Line 28: / Line 28: @@
 [[Category:Client|Native Push (Client)]]
 [[Category:Mobile|Native Push (Client)]]

← Older revision		Revision as of 13:21, 11 October 2024
Line 25:		Line 25:
	{{Hint\|The "Activate native push" setting is only enabled during a user session because it's only possible to maintain topic subscriptions with push topic objects.}}		{{Hint\|The "Activate native push" setting is only enabled during a user session because it's only possible to maintain topic subscriptions with push topic objects.}}

		+	{{Attention\|If you clear the app data or reinstall the app, all existing push topic subscriptions will be reset and you won't receive any pushes until you login using a profile

	{{UnderConstructionEnd}}		{{UnderConstructionEnd}}

@@ Line 13: / Line 13: @@
 == Native push settings ==
-You can turn native push on/off in the app's General settings section via the "Activate native push" setting.
+You can turn native push on/off in the app's General settings section via the [[Settings#Push|"Activate native push" setting]].
 {{Hint|If you use multiple profiles on the same device, it's possible that you continue receiving native pushes even after turning it off. Because the device might still be configured to receives them for the other profiles.}}

@@ Line 1: / Line 1: @@
 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.
@@ Line 8: / Line 6: @@
 {{Attention|Native push is only supported on the two mobile clients: Xamarin Android and Xamarin iOS.}}
 == Native push types ==
@@ Line 25: / Line 25: @@
 {{Hint|The "Activate native push" setting is only enabled during a user session because it's only possible to maintain topic subscriptions with push topic objects.}}
-{{Attention|If you clear the app data or reinstall the app, all existing push topic subscriptions will be reset and you won't receive any pushes until you login using a profile
+{{Attention|If you clear the app data or reinstall the app, all existing push topic subscriptions will be reset and you won't receive any pushes until you login with native push enabled again.}}
-−
-{{UnderConstructionEnd}}
 [[Category:Client|Native Push (Client)]]
 [[Category:Version 4.8|Native Push (Client)]]
 [[Category:Xamarin|Native Push (Client)]]

@@ Line 9: / Line 9: @@
 {{Attention|Native push is only supported on the two mobile clients: Xamarin Android and Xamarin iOS.}}
-== Push types ==
+== Native 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 ==
+== Native push settings ==
-You can turn native push on/off in the app's General settings section.
+You can turn native push on/off in the app's General settings section via the "Activate native push" setting.
 === 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.
+In order to properly determine which pushes to receive or not, the client requires access to [[SYSCLS_PUSH_TOPIC|push topics]] from the server side.
@@ Line 22: / Line 29: @@
 [[Category:Client|Native Push (Client)]]
 [[Category:Version 4.8|Native Push (Client)]]