Publishing Mobile Apps: Stores, Monetization, Legal & Marketing

Key Concepts in Publishing Mobile Applications

1. App Signing and Distribution

Before publishing, apps must be signed with a digital certificate to ensure authenticity and integrity. This prevents tampering and verifies the app’s origin.

Types of Signing

How Signing Works

1. Generate a Keystore (Java Keytool or Android Studio):

   keytool -genkey -v -keystore my-release-key.keystore -keyalg RSA -keysize 2048 -validity 10000 -alias my-alias
   

2. Sign the APK/AAB using jarsigner or Android Studio’s build tools.
3. Upload to App Store (Google Play Console or Apple App Store Connect).

2. App Stores: Google Play Store vs. Apple App Store

Both platforms have different requirements, submission processes, and revenue-sharing models.

Comparison Table

3. Monetization Strategies

Apps can generate revenue through multiple channels:

A. Free with Ads (Ad-supported)

• How it works: Display ads (Google AdMob, Facebook Audience Network) and earn per impression/click.
• Example: Pathao (Nepal) uses ads in its driver app to fund free rides for users.
• Pros: Low barrier to entry, scalable.
• Cons: Users may dislike ads; revenue depends on ad performance.

B. Paid Apps (One-time Purchase)

• How it works: Users pay a fixed price to download the app.
• Example: Procreate (iOS) is a paid drawing app with no ads.
• Pros: Higher revenue per user; no ad dependency.
• Cons: Limited user base if price is too high.

C. Freemium Model

• How it works: Free basic version with premium features unlocked via in-app purchases.
• Example: Khalti (Nepal) offers free basic transactions but charges for advanced features like bulk payments.
• Pros: Attracts users first; upsell opportunities.
• Cons: Requires balancing free vs. paid features.

D. Subscriptions

• How it works: Recurring payments (monthly/yearly) for premium content or services.
• Example: YouTube Premium charges a monthly fee for ad-free viewing.
• Pros: Steady revenue stream.
• Cons: High churn risk; requires constant updates.

E. In-App Purchases (IAP)

• How it works: Users buy virtual goods/services within the app (e.g., coins, levels, features).
• Example: Candy Crush Saga sells extra lives and power-ups.
• Pros: High profit margins.
• Cons: Apple/Google take 15–30% cut.

4. Legal and Compliance Requirements

Publishing apps involves legal considerations to avoid rejection or penalties.

Key Legal Aspects

1. Copyright and Trademarks

   • Ensure your app does not infringe on existing IP (e.g., using someone else’s logo, music, or code).
   • Example: If your app uses a Nepal Police logo without permission, it will be rejected.

2. Privacy Policy

   • Required if the app collects user data (even basic info like names or locations).
   • Must comply with GDPR (EU), PDPA (Nepal), and CCPA (US).
   • Example: eSewa must disclose how it stores and uses user transaction data.

3. Terms of Service (ToS)

   • Defines user rights, app usage rules, and liability disclaimers.
   • Example: Daraz’s ToS outlines refund policies and seller responsibilities.

4. Age Ratings

   • Apps must declare if they are 3+, 12+, or 17+ based on content.
   • Example: A gaming app with violence must be marked 17+.

5. App Submission Process (Step-by-Step)

For Google Play Store

1. Prepare Assets:
   • App name, short/long descriptions, screenshots, feature graphic (512x512px), promo video (optional).
2. Set Up Store Listing:
   • Fill in category, contact details, privacy policy URL, and content rating.
3. Upload APK/AAB:
   • Use Google Play Console to upload the signed file.
4. Select Content Rating:
   • Answer questions about app content (violence, nudity, etc.) to get an age rating.
5. Set Pricing and Distribution:
   • Choose regions, price (or free), and monetization method.
6. Review and Publish:
   • Submit for review (takes 1–3 days). Fix any issues and publish.

Mermaid Diagram: Google Play Submission Flow

flowchart TD
    A["Prepare App & Assets"] --> B["Set Up Store Listing"]
    B --> C["Upload APK/AAB"]
    C --> D["Select Content Rating"]
    D --> E["Set Pricing & Distribution"]
    E --> F["Review & Publish"]
    F -->|"Success"| G["App Live on Play Store"]
    F -->|"Rejection"| H["Fix Issues & Resubmit"]

For Apple App Store

1. Create an Apple Developer Account ($99/year).
2. Prepare App Store Kit:
   • App name, screenshots (6.5" and 12.9" iPhone/iPad), description, keywords.
3. Archive and Upload:
   • Use Xcode to archive the app and upload the .ipa file.
4. Fill Metadata:
   • Set price, age rating, and marketing URL.
5. Submit for Review:
   • Apple reviews for compliance (1–5 days).
6. Release:
   • Choose a release date (immediate or scheduled).

6. Marketing and Promotion

A well-marketed app can achieve higher downloads and revenue.

Pre-Launch Strategies

• Beta Testing: Use Google Play Beta or TestFlight (Apple) to gather feedback.
• ASO (App Store Optimization):
  • Use keywords in the title/description (e.g., "Best Budget Calculator for Nepal").
  • Encourage positive reviews (but avoid incentivizing fake ones).
• Social Media & Influencers:
  • Partner with YouTube or Instagram influencers for promotions.
  • Example: Pathao collaborated with Nepali influencers to boost sign-ups.

Post-Launch Strategies

