r/capawesome • • Jul 13 '26

Announcing the Capacitor Electron Platform

Thumbnail
capawesome.io
21 Upvotes

r/capawesome • • 26d ago

New plugin: Native iOS tab bar with Liquid Glass for your Capacitor app

17 Upvotes

If you’ve opened your app on iOS 26 and your tab bar looks like it’s from 2019 next to every native app, this one’s for you.

@capawesome/capacitor-tab-bar renders a real UITabBar on top of the web view. On iOS 26 you get Liquid Glass. On older versions, the classic native tab bar. Your web content never knows the difference, the plugin extends the bottom safe area inset so nothing gets covered.

What you get:

  • SF Symbols or your own asset catalog images as icons

  • Badges

  • Custom selected/unselected colors (unselected is system-controlled on iOS 26, that’s Apple’s call)

  • Show it from launch via capacitor.config so there’s no flash before your web app loads

  • tabSelected event to hook into your router, selectTabById() to sync the other way

Ionic users: hide ion-tab-bar on iOS with one CSS rule, keep your Ionic router, wire the two events. The docs have an Angular example, same idea in React and Vue.

npm install u/capawesome/capacitor-tab-bar
npx cap sync

Free, open source, Capacitor 8+. iOS only for now, Android and web reject as unimplemented.

Two things to check before you file a bug: your viewport meta needs viewport-fit=cover, and if you use the splash screen plugin, call setTabs() and show() after SplashScreen.hide() instead of using the config, or the tab bar shows up over your splash.

https://capawesome.io/docs/sdks/capacitor/tab-bar/

If you ship this, post a screenshot. We want to see Liquid Glass on Capacitor apps in the wild. 💜


r/capawesome • • Sep 22 '26

Capawesome announces official partnership with Ionic

Thumbnail
capawesome.io
17 Upvotes

We just announced our official partnership with Ionic. As part of it, Ionic recommends Capawesome as its preferred migration partner for Appflow, Auth Connect, Identity Vault, and Secure Storage, which all reach end of life on December 31, 2027. From October 1, 2026, Appflow no longer allows creating new apps or changing plans.

Here's what we built together with Ionic for the migration:

  • Appflow now has an organization export, and the Capawesome CLI imports it with one command (apps:import). Apps, channels, environments, signing certificates, destinations, automations, and build numbers carry over. --dry-run shows the result without creating anything.

  • The Live Update SDK keeps Appflow's sync() and reload() API, so most apps change one dependency.

  • The Capacitor OAuth, Vault, SQLite, and Secure Preferences plugins (Capawesome Insiders) replace Auth Connect, Identity Vault, and Secure Storage. There's no cloud import for plugins, so this part is a code change, but the APIs map closely.

  • Two open source agent skills (ionic-appflow-migration and ionic-enterprise-sdk-migration) walk an AI coding agent through the migration.

You can run Appflow and Capawesome Cloud in parallel, so there's no cutover date to plan around. Ionic Portals keep their live updates through the Ionic Live Update Provider SDK.

Full details, the mapping tables, and the FAQ (including what happens to your Ionic contract) are in the post:

https://capawesome.io/blog/announcing-partnership-with-ionic/

If you're mid-migration or planning one, ask away. We'd like to hear what's missing.


r/capawesome • • Oct 10 '26

Google Play's DEX code optimization requirement and what Capacitor apps need

Thumbnail
capawesome.io
12 Upvotes

From February 2027, Google Play requires at least 25% obfuscation, optimization and shrinking for apps with more than 10 MB of DEX code (50 MB for games). A Capacitor app built from the default Android template fails this today, because the template sets minifyEnabled false and R8 never runs. Our production app reported 1% obfuscation in Play Console.

