We have moved to a new Sailfish OS Forum. Please start new discussions there.

Push notifications

asked 2014-01-03 22:30:28 +0300

koudi gravatar image

updated 2014-01-04 00:21:28 +0300

AL13N gravatar image

Is there currently (can't find it) or is planned support for iOS/Android-like push notifications?

edit retag flag offensive close delete


do you mean for app developers or ...?

AL13N ( 2014-01-04 00:21:45 +0300 )edit

Well...yes. I don't see how normal user would use such thing. Maybe I wasn't really clear about what I mean.


koudi ( 2014-01-04 00:40:30 +0300 )edit

This is an excellent question.

v2px ( 2014-01-04 02:53:14 +0300 )edit

@koudi if unclear, please edit and rephrase your question :-)

AL13N ( 2014-01-04 11:04:40 +0300 )edit

What technologies would you like the solution to use?

Stskeeps ( 2014-01-15 22:16:38 +0300 )edit

3 Answers

Sort by » oldest newest most voted

answered 2014-01-16 09:21:06 +0300

qwazix gravatar image

I'd like to see an open standard used. Apple and Google are using push as a method to lock down users. Also all that centralized power might save battery but it compromises privacy.

I think there are two possible solutions:

  1. Work with QtProject to create something that will work in all platforms Qt is available and where anybody can host his own server. This however might end up in the device having to connect to multiple hosts at the same time, not very battery friendly.

  2. (ab)use a messaging service (XMPP comes to mind) with federation to implement push. Everybody can host his own jabber server, federated with the jolla one. A local and remote jabber user will be created for each app installation. The local user will make a friend request to the remote user which will then talk back in JSON providing notifications. This way the phone will need to just be connected to one federated XMPP account only at each time. This can be jolla's by default or replaced with any other the user might want, as long as it supports federation.

edit flag offensive delete publish link more


Talking with a friend who has some knowledge of this and he mentioned that the data-packet (TCP/IP part) is not so hard, it is the specific carrier optimised settings that are the tricky bit (i.e. how far apart do the "keep-alive" messages need to be for a specific network in each country,

ymb ( 2014-01-16 15:37:29 +0300 )edit

Continued from previous comment.... I could see this being done as something along the lines of the Open StrepMap project (a commons collected data source)

ymb ( 2014-01-16 15:40:22 +0300 )edit

Note that this solution would mean that all applications would need to run a separate service each connecting to a separate server. I agree that privacy is a problem, but that depends what you (or the service) sends. Note that all your SMS texts go through and are archived(!) on one or more servers.

Nux ( 2014-01-16 19:57:12 +0300 )edit

Only the first solution would require that. The second one involves connecting as a apecific user to the provided XMPP server which can be Jolla- or self-hosted. The phone will maintain one connection to said server using the existing daemon, and notify (wake) apps depending on the user which received the message.

qwazix ( 2014-01-16 20:07:33 +0300 )edit

Wouldn't that mean that you would have to have a separate account for each service? With each password saved separately on your device?

Nux ( 2014-01-16 20:21:24 +0300 )edit

answered 2015-01-27 23:03:00 +0300

yanoo gravatar image

updated 2015-01-28 11:07:43 +0300

smoku gravatar image

@tbr is working on support for MQTT under Mer Project umbrella.

MQTT is a open machine-to-machine (M2M)/"Internet of Things" connectivity protocol. The preliminary experiments with MQTT on SailfishOS are very promising.

edit flag offensive delete publish link more



This is a community project, so if anyone wants to join in and help make this a reality, then please make yourself known.

r0kk3rz ( 2015-01-28 11:37:42 +0300 )edit

MQTT is just a building block. I have a concept for a push notification system based on top of MQTT. I posted a diagram to twitter some time ago. This would need further work/help and financing to become usable.

tbr ( 2015-01-28 13:16:29 +0300 )edit

answered 2014-01-16 23:46:41 +0300

dr_gogeta86 gravatar image

updated 2014-01-17 21:49:13 +0300

I vote for an cetralized one regulated by QA if they are on harbour .... why ?

  1. On android push services are abused and sometimes requires a battery sucker daemon they must be regulated ...
  2. IMHO they ask on first start if you wanna use push ..... ( i prefer apple alike permission, simple and effective )

But the first two point are to be more like a propositions than answers ......

The reality is a bit different ... the case ?


We can't use push services due most of app till now ( is a pity ) can't use upstream push services ( whatsapp and foursquare for example ) and then an effective ( ihmo ) approach is like Meego-Harmattan ... you can use daemon but you must to limit drain, in battery and in data

I hope this post can be discussed constructively ... I hope SaifishOs can be saw as a clear, productive and good organized platform rather then ... messy, complicated and with many wheels provieded for the same thing ....

Better a good implemented method then reinvent it every time ... see android process and you know what I mean ....

Respect Fabio

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools



Asked: 2014-01-03 22:30:28 +0300

Seen: 3,512 times

Last updated: Jan 28 '15