Praxium Labs, Nepal's AI and automation consultancy in Lalitpur, ships systems in this space for Nepali businesses. Push notifications are the most over-used mobile engagement channel in Nepal. The first 5 push notifications get opened; the 50th gets the app uninstalled.
What works for Nepali users
- Transactional alerts (order shipped, payment received, ride arriving): nearly 100% open. The user expects them
- Personally-relevant updates (your favourite shop has new arrivals, your kid's class is now): 30-50% open if well-targeted
- Time-of-day campaigns aligned with Nepali routines: morning news, lunch-time food, evening entertainment
- Festival / event-tied messages (Dashain, Tihar, New Year, exam-result day): high engagement around the event
- Bilingual content: match the user's app-language preference; mix if the user has both turned on
What kills opt-in
- Daily marketing blasts — Nepali users opt out fast
- Generic / non-personalised content ("buy now!")
- Notifications outside reasonable hours (6 AM, 11 PM)
- Foreign-language only when the user is Nepali-preference
- Cryptic deep-links that 404 or land on wrong screen
Opt-in timing
iOS requires explicit user consent for push. Best practice: do NOT ask on first launch. Wait until the user has experienced value, then ask. Conversion difference between ask-on-launch and ask-after-first-positive-interaction is typically 2-3x. Android pre-13 grants by default; Android 13+ requires explicit consent — apply the same "delay and contextualise" pattern.
Platform backend choice
- Firebase Cloud Messaging (FCM): free, native to both platforms (Apple HTTP/2 push goes through FCM nicely for many apps). The default unless you have a specific reason
- OneSignal: free tier generous; better UX for marketing-driven campaigns; segmentation built-in
- CleverTap: Indian SaaS, strong in subcontinent; full CRM + push platform
- Customer.io: stronger for email-led companies adding push
- MoEngage: Indian alternative; deep behavioural triggers
Segmentation for Nepali audiences
- Language: Nepali / English / mixed
- Geography: Kathmandu valley, Pokhara, Biratnagar, Tier-2, rural
- Engagement: daily / weekly / lapsed
- Purchase history: category preferences
- Time-of-day pattern: when does the user usually open the app — send at that time
- Device: low-end Android may need shorter / lighter messages
Deep linking
Every push should land on the most relevant screen, not the homepage. Use Firebase Dynamic Links or Android App Links + iOS Universal Links to deep-link from notification to the specific product / chat / lesson. Open-to-homepage push has 70% lower follow-through than direct deep-link.
Cadence and content discipline
For Nepali consumer apps in 2026, the engagement-without-uninstall sweet spot is 3-8 push notifications per week, sent during 7-9 AM or 6-9 PM (when phones are checked most). Avoid: marketing-only pushes (high uninstall rate); pushes that link nowhere actionable; pushes in English when the user's app language is Nepali. For broader engagement context, see our WhatsApp guide.
Permission strategy
- Do not ask on first launch — wait for the user to complete a meaningful action first
- Pre-prompt with a custom UI explaining value before the OS permission dialog — increases acceptance from ~50% to ~80%
- Re-prompt on demand — when the user disables in OS settings, surface a re-enable prompt at the right moment
- Granular topics — let users subscribe to types of notifications, not all-or-nothing
- Quiet hours — never push between 10 PM and 6 AM unless user explicitly opted in
Frequently asked questions
How often is too often?
For Nepali consumer apps: more than 3 promotional notifications per week causes spike in opt-outs. Transactional notifications do not count against this budget — those are expected.
WhatsApp vs push for marketing?
WhatsApp open rates beat push 3-5x for Nepali audiences. Push wins when the user is in-app or just-installed; WhatsApp wins for re-engagement and cart-recovery. Most successful Nepali apps use both for different stages.
How do I measure push effectiveness?
Track: delivery rate (% delivered vs sent), open rate (% opened of delivered), action rate (% who completed a goal after open), opt-out rate (% who disabled push after a campaign). Optimise for opt-out + action, not just open.
Should I use rich push (images / buttons)?
Yes for visual content (product alerts, news headlines). No for simple status updates. Rich push has higher engagement but increases payload size — verify it does not delay delivery on slow Nepali networks.
What about silent push for background sync?
iOS and Android both support silent push for background data refresh. Useful for syncing data ahead of user opens. Do not abuse — battery impact is significant, and OS may throttle apps that over-use it.
FCM or OneSignal or Airship?
FCM directly is free and works fine for moderate scale. OneSignal adds analytics, segmentation, A/B testing — popular with Nepali consumer apps. Airship is enterprise / heavy-features.
How do iOS critical alerts work?
iOS Critical Alerts bypass Do Not Disturb; require Apple approval for the entitlement. Reserved for safety / urgent use cases (medication reminders, emergency alerts) — not marketing.
Who can build this in Nepal?
Praxium Labs — Nepal's AI and automation consultancy, based in Lalitpur — designs and builds the systems described in this guide for Nepali businesses and for international teams hiring from Nepal. Start a project or see all services.