Push notifications: An India perspective
summary
India shows low push delivery because many users turn off mobile data and some custom Android builds kill background services; raising increase TTL from 4 to 8 hours measurably improves delivery. Practical patterns include a periodic job that refreshes FCM tokens and server-side recency-based buckets (0–7, 7–31, 31+) to stagger campaigns and avoid counting stale tokens, a background pull-for-missed approach that risks extra wakeups, and sending data messages delivered ahead and scheduled locally so alerts appear reliably at the target time.
AI-written summary · about
related talks
38mPush Notifications that Don’t Suck
41mUniversal Pushes for Android: FCM, HMS and RuStore in One Place
25mWhen your app is asleep
11mEffective background tasks on Android
32mAdd Real-Time Features to your Mobile App
28mUsing Communication APIs to enhance your UX (and reduce notifications!)
28mStandby Buckets in Android
39mModern best practices for background task execution