Hello, I have also done Umeng push. Your project manager is right. Third-party push services are indeed killed by the system. At present, it seems that only Huawei and Xiaomi among domestic manufacturers have their own push services. The manufacturer's own push service is a system service. Integrating vendor push services can improve push efficiency. Of course, if you want to group them, it is best to obtain the token and mobile phone brand when the App is launched for the first time. If you want to push in the future, determine the model first. If it is a Huawei phone, use the Huawei push interface, Xiaomi phones use the Xiaomi push interface, and other phones use the Umeng push interface. Don't push between Huawei and Xiaomi. Competitors are more likely to be killed.
If you need to ensure stability, you should do this. Integrate several mainstream push notifications, and distinguish according to the device. Xiaomi devices use Xiaomi Push, Huawei devices use Huawei Push, and for other devices, you can use Umeng Push
Have you, the product manager, been deceived by the grandson of which manufacturer?! Any pusher who is not the real son of the mobile phone manufacturer (goddaughter is also acceptable) will have a chance of being killed, especially after theAndroid M引入了DOZEmode.
Why do many manufacturers claim that their push notifications will not be blocked? This is based on a premise: their own push notifications run on their own mobile phone systems, just like the ones running on Nexus phonesGCM(Google Cloud Messaging). They are all system-level applications. Therefore, each The manufacturer's own push itself has such inherent advantages.
Finally, you can find information to prove to your product manager that the push notifications are actually the same, but the push notifications provided by various mobile phone manufacturers have inherent advantages.
Umeng can deal with most situations, but the systems of various manufacturers have now made a lot of adjustments for optimization and launched their own push services. System-level push has natural advantages, while third-party ones are dangerous.
Hello, I have also done Umeng push. Your project manager is right. Third-party push services are indeed killed by the system. At present, it seems that only Huawei and Xiaomi among domestic manufacturers have their own push services. The manufacturer's own push service is a system service. Integrating vendor push services can improve push efficiency.
Of course, if you want to group them, it is best to obtain the token and mobile phone brand when the App is launched for the first time. If you want to push in the future, determine the model first. If it is a Huawei phone, use the Huawei push interface, Xiaomi phones use the Xiaomi push interface, and other phones use the Umeng push interface. Don't push between Huawei and Xiaomi. Competitors are more likely to be killed.
You can read this article: How annoying is external push on Android?
If you need to ensure stability, you should do this. Integrate several mainstream push notifications, and distinguish according to the device. Xiaomi devices use Xiaomi Push, Huawei devices use Huawei Push, and for other devices, you can use Umeng Push
Why do many manufacturers claim that their push notifications will not be blocked? This is based on a premise: their own push notifications run on their own mobile phone systems, just like the ones running on Nexus phones
GCM(Google Cloud Messaging)
. They are all system-level applications. Therefore, each The manufacturer's own push itself has such inherent advantages.Finally, you can find information to prove to your product manager that the push notifications are actually the same, but the push notifications provided by various mobile phone manufacturers have inherent advantages.
END.
Umeng can deal with most situations, but the systems of various manufacturers have now made a lot of adjustments for optimization and launched their own push services. System-level push has natural advantages, while third-party ones are dangerous.