Getting CI/CD to work for a web app is usually painless. Getting it to work for a Capacitor app? That's where things get interesting. Between code signing, native build environments, and app store submission quirks, teams run into the same problems again and again. The good news is that most of these pitfalls are predictable — and avoidable if you know what to watch out for.
Capacitor 8 ships with Swift Package Manager as the default for iOS, targets Android SDK 36, and requires Node.js 22+. Whether you prefer an automated CLI migration, an AI-assisted upgrade, or full manual control, this guide walks you through all three approaches so you can pick the one that fits your project best.
Capacitor 8 makes Swift Package Manager the default on iOS, bumps the Android target to SDK 36, and upgrades to Kotlin 2.2. This guide covers three ways to bring your Capacitor plugin up to date — an automated CLI tool, AI-powered Capawesome Skills, or a fully manual upgrade.
If you've ever pushed a one-line bug fix and then waited days for app store approval, you know the frustration. Traditional mobile releases are slow, manual, and often out of sync with how fast your team actually ships code. Live updates — also known as Over-The-Air (OTA) updates — are changing that by letting Capacitor teams push web layer changes directly to users' devices, no app store submission required. In this post, we'll look at how live updates are reshaping mobile app deployment and why more teams are making the switch.
When building mobile apps in the cloud, it's common to need different configuration values depending on the environment. A staging build might use a different API endpoint than a production build, or you might need to inject API keys that shouldn't be committed to your repository.
With Capawesome Cloud, you can define environments, add environment variables and secrets, and customize the build stack using reserved variables—all without changing your source code.
Capacitor 8 made Swift Package Manager (SPM) the default dependency manager for new iOS projects. While SPM is the future of iOS dependency management, it still has some rough edges that can block real-world projects. In those cases, CocoaPods remains a solid alternative. This post covers when you might want to stick with CocoaPods and how to set it up.
Okta is a widely used identity platform that powers single sign-on (SSO) and user management for thousands of organizations. If you need to add Okta authentication to a Capacitor app, the OAuth plugin supports the Authorization Code flow with PKCE out of the box. In this guide, you'll learn how to register your app in Okta, implement sign-in and sign-out, manage tokens, and retrieve user profile data on Android, iOS, and web. This is also a great alternative to Ionic Auth Connect for teams looking for a lightweight, open approach.
Better Auth is an open-source, framework-agnostic authentication framework for TypeScript. Whether you're building with Ionic, Angular, React, or Vue, the Better Auth JavaScript SDK works out of the box in your Capacitor app — no special configuration needed. Since Capacitor apps are essentially web apps running in a native WebView, you can use the SDK directly for standard authentication flows. You only need Capacitor plugins when it comes to social login flows that require native functionality, like opening a browser window or using platform-specific sign-in APIs. This guide shows you how to set up mobile authentication with Better Auth in your Capacitor app using the Apple Sign-In, Google Sign-In, and OAuth plugins.
Keeping your users on the latest version of your app isn't just nice to have — it's critical for security, performance, and delivering the best experience. In this guide, you'll learn how to build a complete update delivery strategy for your Capacitor app by combining two plugins: the App Update plugin for native app store updates and the Live Update plugin for Over-The-Air (OTA) updates.
If you're using Over-The-Air (OTA) live updates to ship web layer changes to your Capacitor or Ionic app, the size of your update bundles directly affects how fast those changes reach your users. Large bundles mean slower downloads, higher data transfer costs, and a worse experience for users on mobile networks. The good news is that a few targeted optimizations can make a dramatic difference — one team we worked with reduced their average update from ~48 MB to ~9 MB. This guide walks through the most effective ways to reduce your live update bundle size.