Third party push is dead

Origin of domestic third-party push

About 2010 years, the rapid development of Android mobile phones in China, Google's native push (C2DM, now GCM) for various reasons can not be used, then the Android developers use a variety of methods to solve this problem, including Android Mobile phone manufacturers to develop their own push program.

For most developers, in addition to making an App, it is extremely difficult to develop a single set of push systems independently. Even a large number of apps, this is not an easy thing to do. So at the end of 2011, I had the idea of doing an independent third-party push service, and there was the subsequent Aurora push.

The key to delivering a push message

In recent years, many friends in the industry have discussed the key factors that push delivery can be delivered. In fact, the most important thing is whether the SDK can survive.

Specifically, the following two aspects are:

If the SDK fails to initiate a heartbeat in a timely manner, the long connection to the carrier network will be disconnected.

If the SDK task is killed and cannot be pulled up, the message will not be issued at all.

Refer to the previous article: "Principles of Push Technology" http://zhang.hu/mobile-push/

If the SDK side does not effectively bunkers live, then no matter how the server-side optimization, there is no guarantee that the message delivered in a timely manner.

For Android phone manufacturers, there is a contradictory problem. Mobile phone manufacturers want to produce their own mobile phone can have as long as possible standby time, but the App timer in the background to start, maintain the heartbeat behavior, will greatly affect the phone standby time.

Therefore, in recent years, mobile phone manufacturers in order to control the back-office services, continue to introduce various restrictions. such as the previous heartbeat alignment, that is, the App is not allowed to use any RTC background wake-up phone. There is also a tougher way to clean up all back-office services on a regular basis and not allow services to be automatically pulled up through listening broadcasts.

Third party push is dead

As mentioned above, the recent mainstream Android phone will clean up the back-end service, prohibit the service automatically pull up, previously various SDK keepalive means have failed, this problem fundamentally shaken the Android third-party push Service Foundation, resulting in almost all Android Third-party push services are not guaranteed to be delivered.

So, if the push service providers are still using the technology used to pull together, then we can assert that the third-party push is already on the way to death.

How should APP developers respond to such problems?

A more reasonable solution.

Because of the characteristics of the push service, it should be in the form of system-native service. In the early days of the launch of the ios/android system, the issue was taken into account, with IOS having apns,android C2DM (GCM). Unfortunately, Android's GCM has long been unable to be used effectively in China, and Android has not tried to solve this problem, and left the problem to mobile phone manufacturers and App developers.

Given the features of the push service, it's natural to think of the vendor's push channel to solve the problem, just like using APNs on IOS. Use the message channel within the app to send messages to the app, and then wake up the App,app via the vendor's push channel to accept offline messages from the message channel after it is opened.

From the current practice, this is the most effective way to solve the background process being cleaned up.

Domestic Android manufacturers push channel status

At present, the main Android manufacturers in China, Xiaomi, Huawei have to provide the official push service. Through our team's verification, their push service on their own brand of mobile phones, has a relatively stable delivery rate. At present, the best performance is millet, Huawei's push delay is sometimes larger, and not too stable.

and several other OPPO, VIVO, Gionee have no official push service.

The company recently launched a key integration of Xiaomi, Huawei push features to facilitate rapid integration of developers of the push service. But there is no such thing as a very good solution for vendors that do not offer push services. We expect the mainstream handset manufacturers to have a better experience of the APP, can provide solutions to solve this problem.

Article @tiger_ Zhang Hu, founder of Inyumba (Yunba.io), Yunba.io cloud real-time messaging service. Jpush founder, former CTO. Oracle VM Founding team member

Third party push is dead