The effective reach of mobile devices is affected by many factors, with diverse push channels. There is no operational way to test the actual business scenarios or stress scenarios, so it is not possible to provide accurate push reach data.
The mPaaS mobile push service pushes messages to the device side through the following channels:
- For iOS devices, the mPaaS push backend pushes the data to the endpoints via the Apple APNs service, which is responsible for the push to the endpoints.
- For Android devices, if third-party channels (such as Huawei, Xiaomi, and other vendor push channels) are set up in the mPaaS console, the mPaaS push backend is targeted to push data to these third-party vendor servers, which are responsible for pushing to the endpoints.
- For other channels, the device side establishes a long link with the mPaaS backend and pushes messages through that long link as a push channel.
In the case of the mentioned push channels APNs, third-party vendor push servers, and self-built channels with successful connections, it can be assumed that nearly all of them can successfully complete the push.However, the actual reach of the push can be affected by many factors, for example:
- The failure of a third-party push server results in a failure of mPaaS to push information to it.
- The problem between the third-party push server and the device side results in the information not being delivered successfully.
- The communication problem between the push server and the Internet causes the message to be unsuccessfully delivered.
- The ability of the user’s own app to keep the process alive affects the smoothness of the self-built push channel, resulting in the unsuccessful delivery of the push information.
- The failure of the carrier network or wireless network where the device end is located results in unsuccessful delivery of information.
- The push channel is disabled due to the influence of other apps on the device side, resulting in unsuccessful delivery of information.
- The design and coding of the app itself leads to differences in keeping alive.
- Other factors affect the effectiveness of the push channel.
Most of these factors are not under the control of the mPaaS push service itself. We cannot provide official data on this technical metric at the mPaaS level.
Although Alipay, built with the same technology, has an effective reach of around 98%, Alipay uses other means to ensure a successful push channel such as keep-alive and mutual protection among apps of the same family, cooperation with device manufacturers of allow list. These means, however, are not certainly applicable to universal mobile applications. For other universal mPaaS-based mobile applications, we get an effective reach between 85% and 95% in the sampling range we analyzed.