---
title: "How do I publish a VoIP app to the App Store and Google Play?"
topic: "Setup & Configuration"
updated: 2026-07-09
canonical: https://acrobits.net/resources/knowledge-base/publish-voip-app-app-store/
summary: "Publishing a VoIP app means submitting to both the Apple App Store and Google Play, each with VoIP-specific rules that generic app guides skip, mainly around push notifications and background modes. On iOS you need an Apple Developer account, CallKit integration so incoming calls appear on the native call screen, and PushKit VoIP pushes that report every call to CallKit. On Android you need a Google Play Console account, Firebase Cloud Messaging for reliable push, and a foreground service notification if the app stays connected for call readiness. Apple review typically runs 3–7 business days and Google 1–3. If you use a white-label platform, the vendor handles the technical build and submission while you supply branding and configuration."
---

# How do I publish a VoIP app to the App Store and Google Play?

> Publishing a VoIP app means submitting to both the Apple App Store and Google Play, each with VoIP-specific rules that generic app guides skip, mainly around push notifications and background modes. On iOS you need an Apple Developer account, CallKit integration so incoming calls appear on the native call screen, and PushKit VoIP pushes that report every call to CallKit. On Android you need a Google Play Console account, Firebase Cloud Messaging for reliable push, and a foreground service notification if the app stays connected for call readiness. Apple review typically runs 3–7 business days and Google 1–3. If you use a white-label platform, the vendor handles the technical build and submission while you supply branding and configuration.

Publishing a VoIP app means submitting to both the Apple App Store and Google Play, each with VoIP-specific rules that generic app guides skip, mainly around push notifications and background modes. On iOS you need an Apple Developer account, CallKit integration so incoming calls appear on the native call screen, and PushKit VoIP pushes that report every call to CallKit. On Android you need a Google Play Console account, Firebase Cloud Messaging for reliable push, and a foreground service notification if the app stays connected for call readiness. Apple review typically runs 3–7 business days and Google 1–3. If you use a white-label platform, the vendor handles the technical build and submission while you supply branding and configuration.

## Apple App Store (iOS)

### Apple App Store setup requirements

