push notification delay

[Carl Ott]

What expectations can you set for delay from sending a notification from the Appery console, to receiving it on a device (either Android or iOS)?

I'm working through the Appery Push tutorial using a 1st Gen Google Nexus 7 on 4.3. And I'm trying to extend the tutorial to a more practical purpose. Although I have managed to get a few messages through in a matter of seconds, messages often take more than a few minutes to arrive.

This really slows down the build/test cycle- it's very difficult to tell if any given message is not coming through because of something I did, or if it's normal and really long jitter caused by some combination of Appery and Google Cloud Messaging.

In addition to adding frustration, this also casts doubt on whether push notifications using Appery can be relied on for production purposes....

[maxkatz]

Right now push messages are sent when you click send button. In early November we are adding the option to schedule push messages.

[Carl Ott]

Max,

thanks - cool. Yes sometimes notifications go through right away. I can appreciate the benefits of scheduling push messages, but I was actually asking about something else.
Many times today, I have sent a message from the Appery Push Notifications console. In many cases, although the console did indicate that a message was sent (ie. the count of notifications sent was incremented), it was some time, in some cases nearly 5 minutes, before the message finally arrived on my device. In other cases, like now, it shows up right away. Can you explain what is going on, or what could be going on to cause such wide variation?

[maxkatz]

When you click send, it might take a some seconds for the message to be sent We got workers who are looking for new messages, queue them, and send to Google or Apple services. There also could be a short delay from Google or Apple side.