Today we're launching Capawesome Platform — Capawesome Cloud and Insider SDKs unified under one brand, one website, one onboarding flow, and one pricing system. It's the biggest change we've ever made, and almost every detail of it came directly from your feedback. Welcome to the new capawesome.io.
Yesterday, April 28, 2026, Apple's new SDK requirement went into effect. Every app submitted to App Store Connect now has to be built with Xcode 26 and the iOS 26 SDK (or the matching SDKs for iPadOS, tvOS, visionOS, and watchOS). If you're shipping a Capacitor app, here's what changed — and why most Capawesome Cloud customers don't need to lift a finger.
Version 4.7.0 of the Capawesome CLI is now available. Building on the 4.5.0 release, this update brings a unified command for creating live updates, new app management commands for linking repositories and transferring apps, ad hoc environment variables for builds, and source map detection to keep your production bundles clean.
One of the most common questions we get is: "What's the difference between using Live Updates and server.url in Capacitor?"
Many developers use the server.url configuration option to load their app's web content from a remote server in production — even though it was never designed for that.
In this post, we'll break down what each approach does, how they compare, and why Live Updates are the better choice for production apps.
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.
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.
Version 4.5.0 of the Capawesome CLI is here, and it's packed with new features that have been added since the 4.0.0 release. The highlights include full command line management of signing certificates and app store destinations, a streamlined build workflow, and interactive prompts that make the CLI easier to use than ever.
Sometimes you need direct control over which Live Update channel a specific device uses. With forced channel assignments, you can now override the SDK-selected channel on any device — whether you're debugging an issue, testing a new release, or managing a customer's device manually.
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.