Is Capacitor healthy?

As of May 6, 2026, Capacitor is actively maintained by the Ionic team, has a recent 8.3.1 release, about 15.6k GitHub stars, and about 9.6 million @capacitor/core downloads in the previous month.

When is Capacitor a bad fit?

Capacitor is a weaker fit for teams that want only native-language development, stock native UI everywhere, heavy native rendering, advanced games, AR-first products, constant high-volume native bridge traffic, or native-binary changes that must ship without store review.

How does Capgo improve a Capacitor app?

Capgo adds live updates, rollback, channels, maintained Capacitor plugins, and cloud native builds. It helps teams bypass the store review queue for allowed web bundle updates while keeping native binary changes in the normal app review process.

Capacitor app guide

What is a Capacitor app?

Q: What is a Capacitor app?

A Capacitor app is a real iOS, Android, or web app that runs a modern web application inside a native container and uses plugins to access native device APIs.

A Capacitor app is a web app shipped inside real native iOS and Android projects. Your interface is HTML, CSS, and JavaScript running in a WebView, while Capacitor plugins bridge that web code to native device APIs like camera, storage, push notifications, biometrics, files, and location. Capgo turns that architecture into a release advantage with live updates, maintained plugins, and native cloud builds.

Browse Capgo plugins Bypass review for web fixes

Cross-platform mobile app development across iOS, web frameworks, and Android

How it works

Capacitor is not a UI framework. It is the native runtime under the app. Ionic, React, Vue, Angular, Svelte, Tailwind, or your own design system can render the UI inside the WebView.

1. Web app

You build the product with normal web tooling, then output static assets. Capgo can update those assets after approval.

2. Native shell

Capacitor places those assets inside iOS and Android projects. Capgo Build helps when those binaries must be rebuilt.

3. Plugin bridge

JavaScript calls plugins, and plugins call Swift, Kotlin, Java, Objective-C, or web fallbacks. Capgo maintains plugins for common native needs.

Positive parts

One web codebase can ship to iOS, Android, and the web.
With Capgo live updates, allowed HTML, CSS, and JavaScript fixes can bypass the store review queue after the native app is approved.
Teams keep React, Vue, Angular, Svelte, or plain web tooling instead of rewriting in Swift and Kotlin.
Native access comes through plugins, and custom Swift, Kotlin, Java, or Objective-C code can still be added.
Existing modern web apps can adopt Capacitor without changing UI frameworks.
Capacitor keeps native iOS and Android projects in the repo, which makes platform debugging and SDK work more explicit.
Most Cordova plugins can still work, which helps older Ionic and Cordova teams migrate gradually.
Capgo adds maintained Capacitor plugins, live-update channels, rollback, and cloud builds on top of the Capacitor runtime.

Negative parts

The UI runs in a WebView, so poor web performance becomes poor mobile performance.
Large or frequent data transfers across the JavaScript-to-native bridge add overhead.
Teams still need some native app knowledge for signing, store review, permissions, Gradle, Xcode, and SDK upgrades.
Native projects are source files, so major upgrades can require careful manual changes.
The plugin ecosystem is broad, but not every community plugin has the same maintenance quality, which is why maintained Capgo plugins matter for production apps.
It is usually not the best fit for fully native UI, advanced games, AR-heavy apps, or apps with constant low-latency native data flows.

Best fit, bad fit

Capacitor fits best when

SaaS, fintech, healthcare, education, marketplace, and internal tools with strong web product needs.
Existing web apps that need app-store distribution without a full native rewrite.
Teams that want web, iOS, and Android handled by mostly the same frontend team.
Apps with normal native needs: camera, push, auth, files, biometrics, payments, location, and deep links.
Products that benefit from live web bundle updates after store approval.
Teams that want Capgo Build to handle repeatable iOS and Android builds, signing, and release artifacts without maintaining every native CI detail.

Choose another stack when

High-end 3D games, video editors, AR-first products, or apps driven by heavy real-time native rendering.
Teams that want to write only Swift, Kotlin, Java, or Dart.
Products where every screen must be built from stock platform-native controls.
Apps that depend on a niche native SDK when no maintained plugin exists and the team cannot maintain one.
Teams that expect native-code, permission, entitlement, or store-policy changes to bypass app review. Capgo live updates are for the web bundle, not native binary changes.

Why Capgo matters

Native-only apps wait on a new binary, signing, rollout, and app review for every visible change. Capacitor gives you a web bundle inside the native app. Capgo turns that bundle into a faster release path while still keeping native-code changes in the proper app-store review flow.

Live updates that skip the review queue

Capgo ships allowed web bundle changes directly to users after the native app is approved, so copy fixes, UI fixes, JavaScript patches, and remote configuration do not wait days for App Store or Play Store review.

Rollback, channels, and controlled rollout

Capgo lets teams release to beta users, percentages, channels, or specific versions, then roll back quickly when a web update is bad.

Maintained Capacitor plugins

Capgo keeps a large plugin catalog for production Capacitor apps, covering common native needs such as auth, storage, purchases, media, device APIs, and enterprise migrations.

Capgo Build for native releases

When native code really changes, Capgo Build helps produce iOS and Android builds, manage signing, follow logs, and ship store-ready artifacts from the same Capacitor project.

Use Capgo live updates Build native releases

History and lineage

Capacitor came from the Ionic team, the same company behind Ionic Framework. It inherits the core WebView and native-plugin pattern from Cordova and PhoneGap, but modernizes the developer experience around npm packages, TypeScript, Swift, Kotlin, committed native projects, and PWA support.

Cordova and PhoneGap

Capacitor inherits the hybrid-app idea: a native shell, a WebView, and a bridge from JavaScript to native APIs.

Late 2017

The Ionic team started exploring a modern alternative to Cordova as Ionic expanded beyond only mobile UI.

2019

Capacitor was first released as Ionic moved toward a web-native runtime for iOS, Android, desktop, and PWAs.

2022

Ionic joined OutSystems. Ionic later said Capacitor remains central to OutSystems mobile work and open source support.

2023-2026

Ionic moved Capacitor to a more predictable release cadence and began a public backlog health reset.

Maintenance and health

Capacitor is maintained by the Ionic team, with community contributors around the ecosystem. The project is healthy, but not perfect: Ionic publicly acknowledged backlog debt in February 2026 and started a cleanup process for old issues and pull requests.

Snapshot checked May 6, 2026. Counts move over time.

Latest stable release

8.3.1

Published April 16, 2026

GitHub stars

15.6k

ionic-team/capacitor

Forks

1.2k

Public GitHub repo

Monthly downloads

9.6M

@capacitor/core, Apr 6-May 5 2026

Practical reading

Treat Capacitor as a strong default when your product is web-first and mobile matters. Use Capgo when release speed matters: live updates for web fixes, rollback for bad releases, channels for staged rollout, maintained plugins for native features, and Capgo Build when a real native binary must be produced. Native-only apps do not get that live-update path; every fix waits for a fresh build and store review.

Build native apps with Capgo Start with Capgo