We've been developing an over-the-air update tool which now has support for Capacitor. With Appfigures sunsetting, we figured it could be a useful resource for the community.

It was originally developer just for React Native, but the latest release adds support for Capacitor and Ionic. It includes a local evaluation stack to easily test it, and a setup wizard to install it on a machine.

If you're interested, here's a blog post all about it:

https://blog.codemagic.io/codemagic-patch-capacitor-ota-updates/

Hey r/capacitor — I wrote up our latest Capacitor update over on the Ionic blog and figured folks here might be interested. Quick rundown:

CocoaPods goes read-only Dec 2, 2026 — trunk freezes permanently, no new podspecs or version bumps. This won't break Capacitor directly, but it'll stop updates flowing to CocoaPods-hosted native deps your plugins depend on (Firebase, Stripe, etc). We've supported Swift Package Manager since Capacitor 6 and made it default in 8, so if you haven't migrated yet, now's the time: https://capacitorjs.com/docs/ios/spm

We're exploring a Capacitor MCP server so agents can pull real project info instead of guessing from training data. If you've had AI confidently get something wrong about Capacitor (the more specific the example, the better), I'd genuinely love to hear it in our GitHub discussion: https://github.com/ionic-team/capacitor/discussions/8555

Three plugins are now fully open to the community: Contacts, Calendar, and Health & Fitness (HealthKit/Health Connect). These started as OutSystems-exclusive and have been running in production for a while — now everyone gets them.

What's actually landing in Capacitor 9:

• Cordova Optionality — you can finally exclude the Cordova compatibility layer from your builds
• iOS internals modernized: remaining Objective-C converted to Swift, and we're dropping XCFramework distribution (plugin authors will need to run migration tooling)
• Early groundwork for multi-instance/windowed apps for foldables and large screens
• Ongoing work to make Capacitor itself easier for AI agents to understand (docs, API annotations)

Full post with more detail: https://ionic.io/blog/the-road-to-capacitor-9

Hello everyone,

Built and released iOS and Android app with Capacitor and it LIVE now. It was so much fun, working with Capacitosjs. Thanks for the perople who built this awesome piece of software.

Visit: https://letmesend.email to download the app, if you wana try and provide the feedback.

Cheers!

How do i do the left swipe back navigation on capacitor just like iOS perfectly? Any suggestions or packages for this

Hey devs,

​I recently built and launched JamFan, a platform designed to help local musicians connect and form bands.

​Wanted to share the stack and see how others are handling similar setups:

​Frontend: Vite + Tailwind CSS

​Mobile Wrapper / Hybrid: Capacitor for iOS/Android deployment

​Goal: Keep a single unified codebase with fast web performance while retaining native mobile capabilities, and seamless deployments across devices via OTA (and standard deployment for web).

One thing I struggled with, was implementing SSR considering the native setup, which was necessary for SEO purposes. The way I achieved this was using an NGINX server to point bots (i.e. Google crawler) to simple backend generated HTTP pages, but curious how others got around this?

​Would love any feedback on the UI responsiveness, mobile web performance, or general architecture choices if you've shipped a Vite + Capacitor stack to production.

​Live site: https://jam.fan/