We wrote up what it takes to get a Capacitor app past the threshold, based on our own app with about 40 plugins:

  • minifyEnabled true with proguard-android-optimize.txt (the template's proguard-android.txt contains -dontoptimize, and AGP 9 rejects it anyway)

  • One keep rule you need in R8 full mode: -keep @interface com.getcapacitor.** { *; }. Without it the build passes and the app crashes on startup, because Capacitor's consumer rules keep the plugin classes but not the annotation types, so Bridge.getPermissionStates() hits a null. Tracked as ionic-team/capacitor#8589; Capacitor 8.5.2 added a null check that hides the crash but leaves checkPermissions() empty

  • -dontwarn rules for plugins that compile against optional backends with compileOnly (SQLite with SQLCipher or requery, for example)

  • How to sign a local release build with the debug keystore and read the percentages from r8.json inside the AAB before Play does

Disclosure: we are Capawesome, and the post links our Cloud product at the end, but everything above applies to any Capacitor app regardless of how you build it.

Source: https://capawesome.io/blog/google-play-dex-code-optimization-in-capacitor-apps/

If you have already enabled R8 in a Capacitor app, I would like to hear which plugins needed extra rules.


r/capawesome • • Nov 19 '25

Announcing Capawesome Cloud Native Builds

Thumbnail
capawesome.io
10 Upvotes

r/capawesome • • Sep 12 '26

Capacitor LLM plugin runs Apple Intelligence and Gemini Nano on the device

Thumbnail
capawesome.io
9 Upvotes

We just released a Capacitor plugin that prompts the language model built into the OS: Apple Intelligence on iOS through the Foundation Models framework, Gemini Nano on Android through ML Kit GenAI and AICore. It is part of Capawesome Insiders, so it is a paid plugin.

Why on-device: prompts and responses never leave the phone, there is no API key in the bundle, and there is no per-token cost. It also works offline.

The API:

  • getAvailability() with seven typed statuses (Android reports four, iOS five), and it never rejects

  • downloadModel() with progress on Android; iOS manages the download itself

  • Chats with instructions and context, generateText, streamText with a textChunk event, cancelGeneration

  • Limits: Android caps maxOutputTokens at 4096 and temperature at 1.0; both platforms have a context window around 4,000 tokens

Requirements: Capacitor 8, Android API 26 on a Gemini Nano-capable device (Pixel 9, Galaxy S25), iOS 26 with Xcode 26 on iPhone 15 Pro or later.

The post compares it with the Ionic local LLM plugin, the ML Kit GenAI Prompt plugin, and the Capgo plugin, based on what their READMEs document. Questions welcome.


r/capawesome • • Sep 10 '26

Why Directory.ExternalStorage fails on Android 11 in Capacitor apps

Thumbnail
capawesome.io
9 Upvotes

If your Capacitor app writes to Directory.ExternalStorage and it started failing once you targeted Android 11, that is scoped storage, and no permission brings the old behavior back. We wrote up what Android changed and what still works.

The short version:

  • Scoped storage arrived with Android 10 and became mandatory for apps targeting API level 30. requestLegacyExternalStorage is ignored from there on.

  • App-specific directories (Data, Cache, Library, External) still work everywhere without any permission.

  • Directory.Documents only shows files your own app created.

  • MANAGE_EXTERNAL_STORAGE is not the fix: Google Play reviews it against a dedicated policy and most apps do not qualify.

  • The supported path for user-chosen folders is a Storage Access Framework tree URI plus takePersistableUriPermission(), which survives restarts. Our File Manager plugin (Capawesome Insiders, paid) wraps that.

The post has a decision table for which directory or API to use for which need, and links the two ionic-team issues that are still open about this.

How are you handling shared storage on Android 11 and newer today?


r/capawesome • • Jul 15 '26

All of Google's ML Kit is now available in Capacitor: 21 open source plugins, one JavaScript API

9 Upvotes

Hey everyone!

We just finished shipping an extensive suite of ML Kit plugins for Capacitor: 21 plugins that wrap Google's ML Kit SDKs behind a single JavaScript API. Everything is open source and free.

The full list includes text recognition (OCR), barcode scanning, document scanner, translation, language identification, face detection, face mesh, object detection, pose detection, selfie/subject segmentation, digital ink recognition, entity extraction, smart reply, image labeling, and six GenAI plugins powered by Gemini Nano (prompt, summarization, proofreading, rewriting, image description, speech recognition).

The part we think is most interesting: everything runs on-device. No per-call API costs, works offline (after the initial model download), and user data never leaves the phone.

Some honest caveats:

- The GenAI plugins are Android-only for now, since Gemini Nano requires AICore-supported devices (recent Pixel, Samsung flagships, etc.)

- Most other plugins support Android and iOS, some also work on the Web. Each plugin's docs page lists supported platforms.

Docs: capawesome.io/docs/sdks/capacitor/mlkit

Happy to answer any technical questions, and if you build something with them, I'd honestly love to see it. Feedback and issues welcome on GitHub. 💜


r/capawesome • • May 29 '26

Capacitor 8.3.2 ships edge-to-edge and safe area support out of the box

Thumbnail
capawesome.io
9 Upvotes

For the last couple of years, doing edge-to-edge in Capacitor usually meant installing a third-party Android plugin and fighting with status bars covering your header. That changed quietly across three recent releases, so we wrote up the current state of things.

Why it matters now: Android 15 enforces edge-to-edge for apps targeting SDK 35, and Android 16 removed the opt-out entirely. Your WebView renders behind the system bars whether you like it or not.

What the framework fixed:

  • 8.3.0 — SystemBars uses native safe area insets and injects parallel --safe-area-inset-* CSS variables, sidestepping the old Android WebView (<140) env() bug

  • 8.3.1 — separate styling for the status bar and navigation bar

  • 8.3.2 — removed extra padding on older Android devices

The modern setup is small: upgrade to 8.3.2+, add viewport-fit=cover to your viewport meta tag, and apply the safe-area CSS variables to your edge content. Ionic users get most of it for free, and Tailwind users can use tailwindcss-safe-area. The Android Edge-to-Edge Support plugin still exists, but it's now a deliberate choice for apps that want to opt out of edge-to-edge, not a requirement.

Curious how others have been handling this — are you on 8.3.2+ yet, or still relying on the plugin?


r/capawesome • • Feb 10 '26

OAuth Plugin for Capacitor

Thumbnail
capawesome.io
9 Upvotes

r/capawesome • • 12d ago

October was a big month at Capawesome 💜

8 Upvotes

From new ways to ship updates to major improvements across our plugin ecosystem, here's what we've been working on:

🚀 Live Updates for Electron — ship web updates to desktop apps without rebuilding the native binary.

📦 Live Updates for Ionic Portals — bring the power of Capawesome Cloud to your Portals apps.

⚡ Multi-channel automations — publish a single web build to multiple channels with one automation.

🍎 A new native Tab Bar plugin — bring the iOS 26 Liquid Glass experience to your Capacitor app.

🔧 A new default build stack — with the latest Xcode environment.

And we've also published a guide to fix the Google Play DEX Code Optimization finding, which becomes a requirement in February 2027. Get ahead of the deadline before it becomes a release blocker.

Plus, plenty of improvements across File Transfer, SQLite, Haptics, Firebase, and more.

We've been building, shipping, and improving every day to make mobile development a little easier.

Here's everything that shipped in October 👇
https://capawesome.io/blog/2026-october-update/


r/capawesome • • Oct 13 '26

30 open source agent skills + 3 MCP servers for Capacitor, Ionic and Capawesome Cloud

8 Upvotes

If you use Claude Code, Cursor, Copilot, Codex or any agent that follows the Agent Skills spec, this is for you.

Tech moves fast, and what your coding agent learned about Capacitor last year is probably out of date. We built two things so it works from current docs and documented procedures instead of memory.

Agent skills. 30 of them, MIT licensed, in capawesome-team/skills. Each one is a documented procedure for a real task:

  • Create a Capacitor or Ionic app

  • Upgrade across major versions, step by step

  • Install and configure plugins for Android and iOS

  • Push notifications (FCM), in-app purchases

  • Native builds, live updates and store publishing with Capawesome Cloud

  • Migrate from Ionic Appflow or the Enterprise SDK

Install everything:

npx skills add capawesome-team/skills

Or just one:

npx skills add capawesome-team/skills --skill capacitor-app-upgrades

Claude Code users can also go through the plugin marketplace (claude plugin marketplace add capawesome-team/skills).

MCP servers. Three remote ones, nothing to install:

The skills detect a connected MCP server and use it for docs, otherwise they fall back to their bundled reference files and work offline.

Example prompt once installed: “Upgrade my Capacitor app from version 6 to version 8.” The agent picks the skill, applies the diffs, runs the commands.

Docs: https://capawesome.io/docs/ai/skills/

If you try it, tell us what worked and what didn’t. And if there’s a task you’d want a skill for, say so, PRs are welcome too.


r/capawesome • • Sep 24 '26

macOS Golden Gate build stack with Xcode 27 is now available on Capawesome Cloud

Thumbnail
capawesome.io
8 Upvotes

We just released a new build stack for Capawesome Cloud: macos-golden-gate, with macOS 27 and Xcode 27. Xcode 27 was already selectable on macos-tahoe via XCODE_VERSION, and this is the stack built around it.

On October 1, it becomes the default for all iOS and Android builds. Until then, macos-tahoe stays the default, so nothing changes unless you opt in.

The main thing to prepare for: apps built with the iOS 27 SDK must adopt the UIScene lifecycle. Otherwise the build succeeds, but the app fails at launch.

  • Capacitor: update to 8.5 and run npx cap migrate

  • Cordova: cordova-ios 8 already uses the scene lifecycle

  • Native UIKit apps: add a scene delegate (see Apple's TN3187)

Other changes:

  • Node.js 20 and Xcode 26 aren't available on the new stack

  • Android 37 (needed for Capacitor 9) is now on every build stack

  • macos-sequoia is deprecated

If you need more time, select macos-tahoe for your builds and automations.

Happy to answer questions, especially about the UIScene migration.


r/capawesome • • Aug 17 '26

Awesome Capacitor list, 100+ plugins/tools/guides in one place

8 Upvotes

We just updated the Awesome Capacitor list 🌟

100+ plugins, tools, guides, videos, AI tools, demo apps — everything the Capacitor ecosystem has to offer, in one place.

Bookmark it, star it, share it, use it.

PRs welcome if we missed something.


r/capawesome • • Aug 06 '26

This is by far Capawesome's most underrated feature

8 Upvotes

Did you know you can turn any successful build into a link and QR code, testers scan it and install straight to their phone.

No need of a Capawesome account, no TestFlight review wait, no "hey can you send me the APK" email thread.

It works for Android and iOS, Capacitor/Cordova apps and native Kotlin/Swift apps. Set an expiration, revoke it whenever.

And the best part: you can plug it straight into CI, drop a QR code into every pull request so reviewers can test the actual build, not just the diff

Read more: https://capawesome.io/blog/share-mobile-app-builds-with-testers/


r/capawesome • • Jul 22 '26

Ever wondered how Live Updates work? Here's what happens under the hood.

8 Upvotes

You already know Live Updates let you ship fixes to your app in real time, no app store review. But do you actually know how it works? It's simpler than most people think, and understanding it will help you use it better.

The two layers

Every Capacitor app has two layers. The web layer: your HTML, CSS, and JS, loaded into the web view. The native layer: the compiled code (Java/Kotlin, Swift) plus your native plugins.

Here's the key detail: your web files are never compiled into the app binary. They ship inside the app package (the classic www/ folder), but they stay plain files. And plain files can be replaced.

Where your app actually loads from

The web view doesn't load your app from the internet. It loads it from a local origin served out of the app bundle, on Android via WebViewAssetLoader (https://localhost/), on iOS via WKURLSchemeHandler (app://localhost/). By default, that content is the www/ folder that was bundled when the binary was built.

What a Live Update actually does

A live update simply changes which folder those requests are served from:

  1. The SDK downloads a new bundle from the server

  2. Writes it to a local directory inside the app's sandbox

  3. Registers it as the next bundle to use

  4. On the next launch (or immediately, if you prefer), the web view serves your app from the new bundle instead of the built-in www/

That's it. No binary patching, no code injection. Just swapping the folder the web view reads from.

The constraint that is also the feature

Because only the web layer changes, live updates are limited to binary-compatible changes: HTML, CSS, JS, and assets. Add a plugin or touch native code, and you need a store release. But that same constraint is why it's fully compliant with both stores: Apple explicitly permits downloading interpreted code that doesn't change the app's primary purpose, and Google Play exempts code running in a webview from its self-update restrictions.

What the platform adds on top

The mechanism is simple. Running it in production is where it gets interesting: bundles delivered via global CDN, channels so the right devices get the right version, staged rollouts, one-click rollbacks when something goes wrong, and code signing so only you can publish updates to your app (the SDK verifies the signature before applying a bundle).

Full deep dive here: capawesome.io/blog/how-live-updates-for-capacitor-work/

Questions welcome: happy to go deeper on any part.


r/capawesome • • Feb 27 '26

New guide: How to use TypeORM with Capacitor and SQLite

Thumbnail
capawesome.io
8 Upvotes

We just published a guide on using TypeORM with Capacitor for local SQLite storage in mobile apps.

If you're familiar with TypeORM on the backend, the same decorator-based workflow works in Capacitor apps too. The SQLite plugin includes a built-in SQLiteConnection class that plugs directly into TypeORM's DataSource, so there's no separate adapter to install.

The guide walks through the full setup:

  • Configuring the DataSource with the Capacitor driver

  • Defining entities with decorators (@Entity, @Column, @ManyToOne, etc.)

  • Using repositories for CRUD operations

  • Wrapping multiple operations in transactions

  • Writing and running migrations for production

This is the third guide in our ORM series — we also have guides for Drizzle ORM and Kysely if you prefer a more SQL-first approach.

Source: https://capawesome.io/blog/how-to-use-typeorm-with-capacitor-and-sqlite/

Happy to answer any questions.


r/capawesome • • Feb 25 '26

Guide: Using Drizzle ORM with Capacitor and SQLite for type-safe database operations

Thumbnail
capawesome.io
8 Upvotes

We just published a guide on integrating Drizzle ORM with the Capacitor SQLite plugin using the new @capawesome/capacitor-sqlite-drizzle adapter.

If you've been writing raw SQL strings in your Capacitor app and manually mapping query results, this adapter lets you use Drizzle's type-safe query builder instead. You define your schema in TypeScript and get autocompletion, compile-time checks, and a familiar SQL-like API.

The guide walks through the full setup:

  • Installing the adapter and connecting it to the SQLite plugin

  • Defining tables with sqliteTable (columns, foreign keys, defaults)

  • Running type-safe CRUD queries (insert, select, update, delete)

  • Loading related data with Drizzle's relational query API

  • Using transactions for atomic multi-table operations

  • Setting up schema migrations with Drizzle Kit, including bundler configuration for non-Node environments

The adapter itself is a thin bridge — it translates Drizzle's query methods into Capacitor SQLite plugin calls, so there's minimal overhead.

Source: https://capawesome.io/blog/how-to-use-drizzle-orm-with-capacitor-and-sqlite/

Happy to answer any questions if you run into issues setting it up.


r/capawesome • • Feb 24 '26

Practical tips for setting up in-app purchases with Capacitor on iOS and Android

Thumbnail
capawesome.io
8 Upvotes

We just published a collection of practical tips for getting in-app purchases and subscriptions working in Capacitor apps using the Purchases plugin.

If you've tried to get IAP working before, you know the code is only half the battle. The setup on Apple's and Google's side trips up a lot of developers — missing agreements, incomplete product configurations, or not knowing how to properly test before going live.

The post covers:

  • Apple Developer agreements and App Store Connect business setup

  • Creating products and subscriptions in App Store Connect and Google Play Console

  • Handling unfinished transactions on app launch

  • Adding a restore purchases button

  • Choosing consistent product IDs across platforms

  • Server-side notification handling for renewable subscriptions

  • Testing on both iOS (Sandbox + StoreKit) and Android (license testing)

Source: https://capawesome.io/blog/tips-for-setting-up-in-app-purchases-with-capacitor/

If you've run into any gotchas during your own IAP setup, feel free to share — always helpful to hear what others have dealt with.


r/capawesome • • Feb 23 '26

Capawesome Cloud now supports automated builds from Git events

Thumbnail
capawesome.io
8 Upvotes

We just launched Automations for Capawesome Cloud. You can now automatically trigger builds whenever you push to a branch or create a tag — no CLI or external CI/CD pipeline required.

Before this, you either had to trigger builds manually from the Console or set up an external pipeline (GitHub Actions, GitLab CI, etc.) to call our API. That meant maintaining another pipeline, managing extra credentials, and paying for CI/CD minutes on top of what you were already paying for with Capawesome Cloud.

With Automations, everything stays inside Capawesome Cloud. Here's what you can configure per automation:

  • Branch or tag triggers with pattern matching (e.g. main, v*, release/*)

  • Commit message filtering to skip builds for non-code changes

  • Full build settings — signing certificates, environments, store destinations, and live update channels

  • Automatic webhook registration on your Git provider

You also get email notifications and can track everything in the Console.

We'd love to hear how you plan to use this or if there's anything we should add.


r/capawesome • • Feb 21 '26

New guide: How to sign in with Google using Capacitor

Thumbnail
capawesome.io
8 Upvotes

We just published a step-by-step guide on integrating Google Sign-In into a Capacitor app using our Google Sign-In plugin.

The guide covers the full setup from scratch:

  • Creating a Google Cloud project and OAuth client IDs for Android, iOS, and web

  • Configuring the plugin on each platform (Info.plist setup on iOS, Credential Manager on Android)

  • Implementing the sign-in flow with code examples

  • Handling the redirect callback on web

  • Requesting additional OAuth scopes

  • Verifying the ID token on the backend using google-auth-library

If you've been looking for a straightforward way to add Google authentication to your Capacitor app, this should save you some time.

Happy to answer any questions.


r/capawesome • • Jan 04 '26

Square Mobile Payments Plugin for Capacitor

Thumbnail
capawesome.io
8 Upvotes

r/capawesome • • Dec 17 '25

Updating to Capacitor 8.0

Thumbnail
capawesome.io
8 Upvotes

r/capawesome • • Oct 06 '26

Downloading files in the background in Capacitor apps (what survives backgrounding, OS kills and force-quits)

7 Upvotes

We just published a guide on background downloads, and it answers the question we get all the time: why does my download die when the user locks the phone?

Short version: a fetch runs in the web view, inside your app's process. iOS suspends that process a few seconds after backgrounding, and the download goes with it. Background-mode plugins don't help, the download still lives in the same process.

The Capacitor File Transfer plugin hands the transfer to the OS instead: a background URLSession on iOS, a dataSync foreground service on Android.

What survives what:

  • Backgrounded: keeps running on both.

  • OS kill for memory: iOS finishes it and delivers on relaunch. Android interrupts it, resumable from the bytes on disk.

  • Force-quit: canceled on both. iOS retries on relaunch if maxRetries > 0.

The guide also covers the AppDelegate hook you need on iOS, why listeners belong at app startup, and how to rebuild your download list after a relaunch.

https://capawesome.io/blog/how-to-download-files-in-the-background-in-capacitor/


r/capawesome • • Sep 17 '26

Need native calendar functionality in a Capacitor app?

7 Upvotes

If you're building a Capacitor app that needs to interact with the user's native calendar, we just released a new Calendar plugin that might save you some work.

It supports both iOS and Android and covers things like:

  • Creating and managing events

  • Recurring events

  • Updating individual occurrences of recurring events

  • Reminders

  • Listening for calendar changes

The last one is particularly useful if your app needs to stay in sync when the user changes something directly in their calendar.

Docs: https://capawesome.io/docs/sdks/capacitor/calendar/

We also wrote a bit more about the implementation and the use cases here: https://capawesome.io/blog/announcing-the-capacitor-calendar-plugin/