Capawesome

Most common errors when implementing mobile OAuth 👇 We've seen all 5 of these in real production apps. 1. Opening the login flow in an embedded WebView instead of the system browser. That's exactly the pattern security teams flag OAuth for native apps to avoid. Users can't tell your embedded login screen from a fake one either. 2. Skipping PKCE because "it's just a mobile app." Your client secret is sitting inside a public binary. It was never a secret. That's exactly the problem PKCE exists to solve. 3. Treating decoded as verified. Base64-decoding the ID token and trusting email/sub from it — without checking the signature server-side. Decoding a JWT tells you what it claims. It doesn't tell you if it's real. 4. Storing tokens in plain SharedPreferences/UserDefaults instead of the Keychain/Keystore. Encrypted storage exists for a reason. 5. No refresh token logic. Users get silently logged out mid-session and blame your app instead of your auth flow. We built the Capacitor OAuth plugin to default to the right answer on all 5 — PKCE, system browser, no accidental footguns. https://lnkd.in/dq3d3q48

⚙️ Ever tried sending users to the right settings screen from your Capacitor app? The Capacitor Settings Launcher plugin makes it a one-liner: 📱 openAppSettings() — open your app's settings 🔔 openNotificationSettings() — open your app's notification settings 🤖 openAndroidSettings({ page }) — open ~40 Android system screens like Wi-Fi, Bluetooth, or Location The big use case: recovering from denied permissions. Neither Android nor iOS shows the permission prompt again after a denial — the only way forward is guiding users to your app's settings. openAppSettings() does exactly that. And one deliberate design decision: no private App-Prefs: URL scheme on iOS. The plugin only uses official Apple APIs, so you don't risk App Store rejection for deep-linking into system settings. Which settings screen does your app need to reach most often? Check it out 👇 https://lnkd.in/eqQNH3XK

👛 Introducing the Capacitor Wallet plugin! Add passes to Apple Wallet and Google Wallet directly from your Capacitor app — tickets, loyalty cards, coupons, boarding passes, and more. Here's what it offers: 🍎 Apple Wallet: Add passes with the native pass presentation UI 🤖 Google Wallet: Save passes using the official "Save to Wallet" flow ✅ Availability check: Verify passes can be added before showing the UI 📦 CocoaPods & SPM support on iOS 🔁 Always supports the latest Capacitor version Wallet passes are a great way to keep your users engaged beyond the app itself — your tickets and loyalty cards live right where users expect them. The plugin handles the presentation; you create and sign the passes on your server. What kind of passes are you planning to offer in your app? Check it out 👇 https://lnkd.in/ek76gp9P

🚀 The Capawesome June 2026 update is here — and it's all about reach. The headline: Capawesome Cloud now officially supports Apache Cordova. With Ionic Appflow winding down, Cordova teams finally get a real home for cloud builds and OTA updates: - Native iOS & Android builds in the cloud - Automated App Store & Google Play submissions - Over-the-air Live Updates via the new Cordova Live Update plugin But there's more across Cloud and our plugins: ☁️ Build stacks refreshed — the macos-tahoe stack now ships Xcode 26 🔑 Rotate API tokens directly in the Cloud Console 🔐 New Capacitor Vault plugin — encrypted, unlock-gated key/value storage and a drop-in alternative to Ionic Identity Vault 🗄️ SQLite — load custom Android extensions and read SQLite result codes from errors 📊 PostHog — error tracking via captureException plus automatic exception capture 🔥 Capacitor Firebase 8.3.0 — broader Firestore data types, filtered getCountFromServer, and new Remote Config helpers 📦 Live Update backports to Capacitor 6 and 7 Which of these will you try first? Check it out 👇 https://lnkd.in/eMA8aKKj

Who can relate?

When should you use SQLite in your mobile app? 🤔 Most apps start with simple key-value storage — and for settings, flags, and small preferences, that's exactly the right tool. But at some point, your data outgrows it. If your app has lists, relations, sync queues — anything you'd naturally model as tables — key-value storage won't cut it anymore. That's when SQLite comes in. It gives you a real relational database running directly on the device: ⚡ Fast SQL queries, even with thousands of rows 📴 100% offline — no network required, ever 🔐 Encryption at rest, so lost or stolen devices don't become data breaches 🔍 Built-in full-text search — ranked, tokenized results in milliseconds, no extra search library needed 🛡️ Atomic transactions — related writes either all succeed or all roll back And because SQLite stores data in a real database file on the filesystem, it's persistent by design — unlike browser storage, which the OS can evict under storage pressure. A simple rule of thumb: if you'd model it as tables on the server, model it as tables on the device. This applies whether you're building with Capacitor, Cordova, React Native, or native iOS and Android. How are you handling offline data in your mobile apps? 👇 #MobileDevelopment #SQLite #OfflineFirst #iOS #Android

Humans are wired to resist change. We can't fix evolution, but we can make migrating from Appflow to Capawesome feel a lot less scary. 😄 Appflow's shutdown date is locked in. If you're still shipping Capacitor, Ionic, or Cordova releases through Appflow, the question isn't if you'll migrate—it's when. The good news is that you don't have to wait until the last minute. We've put together a guide that walks through exactly what switching to Capawesome looks like: - What you need to migrate - How long it typically takes - What it costs - And why many teams are making the switch now instead of joining the inevitable deadline rush Our goal wasn't just to build an alternative to Appflow. We wanted the migration itself to be as straightforward as possible, so you can spend your time shipping features instead of rebuilding your release pipeline. If Appflow has been part of your workflow for years, hopefully this guide makes the next step a little less intimidating. Link in the comments 👇

Need to ship the same mobile app for multiple clients? White-labeling doesn't have to mean maintaining 10 different codebases. You can have a pipeline that ships a branded app for every customer you serve, without the fork-per-client spiral or the credential sprawl that usually comes with it. We can automate app branding, bundle IDs, signing, builds, and iOS and Android store-ready binaries, so your team can focus on building features instead of managing releases. Want to learn more? https://lnkd.in/dbZyGbZB #saas #mobiledev #devops #ios #android

snapAddy cut critical bug-fix deployment time from a week to under two hours — here's how they did it. They ship to 200,000+ users on iOS & Android so waiting on App Store review for every fix wasn't an option. So they decided to adopt Capawesome Cloud Live Updates: • RSA code signing — private key lives in Capawesome Cloud, not in CI secrets • Automatic rollback — if the app fails after an update, it reverts automatically • Silent vs. prompted updates — controlled per bundle via a custom property • GitHub Actions + Cloud Runners — one command triggers build, signing, and rollout • Channel-based distribution — separate streams per app version for gradual rollouts The results: → Fixes live in under 2 hours (was 5–7 days) → 95%+ of users on latest version within 48h → 3–4 releases/week instead of ~1/month → 40% fewer support tickets Full case study: https://lnkd.in/ddQPJM6B

3 files. 3 platforms. 3 chances to mess up your app version. Or just: npx capver sync You can also add this to your capacitor app https://lnkd.in/e-aUntza