u/genzits

We just shipped Capawesome Cloud Assist — a new AI surface inside the Cloud Console — and the first feature under it is Ask AI.

One click on any failed build or deployment turns the logs into a short summary with three sections: cause, explanation, and a suggested fix. The output is capped at ~400 words, so it stays a summary rather than a wall of text you'd have to re-read the logs to verify.

A few things that make it different from pasting logs into a general-purpose chatbot:

• Tuned for mobile build failures — Gradle/AGP mismatches, Xcode signing, Pod/SPM resolution, npm registry auth, App Store rejection notes
• Cached per failed job and shared across the org — the first teammate to click pays the cost, everyone else opens the dialog and sees the same answer instantly
• Only the failed job's logs are sent, opt-in, zero data retention, permission-gated to write access

It's free on all plans with build minutes, shipping as a beta.

Honest feedback welcome — especially from anyone who's had to debug a failed mobile build at 2am. What does your current workflow look like?

Source: https://capawesome.io/docs/blog/announcing-capawesome-cloud-assist/

We just published a long-form guide to Capacitor Live Updates on the docs blog. It's the version we wished existed when we started — a single place that walks through how OTA updates actually work, what choices you have to make, and what a production-ready setup looks like.

The structure:

• How OTA updates work under the hood — server paths, web vs. native layer, App Store and Google Play compliance.
• The three choices every team makes: update strategy (background, always latest, force, instant), versioning (per-bundle vs. per-channel), and delivery (zip vs. delta).
• Code signing for bundle authenticity.
• Best practices: automatic rollbacks, bundle size optimization, and gradual rollouts.
• A complete end-to-end example based on the DHBW VS app, including the actual CI/CD workflow.

The setup we land on as the recommended path: "Always Latest" strategy + versioned channels pinned in the native config + zip delivery + automatic rollback + code signing. It's the same stack a number of production apps are running.

If you're already shipping live updates with Capawesome, this should answer the "is the way I'm doing it actually right?" question — and call out a few subtle production traps (delta updates and content-hashed filenames is a fun one).

Happy to answer questions or take feedback in the comments.

We're launching Capawesome Platform today, which merges Capawesome Cloud (Live Updates, Native Builds, App Store Publishing) and our Insider SDKs into a single product with one website, one onboarding flow, and one pricing system.

Why: most teams wanted both, but had to sign up twice and pay on two invoices. Many devs only cared about Live Updates and didn't want to pay for Native Builds. There was no trial for Insider SDKs. And after we moved Live Updates to per-update pricing last year, the community kept asking for the simpler MAU-based model back.

Three pricing tracks:

• Platform: Live Updates + Native Builds + App Store Publishing + Automations + Insider SDKs in one cloud, from $19/mo
• Live Updates only: OTA updates for teams that handle their own native builds, from $9/mo
• SDKs only: All 22+ Insider SDKs ($249/mo Develop, $4,999 one-time Maintain, or Enterprise)

Key changes from community feedback:

• Unlimited Live Updates with MAU-based pricing (the old simpler model is back)
• No more commercial-use restriction on Insider SDKs — use the libraries in any project
• 14-day trial on every plan, including SDKs
• Yearly billing gets you two months free

Existing customers keep their current plans until they decide to switch.

Going forward, we're focusing on depth over breadth on the existing SDKs — more features, better docs, faster support — instead of shipping a new plugin every week.

https://capawesome.io

We just published a guide on getting AI coding agents to handle real Capacitor work — not just code completion, but the full lifecycle: scaffolding, plugin setup, builds, deploys, hotfixes, debugging, and major version upgrades.

The short version: general-purpose agents struggle with Capacitor because Xcode toolchains, Gradle versions, signing certificates, and plugin config aren't well represented in their training data. They often invent commands or skip steps. The fix is two pieces working together:

• Open source agent skills that teach the agent how to perform Capacitor tasks correctly (npx skills add capawesome-team/skills)
• Capawesome CLI for the actual build/sign/deploy capability

Once both are set up, the same agent can scaffold a new Ionic + React + Tailwind app, install plugins like NFC with all native config, build and submit to the App Store with one prompt, push hotfixes via Live Updates, and even debug iOS-specific build failures from Windows or Linux without committing throwaway changes to git.

Works with Claude Code, Cursor, Windsurf, GitHub Copilot, and any agent that follows the agentskills.io spec.

Happy to answer questions or hear what other workflows you'd want covered.

We just published the April 2026 update covering everything that shipped this month across Capawesome Cloud and our Capacitor plugins.

A few highlights:

• Capawesome Cloud API response times are now up to 5x faster after backend infrastructure improvements. Faster Live Update checks and a snappier Cloud Console for everyone, no action needed.
• We launched two free, browser-based signing tools: the Android Keystore Generator and the iOS Certificate Generator. Private keys stay on your device via the Web Crypto API, so no macOS, Keychain, or local tooling is required.
• SSO now requires domain verification before members can sign in, which also means SSO is no longer Enterprise-only — it's now available on the Business plan as well.
• A new Viewer role for read-only org access, and an improved webhook message layout for Discord, Slack, and Teams notifications.
• On the plugin side, Capacitor Speech Recognition v8.1.0 adds full on-device recognition (audio never leaves the device) and Audio Recorder v8.1.0 adds a uri option for startRecording(...) so you can save recordings to a custom path.

We also have something big planned for May that we'll share soon.

Disclosure: I work on Capawesome.

As of April 28, 2026, every app or app update submitted to App Store Connect must be built with Xcode 26 and the iOS 26 SDK (or matching SDKs for iPadOS, tvOS, visionOS, watchOS). Apps already on the store keep working, but the next update has to be on the new toolchain.

For Capacitor apps, this is purely a toolchain change. Capacitor itself works fine with Xcode 26 — there's no app-side migration needed.

I just published a short write-up on what the change means and how Capawesome Cloud customers are affected. Both default build stacks (macos-sequoia and macos-tahoe) already ship Xcode 26 by default, so most builds are already compliant. The only case where action is needed is if you've pinned XCODE_VERSION=16.x via a reserved environment variable — in that case, remove the override or bump it to 26.x.

Disclosure: I work on Capawesome.

Source: https://capawesome.io/blog/xcode-26-requirement-for-capacitor-apps/