• Paid Ads: Run campaigns on Google Ads or Facebook Ads targeting specific demographics.
• Email Marketing: Collect emails during signup and send updates/offers.
• Referral Programs: Offer discounts for users who refer friends (e.g., Khalti’s referral bonuses).
• App Updates: Regularly add features to retain users (e.g., WhatsApp’s new features like payments).

7. Handling Updates and User Feedback

Apps must evolve to stay relevant.

Types of Updates

Responding to Reviews

• Positive Reviews: Thank users and encourage them to share feedback.
• Negative Reviews:
  • Respond professionally (e.g., "We’re sorry for the issue. Here’s how we fixed it...").
  • Offer solutions (e.g., refunds, feature requests).
• Example: Ncell responds to complaints about network issues with updates on service status.

8. Analytics and Performance Tracking

Use tools to monitor app performance and user behavior.

Key Metrics to Track

In the Real World

1. eSewa (Nepal)

   • Idea Used: Monetization (Transaction Fees + Ads)
   • How: eSewa earns a small percentage (1–3%) on every transaction (e.g., bill payments, transfers). It also displays ads for financial products in its app to generate additional revenue.
   • Real-World Impact: Over 8 million users rely on eSewa for digital payments, making it Nepal’s most successful fintech app.

2. Pathao (Nepal)

   • Idea Used: Freemium Model + Driver Incentives
   • How: Pathao offers free rides for users but charges drivers a commission (10–20%) per trip. It also uses ads in the app to fund discounts for users.
   • Real-World Impact: Pathao dominates Nepal’s ride-hailing market with 100,000+ drivers and millions of rides monthly.

3. YouTube (Global)

   • Idea Used: Ad-Supported Monetization + Subscriptions
   • How: YouTube earns 95% of ad revenue from creators (via AdSense) and offers YouTube Premium ($11.99/month) for ad-free viewing and background play.
   • Real-World Impact: Generates $29 billion/year (2023) and is the #1 video platform worldwide.

Worked Example: Publishing a Budget Tracker App

Scenario: You built a Nepal-focused budget tracker app (like MoneyLion but for Nepali users). Let’s publish it on Google Play Store.

Step 1: Sign the App

1. Generate a keystore in Android Studio:

   keytool -genkey -keystore budget_app.keystore -alias budget_app -keyalg RSA -keysize 2048 -validity 10000
   

2. Sign the AAB file in build.gradle:

   android {
       signingConfigs {
           release {
               storeFile file('budget_app.keystore')
               storePassword 'yourpassword'
               keyAlias 'budget_app'
               keyPassword 'yourpassword'
           }
       }
       buildTypes {
           release {
               signingConfig signingConfigs.release
           }
       }
   }
   

Step 2: Prepare Store Listing

• App Name: "Nepal Budget Tracker"
• Short Description: "Track expenses, set budgets, and save money in Nepali Rupees (NPR)."
• Long Description: Includes features like expense categorization, monthly reports, and Nepali language support.
• Screenshots: Show the app’s UI for home screen, expense entry, and report generation.
• Feature Graphic: A 512x512px icon with a piggy bank and NPR symbol.

Step 3: Set Monetization

• Model: Freemium (free with ads, premium features for $0.99/month).
• Ads: Integrate Google AdMob (banner ads in the free version).
• In-App Purchase: Offer a $0.99/month subscription for ad-free experience and advanced analytics.

Step 4: Submit to Google Play

1. Upload the AAB file in Google Play Console.
2. Fill in content rating (e.g., "3+" since it’s a budgeting tool).
3. Set price to $0 (free) and enable AdMob.
4. Submit for review (takes 2 days).

Step 5: Post-Launch Marketing

• ASO: Use keywords like "Nepal expense tracker", "NPR budget app".
• Social Media: Post on Facebook Groups (e.g., "Nepal Finance Tips") and Twitter with hashtags like #SaveMoneyNepal.
• Influencer Collab: Partner with a Nepali finance YouTuber to review the app.

Mermaid Diagram: Budget Tracker App Revenue Flow

Exam Tip

What to Expect in the Exam

1. Short Questions (2–5 marks):

   • Define keystore, AAB, or ASO.
   • Difference between Google Play Store and Apple App Store (revenue share, review time).
   • List three monetization models and give an example for each.

2. Long Questions (10–15 marks):

   • Describe the step-by-step process of publishing an app on Google Play Store.
     • Include: signing, store listing, content rating, pricing, and submission.
   • Explain how you would market a Nepali food delivery app (like Pathao) using ASO and social media.
     • Cover: keywords, influencer collabs, referral programs.
   • Analyze the pros and cons of a freemium model vs. a paid app model.
     • Use Khalti (freemium) and Procreate (paid) as examples.

3. Practical (5–10 marks):

   • Given a scenario, choose the best monetization strategy (e.g., a gaming app → ads + IAP; a productivity app → subscriptions).
   • Debug a submission rejection: Explain how to fix issues like missing privacy policy or high app size.

How to Score Full Marks

• Use real-world examples (e.g., eSewa, Pathao, YouTube) to illustrate concepts.
• Draw diagrams for processes (e.g., Google Play submission flow).
• Compare and contrast (e.g., Google Play vs. App Store, freemium vs. paid).
• Explain both technical and business aspects (e.g., how signing works + why it’s important for security).
• For coding questions, show one correct code snippet (e.g., keystore generation) and trace its output.

Final Checklist Before Publishing

Remember: Publishing is just the first step—retention and updates keep an app successful! 🚀