Universal Pushes for Android: FCM, HMS and RuStore in One Place
summary
Covers implementing unified push notifications on Android by integrating Firebase Cloud Messaging (FCM), Huawei Mobile Services (HMS) and regional stores like RuStore to reach more users. Explains using multiple delivery transports in parallel to improve notification delivery rates and handle the shift from single-provider (Firebase) to multi-provider setups.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:54Push notification services overview
- 3:42Custom push transport
- 8:19How custom transport works
- 13:40Disadvantages of custom transport
- 14:44Universal Push SDK concept
- 16:30How Universal Push works
- 18:14Sending pushes via two channels
- 20:05Targeting and segmentation
- 23:01Bitmap indices for targeting
- 24:50Current load and future plans
- 25:31Next steps and iOS limits
- 26:38Unified Push protocol overview
- 29:33Why no Unified Push support
- 30:16Q&A
related talks
06mPush notifications: An India perspective
53mHuawei Mobile Services Vs Google Play Services?
32mAdd Real-Time Features to your Mobile App
23mIn-App Subscriptions for all Android devices
38mPush Notifications that Don’t Suck
30mMarketing Automation Tools and App Engineers — Automating Pushes and Notification Dialog Operations
35mRelease Android apps globally with no headache and minimum stress
01h 14mEntering the Huawei market