You need an [Apple Developer Account](https://developer.apple.com/programs/) ($99/year). This must be an Organization account if you're publishing as a business, which requires a D-U-N-S number. Apple organization verification can take 1–2 weeks if you do not already have one.

### Apple App Store VoIP requirements

Starting with iOS 13, Apple enforces specific rules for VoIP apps:

**CallKit is mandatory.** Your app must integrate with CallKit to display incoming calls on the native iOS call screen. Apps that show their own custom incoming call UI without CallKit will be rejected.

**PushKit VoIP push is restricted.** Since iOS 13, every VoIP push notification MUST report a call to CallKit. You cannot use VoIP pushes as a general wake-up mechanism for your app. Violating this can put your VoIP push certificate at risk.

**Background modes.** Your Info.plist must declare the voip background mode, but only if you're legitimately handling VoIP calls. Apple reviewers may check this.

### Common App Store rejection reasons

Rejection ReasonWhat HappenedHow to Fix

VoIP push misuseApp uses PushKit for data sync, not callsUse standard APNs for non-call notifications
Missing CallKitIncoming calls don't show on lock screenIntegrate CallKit for all incoming calls
No privacy policyApp accesses microphone/contacts without explanationAdd privacy policy URL in App Store Connect
Incomplete metadataScreenshots don't show actual functionalityUse real screenshots showing call/registration flow
Login wall without demoReviewer can't test without a SIP accountProvide a demo account in review notes

### Apple App Store review timeline

Initial submission: 3–7 business days. Subsequent updates (once your app has a track record): 1–3 days. Expedited reviews are available for critical bug fixes but don't count on them.

## Google Play (Android)

### Google Play setup requirements

[Google Play Console](https://play.google.com/console/) access costs a one-time $25 fee. Organization verification is faster than Apple, typically a few days.

### Google Play VoIP requirements

Android has its own requirements for VoIP apps:

**Firebase Cloud Messaging (FCM) is required** for reliable push notifications. Without FCM, your app must maintain a persistent background connection, which Android's battery optimization will kill. Users will miss calls.

**Foreground service notification.** If your app maintains a connection for call readiness, Android requires a persistent notification informing the user. This is a policy requirement, not optional.

**Microphone permission rationale.** Google requires that you explain why your app needs microphone access before the permission prompt appears.

### Google Play review timeline

Typically 1–3 business days. Google's review is typically faster than Apple's, and recent Android versions have placed more attention on permission usage and background behavior.

## How white-label publishing changes the process

If you're using a white-label platform, the workflow shifts significantly. You're not writing code; you're providing branding assets and configuration while the vendor handles the technical build.

### What You Provide

  - App name and bundle/package identifier

  - App icon, splash screen, color scheme

  - Your Apple Developer and Google Play Console account credentials (or invite the vendor as a team member)

  - SIP server configuration details

  - Privacy policy URL

### What the Vendor Handles

  - Compiling the app with your branding baked in

  - Generating and managing push notification certificates (APNs, FCM)

  - Configuring CallKit integration, background modes, and permissions

  - Building signed binaries for both platforms

  - Submitting to both stores under your accounts

  - Handling reviewer questions and resubmissions

### What Stays Your Responsibility

  - Maintaining your Apple Developer and Google Play Console accounts (paying annual fees, responding to policy emails)

  - Keeping your privacy policy current

  - Responding to user reviews

  - OS update compatibility, though a good vendor handles the app updates for you

## Publishing timeline for a white-label app

PhaseDuration

Branding assets and configuration3–5 days
App build and internal QA5–7 days
Apple review3–7 days
Google review1–3 days
**Total****2–4 weeks**

This assumes your developer accounts are already set up and your SIP infrastructure is ready. Add 1–2 weeks if you need a new Apple Organization account.

## Keeping your app in the store

Publishing isn't a one-time event. Both Apple and Google release new OS versions annually, and both will flag or remove apps that don't stay current.

  - **iOS**: Apps that haven't been updated in 2+ years may receive removal warnings.

  - **Android**: Target API level requirements increase yearly. Apps must update to the latest target SDK or face delisting.

In many white-label setups, the vendor handles these updates as part of the service agreement. Verify this is covered in your [MSA](/blog/cloud-softphone/white-label-softphone-msa/).

*Want to skip the complexity? [Cloud Softphone](/cloud-softphone/) handles the entire build-and-submit process. You provide the brand; we handle Apple, Google, and every OS update after that.*

## Turning your app into a revenue channel

Getting your app into the stores is the start, not the finish. Cloud Softphone's **custom web tabs** let you push new content (billing portals, upsell pages, promotional offers) to subscribers without triggering a new app-store review cycle. Included free in White Label bundles.

See [What Is the ROI of Offering a Branded Mobile App](/blog/cloud-softphone/roi-branded-mobile-app-voip/) for the payback analysis, and [How to Price and Monetize a Branded Softphone App](/blog/cloud-softphone/price-branded-softphone-app/) for tier-and-margin strategy.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Publish a VoIP App to App Store and Google Play",
  "description": "Publishing a VoIP app means submitting to both the Apple App Store and Google Play, each with VoIP-specific rules that generic app guides skip, mainly around push notifications and background modes. On iOS you need an Apple Developer account, CallKit integration so incoming calls appear on the native call screen, and PushKit VoIP pushes that report every call to CallKit. On Android you need a Google Play Console account, Firebase Cloud Messaging for reliable push, and a foreground service notification if the app stays connected for call readiness. Apple review typically runs 3–7 business days and Google 1–3. If you use a white-label platform, the vendor handles the technical build and submission while you supply branding and configuration.",
  "url": "https://acrobits.net/blog/cloud-softphone/publish-voip-app-app-store/",
  "datePublished": "2026-05-06T09:00:00Z",
  "dateModified": "2026-05-06T09:00:00Z",
  "author": {
    "@type": "Organization",
    "name": "Acrobits"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Acrobits",
    "url": "https://acrobits.net"
  }
}

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How White-Label Changes the Process",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "If you're using a white-label platform, the workflow shifts significantly. You're not writing code: you're providing branding assets and configuration while the vendor handles the technical build."
      }
    },
    {
      "@type": "Question",
      "name": "What You Provide",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "This assumes your developer accounts are already set up and your SIP infrastructure is ready. Add 1–2 weeks if you need a new Apple Organization account."
      }
    },
    {
      "@type": "Question",
      "name": "What the Vendor Handles",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "This assumes your developer accounts are already set up and your SIP infrastructure is ready. Add 1–2 weeks if you need a new Apple Organization account."
      }
    },
    {
      "@type": "Question",
      "name": "What Stays Your Responsibility",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "This assumes your developer accounts are already set up and your SIP infrastructure is ready. Add 1–2 weeks if you need a new Apple Organization account."
      }
    }
  ]
}