Skip to content
Tutorials Center
My learning

Topics

Lesson 32 of 37 ยท Building and Publishing

Publishing, PWA and Live Updates

Ship an Ionic app to Google Play and the App Store, deploy it as a PWA, understand review rules, staged rollouts and what live updates may and may not change.

An Ionic app can reach users in three ways: as a store app on Google Play and the Apple App Store, as a Progressive Web App (PWA) installed from a browser, or as a plain website. The same code base serves all three, but each channel has its own rules, review process and update model. This lesson covers each one and how to push fixes between store releases.

Choosing the channel

Play Store App Store PWA
Reach Android iOS any browser
Native plugins yes yes only web APIs
Review automated plus some manual, hours to days manual, usually 1-2 days none
Fee one-time yearly hosting only
Update store release or live update store release or live update instant on deploy
Push, background, Bluetooth full full limited, varies by browser

Many teams start with the PWA to validate the idea, then add Capacitor when they need native features or store presence.

Releasing to Google Play

  1. Create an app in the Play Console and fill in the store listing: name, short and full description, screenshots, feature graphic, privacy policy URL.
  2. Complete the Data safety form honestly, listing what data you collect and share, including from third-party SDKs.
  3. Build a signed AAB (./gradlew bundleRelease, see Building for Android and iOS) and upload it to a track.
  4. Use the tracks in order: internal testing (up to 100 testers, instant), closed testing, open testing, then production. New personal developer accounts must run a closed test with a minimum number of testers for a number of days before production access, so plan for it.
  5. Use a staged rollout: release to 5 percent, 20 percent, then 100 percent while watching crash rates. You can halt a rollout.

Releasing to the App Store

  1. Join the Apple Developer Program, create an App ID that matches your bundle id, and make the app in App Store Connect.
  2. Archive in Xcode and upload to App Store Connect. Distribute first with TestFlight to internal and external testers.
  3. Fill in metadata: screenshots for required device sizes, description, keywords, age rating, support URL, privacy policy, and App Privacy labels.
  4. Submit for review. If you use login, offer a demo account in the review notes.

Common rejection reasons for hybrid apps:

  • Minimum functionality: the app is just a website in a frame. Native features, offline behavior and a real app experience help.
  • Missing or vague permission texts (see App Icons, Splash Screens and Permissions).
  • Crashes on launch or broken links in the review build.
  • Account deletion: apps with account creation must let users delete the account in the app.
  • In-app purchase rules: digital goods generally must use the platform's payment system.
  • No privacy policy, or one that does not match the data you collect.

Store policies change. Read the current Google Play Developer Policy and Apple's App Review Guidelines before every major release rather than relying on memory or old articles.

A release checklist

JS A release readiness check

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Deploying as a PWA

A PWA is the web build served over HTTPS with a web app manifest (name, icons, colors, start URL) and a service worker (offline caching). Browsers then offer "Install app".

JSON
{
  "name": "Trail Notes",
  "short_name": "Trails",
  "start_url": "/",
  "display": "standalone",
  "background_color": "#0b5fff",
  "theme_color": "#0b5fff",
  "icons": [
    { "src": "/icons/icon-192.png", "sizes": "192x192", "type": "image/png" },
    { "src": "/icons/icon-512.png", "sizes": "512x512", "type": "image/png", "purpose": "maskable" }
  ]
}

In Angular, ng add @angular/pwa adds the manifest and a service worker; Vite projects use vite-plugin-pwa. Service worker caching is powerful and tricky: a bad worker can keep serving an old app. Version your cache, show an "Update available" prompt, and test with the DevTools Application panel. Our Chrome DevTools tutorial covers it in more depth.

Remember the limits: iOS supports installing PWAs and push for installed ones, but with fewer capabilities than a native app, and storage can be cleared if the PWA is unused for a while.

Live updates

Waiting days for a store review to fix a typo is painful. Live updates replace the web layer of an installed app (the HTML, CSS, JavaScript in the bundle) without a store release. Services include Ionic Appflow, Capgo, or a self-hosted solution.

What live updates can change: your web code and web assets. What they cannot change: native code, plugins, permissions and the native configuration. Those need a new binary through the store.

Rules to follow:

  • Both Apple and Google allow updating app content through the interpreted web layer, provided you do not change the main purpose of the app or bypass review for things the policies forbid. Read the current terms.
  • Version the web bundle against the native version: a web bundle that calls a plugin the installed binary lacks will break. Each live update channel should target a native version range.
  • Roll out gradually and keep a rollback: if the new bundle crashes at startup, the plugin should revert to the previous one automatically.
JS Choosing a compatible live update

Press Run (or Ctrl + Enter) to see the console output here.

No output.

After release

Watch crash reports (Play Console vitals, Xcode Organizer, or Sentry and Firebase Crashlytics), reviews and the adoption of each version. Plan a way to force an upgrade when an old version must stop working (a minimum supported version returned by your API, with a friendly "Please update" screen), and keep the API backward compatible for a long time, because old app versions stay in the wild.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What can a live update change?

    Only the web layer can be replaced; native changes need a new store binary.
  2. 2. Why does a staged rollout help?

    Watching crash rates at 5 percent is much safer than discovering a bug at 100 percent.
  3. 3. Which is a PWA requirement for installation prompts?

    Browsers look for a manifest, icons and a secure origin (plus usually a service worker).
  4. 4. Why target live update bundles by native version range?

    The web code and the installed native layer must be compatible.

Summary

  • Choose between store apps, PWA or both; Capacitor makes the same code serve each.
  • Use testing tracks, TestFlight and staged rollouts; prepare listings, privacy details and a review demo account.
  • Avoid common rejections: thin web wrappers, vague permission texts, no account deletion, crashes.
  • PWAs need a manifest, HTTPS and a carefully versioned service worker.
  • Live updates change only the web layer; match bundles to native versions and keep rollback.

Next: Project: Notes App with Offline Sync