Mobile Product Growth Guide: Optimization Playbook

The India Mobile Acquisition & Retention Landscape

India is a mobile-first, Android-dominated internet market. With over 750 million smartphone users, growth teams must design acquisition and engagement flows optimized for mobile screens and low-bandwidth environments. In tier 2 and tier 3 cities, users are quick to uninstall apps that consume storage or drain battery. Thus, maintaining user engagement requires a balanced channel strategy across push notifications, SMS, and WhatsApp.

This guide reviews how to implement these channels to optimize user activation and retention.

1. Channel Comparison: Open Rates, Costs & Best Practices

To design high-converting messaging campaigns, product teams must evaluate the economics and performance of each channel:

• Push Notifications: Free. Best for real-time transactional updates and personal nudges. Open rates average 2-4%. Android 13+ requires explicit opt-in, making permission request flows a critical product optimization step.
• SMS: Paid (per-message cost, e.g. ₹0.12). Crucial for OTP authentication and offline transactional alerts. Open rates average 8-10%, but promotional inbox tab placement reduces effectiveness.
• WhatsApp Business API: Paid (conversation-based model, e.g. ₹0.30–₹0.80 per template conversation). Industry-leading open rates of 85-90%. Highly interactive, but expensive. Best reserved for high-intent conversions (e.g. abandoned cart checkout, KYC completion, policy renewals).

2. Android 13+ Notification Permissions & Onboarding

Historically, Android apps could send push notifications by default. In modern Android, apps must explicitly request permission. Prompting the user immediately on first launch is a conversion killer, resulting in a 40-50% opt-out rate.

Instead, use a "pre-permission primer"—a well-designed in-app dialog explaining *why* the user needs notifications (e.g., tracking delivery, security alerts) before triggering the system permission prompt. Prompt only after the user has taken their first core action.

3. Deep-Linking: Branch vs. Firebase Dynamic Links

A messaging campaign is useless if it takes the user to the generic app home screen. Deep-linking maps custom URLs to specific screens inside the native mobile app (e.g. taking a user directly to a discount checkout screen). Implementing deep-linking via protocols like Universal Links (iOS) and App Links (Android) ensures a seamless transition from web or SMS to native app, increasing conversion rates by 40%.

4. Optimizing Mobile Performance and Battery Impact

In the Indian market, entry-level mobile devices with limited RAM and flash memory represent a significant share of your user base. Product teams must optimize the native app package size (APK) to prevent uninstall actions. Large application assets should be compressed or streamed dynamically. Additionally, running background services to fetch data or handle heavy tracking events can drain the user's battery, prompting immediate uninstalls. Configure your analytical SDKs to batch event tracking data and upload it only during active user sessions or over Wi-Fi, keeping the background footprint minimal.

Frequently Asked Questions