<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dayana Jabif on Medium]]></title>
        <description><![CDATA[Stories by Dayana Jabif on Medium]]></description>
        <link>https://medium.com/@dayanajabif?source=rss-f05e27e8a50e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EluEku9-7KSw5KXzGPAOgg.jpeg</url>
            <title>Stories by Dayana Jabif on Medium</title>
            <link>https://medium.com/@dayanajabif?source=rss-f05e27e8a50e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:51:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dayanajabif/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Convert Lovable Apps to iOS and Android Apps]]></title>
            <link>https://medium.com/learn-ionic-framework/convert-lovable-app-to-ios-and-android-apps-1b0b5eb44a78?source=rss-f05e27e8a50e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b0b5eb44a78</guid>
            <category><![CDATA[capacitorjs]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ios-development]]></category>
            <category><![CDATA[lovable]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Dayana Jabif]]></dc:creator>
            <pubDate>Fri, 26 Jun 2026 00:00:55 GMT</pubDate>
            <atom:updated>2026-10-06T18:01:05.818Z</atom:updated>
            <content:encoded><![CDATA[<p>You can convert a <a href="https://lovable.dev/">Lovable</a> app into native iOS and Android apps with Capacitor and build both in the cloud, so you need neither a Mac nor Xcode nor Android Studio. Lovable itself publishes to the web only, but the code it generates is a standard React + Vite project, which is exactly what <a href="https://capacitorjs.com/">Capacitor</a> wraps into a native app. In this guide, we take a Lovable expense tracker called Spendly from the Lovable editor to a signed app on a real iPhone, add a native camera feature, set up the Apple Developer and Google Play accounts and signing certificates, and push a fix over the air with <a href="https://capawesome.io/cloud/">Capawesome Cloud</a> Live Updates.</p><p><strong>No prior mobile experience required: every command and tool is explained as if you’ve never opened a terminal.</strong></p><p><em>This post was originally published at </em><a href="https://capawesome.io/blog/convert-lovable-app-to-mobile-app/"><em>https://capawesome.io </em></a><em>on June 26, 2026.</em></p><p>This post has a companion video that walks through the entire process in real time, including the parts where things break and how to fix them:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F_5l-wiVYkVY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D_5l-wiVYkVY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F_5l-wiVYkVY%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/605b1b91695cd22fa7d01f82ac8707e8/href">https://medium.com/media/605b1b91695cd22fa7d01f82ac8707e8/href</a></iframe><p><strong>Key takeaways:</strong></p><ul><li>Lovable only publishes to the web, but its code is a normal web app, and Capacitor turns a web app into iOS and Android apps without rewriting it.</li><li>You don’t need a Mac, Xcode or Android Studio: Capawesome Cloud builds the iOS and Android apps for you in 2–5 minutes, from Windows, Linux or macOS.</li><li>Ask Lovable for a single-page app: new Lovable apps use server-side rendering by default since May 13, 2026, and a native app needs a plain static build.</li><li>Once the app is on phones, small fixes go out over the air in minutes with Live Updates; only new native features like the camera need a new build and store review.</li><li>Publishing costs $99 per year for Apple and $25 one-time for Google Play, and you can do the whole guide on the free 14-day Capawesome Cloud trial.</li></ul><h3>What You’ll Build</h3><p>To keep things concrete, we’ll use a sample app called Spendly, a mobile-first expense tracker built with Lovable. It lets you add expenses, see a running total, and (once we add the camera) snap a photo of a receipt when logging a transaction.</p><p>The steps apply to every Lovable app; Spendly is only the example.</p><p>By the end, you’ll have:</p><ul><li>A native iOS and Android app built entirely in the cloud: no Mac, no Xcode, no Android Studio required</li><li>The iOS app installed and running on a real iPhone device</li><li>The Android app installed and running on a real Android device</li><li>iOS and Android developer accounts configured to submit your app for review in the App Store and Google Play Store</li><li>A working camera feature that only a real native app can offer</li><li>Live Updates set up, so you can ship changes without going through app review every time, including a real fix we’ll push over the air</li></ul><h3>Build iOS and Android Apps Without a Mac</h3><p>The traditional way to build a mobile app requires a Mac with Xcode for iOS and a fully configured Android Studio for Android. That’s a huge amount of setup, and if you’re on Windows or Linux, iOS is off the table.</p><p>We’re going to skip almost all of that. <a href="https://capawesome.io/cloud/native-builds/">Capawesome Cloud Native Builds</a> builds your iOS and Android apps on Apple computers in the cloud, signs them, and hands you back an installable app in a few minutes, from any operating system.</p><p>That changes the prerequisites dramatically:</p><ul><li><strong>You do <em>not</em> need Xcode or Android Studio</strong> to build and ship your app. The cloud does it.</li><li><strong>You <em>only</em> need them if you want a simulator</strong>, a virtual phone that runs on your computer’s screen. That’s optional, and (fair warning) it’s a lot more setup. We’ll point out where it fits in, but the main path in this guide never touches them.</li></ul><p>Check the <a href="https://capawesome.io/blog/convert-lovable-app-to-mobile-app/#prerequisites">Prerequisites</a> to see what you need before you start.</p><h3>Step 1: Build Your App in Lovable</h3><p>If you already have a Lovable app, skip to Step 2. If you’re starting fresh, here’s how Spendly was created.</p><p><a href="https://lovable.dev/">Lovable</a> is an AI app builder. You describe the app you want in plain English, and it generates a working React app you can preview and refine in your browser, no coding required.</p><p>Here’s the <a href="https://capawesome.io/docs/assets/images/posts/convert-lovable-app-to-mobile-app/lovable-prompt/">exact prompt</a> we used to generate Spendly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fBdzqOA5pu-3i8-w.png" /></figure><p>Keep it a simple single-page app</p><p>For the smoothest path to mobile, explicitly ask Lovable for a single-page app, like the prompt above does. New Lovable apps are server-rendered by default, and asking for a single-page app is what gets you the dist folder Capacitor wraps into a native app.</p><p>✅ <strong>Success:</strong> Your app previews and works inside the Lovable editor.</p><h3>Step 2: Export to GitHub</h3><p>To work with your app on your own computer (and so Capawesome Cloud can build from it later), you first need the code in a GitHub repository. Lovable can push it there for you.</p><ol><li>In the Lovable editor, click the <strong>Upgrade</strong> button in the top-right corner.</li><li>Click <strong>Git</strong> on the left menu and then the <strong>Github</strong> option.</li><li>Authorize Lovable (create a free GitHub account here if you don’t have one).</li><li>Link your github account to this Lovable project.</li><li>Lovable will create a new repository and push your app into it automatically.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sBkTZm86ChsX5oNN.png" /></figure><p>After it finishes, you’ll have a repo at an address like github.com/YOUR-USERNAME/spendly.</p><p>If you got lost here, watch the video for the detailed step by step.</p><p>✅ <strong>Success:</strong> Visiting github.com/YOUR-USERNAME/spendly shows your app&#39;s code.</p><h3>Step 3: Run Your App Locally</h3><p>Now download the code to your computer and make sure it runs. “Cloning” means copying the repository (the project on GitHub) onto your machine.</p><p>Open VS Code, start a terminal with <strong>Terminal → New Terminal</strong>, and run these one at a time (replace YOUR-USERNAME):</p><pre>git clone https://github.com/YOUR-USERNAME/spendly.git <br>cd spendly <br>npm install <br>npm run dev</pre><ul><li>git clone ...: downloads your code into a new spendly folder.</li><li>cd spendly: moves into that folder.</li><li>npm install: downloads all the libraries your app depends on.</li><li>npm run dev: runs the app on your computer so you can open it in a browser.</li></ul><p>Then open the project in VS Code: <strong>File → Open Folder</strong>, select the spendly folder. Any new terminal you open is already inside it, so you can skip cd spendly from here on.</p><p>The terminal prints a local address. Open it in your browser. Lovable apps typically run on http://localhost:8080, but use whatever address your terminal shows (it may differ).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UtrFKOY4X_XT2CoE.png" /></figure><p>✅ <strong>Success:</strong> Spendly opens in your browser showing its UI.</p><p>Press Ctrl + C in the terminal to stop the app when you&#39;re ready to continue.</p><h3>Step 4: Add Capacitor to Your Lovable App</h3><p>Capacitor is the bridge that turns your web app into a real native mobile app. It wraps your existing code in an iOS and Android shell, no rewrite needed.</p><p>Install Capacitor and set it up:</p><pre>npm install @capacitor/core @capacitor/cli <br>npx cap init</pre><p>npx cap init asks three questions. Answer them like this:</p><p><strong>App Package ID</strong>com.spendly.app</p><p>A unique ID for your app, written like a web address in reverse (your website’s domain, then the app name). It can’t be changed after you publish to the stores.</p><p><strong>Web assets directory</strong></p><p>The folder your built app lands in. <strong>For Lovable single-page apps this is </strong><strong>dist.</strong></p><p>This creates capacitor.config.ts:</p><p>Pick a Package ID you own</p><p>Your Package ID (Apple calls it the bundle ID, Google the application ID) must be unique across the App Store and Google Play, so two apps can never share one. In the companion video we picked one that was already taken and had to change it later, which means editing it in several files inside ios/ and android/ and rebuilding. Save yourself the detour: base it on a domain you own (e.g. com.yourcompany.spendly) from the start.</p><p>Now build your web app, add the iOS and Android projects, and copy the app into them:</p><pre>npm run build <br>npm install @capacitor/ios @capacitor/android <br>npx cap add ios<br>npx cap add android <br>npx cap sync</pre><ul><li>npm run build produces the dist/ folder (Capacitor needs it before you add the platforms).</li><li>npx cap add ios / android create the ios/ and android/ folders, each a complete native project.</li><li>npx cap sync copies your built web app into both. You&#39;ll run it again after every change.</li></ul><p>Your project now looks roughly like this:</p><pre>spendly/<br>├── android/          ← native Android project<br>├── ios/              ← native iOS project<br>├── dist/             ← your built web app<br>├── src/              ← your Lovable app code<br>├── capacitor.config.ts<br>└── package.json</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/0*--E7yWCmcx393-Yy.png" /></figure><p>No CocoaPods needed</p><p>If you’ve followed older Capacitor tutorials, you may have seen a step to install a tool called CocoaPods for iOS. You don’t need it. Since Capacitor 8, iOS dependencies are handled automatically by <a href="https://capawesome.io/blog/how-to-migrate-a-capacitor-app-to-spm/">Swift Package Manager</a>, which comes with the project.</p><p>✅ <strong>Success:</strong> ios/ and android/ folders appear, and the terminal shows Sync finished.</p><h3>Step 5: Check .gitignore</h3><p>Capawesome Cloud builds from your GitHub repository, which means the ios/ and android/ folders must be uploaded to GitHub. A .gitignore file lists what Git should leave out of the upload, and a common mistake is accidentally listing those folders there.</p><p>npx cap add already put a .gitignore inside each platform folder that leaves out only temporary build files, not the project itself, so you usually don&#39;t need to change anything. Confirm:</p><ul><li>The .gitignore in your project&#39;s main folder lists node_modules and dist (the cloud rebuilds dist itself, so it doesn&#39;t belong on GitHub). Lovable&#39;s default already does this.</li><li>The ios/ and android/ folders are not listed. They need to be on GitHub.</li></ul><p>✅ <strong>Success:</strong> Running git status shows the new ios/ and android/ folders as ready to upload (not ignored).</p><h3>Step 6: Commit and Push</h3><p>Upload this milestone to GitHub so the cloud can build from it ( commit records the change, push uploads it):</p><pre>git add .<br>git commit -m &quot;Add Capacitor and native iOS/Android platforms&quot;<br>git push</pre><p>✅ <strong>Success:</strong> Your GitHub repo now shows the ios/ and android/ folders.</p><h3>Step 7: Connect Capawesome Cloud</h3><p>Everything in this section is done in the Capawesome Cloud Console, with no terminal needed.</p><ol><li><strong>Sign up and create an organization.</strong> Go to <a href="https://console.cloud.capawesome.io/">console.cloud.capawesome.io</a> and create an <strong>organization</strong> (your workspace). All plans include a <strong>14-day free trial</strong>.</li><li><strong>Create an app.</strong> On the <a href="https://console.cloud.capawesome.io/organizations/_/apps">Apps</a> page, select your organization, click <strong>Create App</strong>, give it a name (e.g. Spendly), and click <strong>Create</strong>. Open the app and copy its app ID. You&#39;ll paste it into your config when we set up Live Updates.</li><li><strong>Connect your GitHub repository.</strong> Open the <a href="https://console.cloud.capawesome.io/apps/_/git">Git</a> page for your app.</li></ol><ul><li>Under <strong>Git Providers</strong>, select <strong>GitHub</strong> and click <strong>Connect</strong> to authorize access.</li><li>Under <strong>Git Repositories</strong>, choose the repository owner, select your spendly repo, and click <strong>Save</strong>.</li></ul><p>For the full connection flow and permissions, see the <a href="https://capawesome.io/docs/cloud/integrations/github/">GitHub integration docs</a>.</p><p>✅ <strong>Success:</strong> Your app in Capawesome Cloud shows your GitHub repo connected, and you have your app ID saved.</p><h3>Step 8: Create Developer Accounts</h3><p>To install on a real iPhone and to publish, you need developer accounts. This is a one-time setup with real timelines. Start it early.</p><h3>Apple Developer Program: $99/year</h3><p>Enroll at <a href="https://developer.apple.com/programs/enroll/">developer.apple.com/programs/enroll</a> for $99 per year. Individual accounts are usually approved within two days. Registering as a company also needs a D-U-N-S number, a free business identifier from Dun &amp; Bradstreet that takes about a week to get.</p><h3>Google Play Console: $25 one-time</h3><p>Register at <a href="https://play.google.com/console/signup">play.google.com/console/signup</a> for a one-time $25 fee. Identity verification usually completes within a few hours.</p><p>Full walkthrough: <a href="https://capawesome.io/blog/how-to-create-apple-developer-and-google-play-accounts/">How to Create Your Apple Developer and Google Play Developer Accounts</a>.</p><p>✅ <strong>Success:</strong> Your Apple Developer account is active (and Google Play, if you’re targeting Android).</p><h3>Step 9: Generate Signing Certificates</h3><p>Apple and Google only accept signed apps, and iOS won’t install an unsigned build on a real device either. Signing is a digital stamp that proves the app comes from you, and each platform has its own files for it:</p><ul><li><strong>iOS:</strong> a certificate (the stamp itself) plus a provisioning profile (a list of which app, and which devices, that stamp may be used for). You need one pair for installing on your own iPhone (called <em>development</em>) and one pair for TestFlight and the App Store (called <em>distribution</em>). Both are created the same way.</li><li><strong>Android:</strong> a single keystore file that holds the stamp.</li></ul><p>This is where most first-timers get stuck, but you can create everything in your browser, no Xcode or Android Studio required:</p><p>Then upload them to Capawesome Cloud once, in the Console:</p><ol><li>Open your app and go to the <strong>Certificates</strong> page.</li><li>Click <strong>Create Certificate</strong>, choose the platform, and upload the files:</li></ol><ul><li><strong>iOS:</strong> your .p12 certificate (with its password) and your .mobileprovision provisioning profile.</li><li><strong>Android:</strong> your keystore file (with its keystore password, key alias, and key password).</li></ul><p>3. Give it a recognizable name (e.g. Production iOS Certificate) and save.</p><p>Every future build picks the certificate up automatically, so you store nothing on your machine.</p><p>Step-by-step guides:</p><ul><li><a href="https://capawesome.io/docs/cloud/native-builds/certificates/ios/">iOS signing certificates</a></li><li><a href="https://capawesome.io/docs/cloud/native-builds/certificates/android/">Android signing certificates</a></li><li><a href="https://capawesome.io/blog/ios-certificates-and-provisioning-profiles-explained/">iOS Certificates and Provisioning Profiles Explained</a>.</li></ul><p>Remember that in the video this is shown step by step.</p><p>Every iPhone has a unique identifier called a UDID. Look yours up with the free <a href="https://capawesome.io/tools/ios-udid-finder/">iOS UDID Finder</a>, register it in your Apple Developer account, and include it in the development provisioning profile. That lets you install a development build directly on your phone. The easiest alternative is TestFlight, set up in Step 12.</p><p>✅ <strong>Success:</strong> Your certificates are uploaded to Capawesome Cloud.</p><h3>Step 10: Build Your Native App in the Cloud</h3><p>Start a cloud build straight from the connected repository, all from the Console:</p><ol><li>Open your app and go to the <strong>Builds</strong> page.</li><li>Click <strong>Build from Git</strong>.</li><li>Select your <strong>Git reference</strong> (the main branch, which is the version of your code the cloud should build), the <strong>Platform</strong> (iOS or Android), and the <strong>Build Type</strong>:</li></ol><ul><li><strong>iOS → Development</strong> (signed with your iOS <em>development</em> certificate, with your iPhone included in the provisioning profile): to install directly on your own device.</li><li><strong>iOS → App Store</strong> (signed with your iOS <em>distribution</em> certificate): for TestFlight and the App Store (you can’t install this one straight onto a device).</li><li><strong>Android → Release</strong> (signed with your Android keystore): for Google Play. For a quick test on any Android device, <strong>Android → Debug</strong> needs no certificate.</li></ul><p>4. Pick the matching <strong>certificate</strong>, then click <strong>Build</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*NLekk2nJj882IChT.png" /></figure><p>Builds typically finish in 2–5 minutes. When a build fails, the Console’s <a href="https://capawesome.io/docs/cloud/assist/">Ask AI</a> explains the cause and a fix in plain English.</p><p>Want a free, unsigned build to try first?</p><p>On the <strong>Build Type</strong> dropdown, choose <strong>iOS Simulator</strong> or <strong>Android Debug</strong>. Neither needs a certificate. The iOS one only runs in a virtual iPhone, and the Android one installs on any Android phone, so they’re a good first end-to-end test. Full reference: <a href="https://capawesome.io/docs/cloud/native-builds/setup/">Getting Started with Native Builds</a>.</p><p>Watch the full Console walkthrough for each platform:</p><p>✅ <strong>Success:</strong> Your build completes in the Console with a downloadable app file (an IPA for iOS, an APK or AAB for Android).</p><h3>Step 11: Install the App on Your iPhone</h3><p>Time to hold Spendly in your hand. The simplest paths, all without Xcode:</p><ul><li><strong>TestFlight (iOS):</strong> push the build to TestFlight from Capawesome Cloud <a href="https://capawesome.io/cloud/app-store-publishing/">App Store Publishing</a>, then install it from the TestFlight app on your iPhone. Internal testers don’t wait for review.</li><li><strong>Direct install:</strong> install a development build straight onto a registered device from the Capawesome Cloud Console.</li><li><strong>Google Play Internal Testing (Android):</strong> share a link and testers install from the Play Store immediately, no review.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ar-Z1bLsAUdu-v2-.png" /></figure><p>Full guide: <a href="https://capawesome.io/blog/how-to-distribute-ios-and-android-apps-to-testers/">How to Distribute iOS and Android Apps to Testers</a>. Console walkthrough:</p><p>Prefer a local simulator/emulator? (the heavier path)</p><p>If you’d rather test in a virtual phone on your computer, you <em>can</em> install <a href="https://apps.apple.com/app/xcode/id497799835">Xcode</a> (Mac only) and/or <a href="https://developer.android.com/studio">Android Studio</a>, then run npx cap open ios / npx cap open android and press the Run button. Be warned: these are large downloads and a lot more configuration. The cloud + real-device path above is faster and works on any OS, which is why it&#39;s our main recommendation.</p><p>✅ <strong>Success:</strong> Spendly launches on your iPhone.</p><h3>Step 12: Deploy to Testers</h3><p>Installing on your own phone is great, but to get the app to other testers you send it to a store destination: TestFlight on iOS or a Google Play testing track on Android. You set the destination up once in the Console and then deploy builds to it.</p><p>This is walked through end-to-end in the companion video</p><p>Creating both destinations involves a fair amount of clicking through Apple and Google’s consoles. The <a href="https://youtu.be/_5l-wiVYkVY">companion video</a> demonstrates the whole flow in real time, including the credentials, a couple of errors, and the fixes. This section is the written map; the linked docs below have the click-by-click detail.</p><p>The two-step pattern is the same for both platforms:</p><ol><li><strong>Create a store destination</strong> (the target + its credentials).</li><li><strong>Create a deployment</strong> of a signed build to that destination.</li></ol><h3>TestFlight (iOS)</h3><p>Create an <strong>Apple App Store</strong> destination on the <strong>Destinations</strong> page of your app. Using the Apple ID + Password method, you&#39;ll provide:</p><ul><li><strong>Team ID</strong>: from your Apple Developer Membership details.</li><li><strong>Apple App ID</strong>: the <em>Apple ID</em> property from the <strong>App Information</strong> section in App Store Connect (create the app there first, using your registered bundle ID).</li><li><strong>Apple ID</strong> + an <strong>app-specific password</strong>: a separate password Apple lets you create for tools like this one, on your <a href="https://appleid.apple.com/">Apple ID account page</a>.</li></ul><p>Then create an <strong>iOS → App Store</strong> build signed with your distribution certificate and deploy it to that destination. Submissions are uploaded to TestFlight automatically. (You can also tick the deploy option on the build itself so a successful build ships to TestFlight in one go.)</p><p>Full detail: <a href="https://capawesome.io/docs/cloud/app-store-publishing/destinations/apple-app-store/">Apple App Store &amp; TestFlight Destination</a>.</p><h3>Google Play Internal Testing (Android)</h3><p>Create a <strong>Google Play Store</strong> destination with:</p><ul><li><strong>Track</strong>: Internal for internal testing.</li><li><strong>Package Name</strong>: your Android application ID (the same bundle ID).</li><li><strong>Release Status</strong>: Draft for the very first release (lets you finish setup in the console before it goes live).</li><li><strong>JSON Key File</strong>: a file that lets Capawesome Cloud upload to Google Play on your behalf. You create it in the Google Cloud Console as a “service account”, then invite that account as a user in the Google Play Console and give it release permissions.</li></ul><p>Then create an <strong>Android → Release</strong> build (Google Play rejects <strong>Debug</strong> builds) and deploy it to the destination. It appears under <strong>Testing → Internal testing</strong> in the Google Play Console, where you add tester emails.</p><p>Full detail: <a href="https://capawesome.io/docs/cloud/app-store-publishing/destinations/google-play-store/">Google Play Store Destination</a>.</p><p>For the bigger picture (automatic submissions after a build, all tracks, and Firebase App Distribution), see <a href="https://capawesome.io/docs/cloud/app-store-publishing/setup/">Getting Started with App Store Publishing</a> and our <a href="https://capawesome.io/blog/how-to-distribute-ios-and-android-apps-to-testers/">How to Distribute iOS and Android Apps to Testers</a> guide.</p><p>✅ <strong>Success:</strong> Your build is live on TestFlight and/or the Google Play Internal track, and your testers have been invited.</p><h3>Step 13: Add a Native Feature: The Camera</h3><p>A Capacitor plugin is a small add-on that lets your app’s code use a real phone feature: camera, fingerprint or face unlock, location, and <a href="https://capawesome.io/docs/sdks/capacitor/">50+ more</a>. This is what separates a real native app from a website in a wrapper.</p><p>We’ll add the <a href="https://capacitorjs.com/docs/apis/camera">Camera plugin</a> so users can photograph a receipt when adding an expense. If you later want to crop that receipt photo or shrink it before upload, <a href="https://capawesome.io/blog/how-to-take-and-edit-photos-in-a-capacitor-app/">How to Take and Edit Photos in a Capacitor App</a> covers the plugins for that.</p><pre>npm install @capacitor/camera &amp;&amp; npx cap sync</pre><h3>Declare Camera Usage</h3><p>Both platforms require you to declare <em>why</em> your app uses the camera, or it crashes when the camera opens. You only do this once.</p><p><strong>iOS</strong>: open ios/App/App/Info.plist and add inside the top-level &lt;dict&gt;:</p><p>ios/App/App/Info.plist</p><pre>&lt;key&gt;NSCameraUsageDescription&lt;/key&gt;<br>&lt;string&gt;Spendly uses the camera to let you photograph receipts.&lt;/string&gt;</pre><p><strong>Android</strong>: open android/app/src/main/AndroidManifest.xml and add inside the &lt;manifest&gt; tag:</p><p>android/app/src/main/AndroidManifest.xml</p><pre>&lt;uses-permission android:name=&quot;android.permission.CAMERA&quot; /&gt;</pre><h3>Use the Camera in Your App</h3><p>Open the file that holds your “Add Transaction” form (it lives somewhere under src/; ask Lovable which file if you&#39;re unsure), and add this function plus a button:</p><p><strong>Capacitor handles the permission dialog</strong></p><p>You don’t write any code to ask for camera access. The first time a user taps the button, Capacitor shows the system “Allow camera access?” prompt, using the message you wrote in Info.plist.</p><p>✅ <strong>Success:</strong> Your code calls the Camera plugin and the project syncs without errors.</p><p><strong>Hundreds more plugins, including Capawesome Insiders SDKs</strong></p><p>The camera is one example. Capawesome maintains a large library of <a href="https://capawesome.io/docs/sdks/capacitor/">free, open-source Capacitor plugins</a>, and for more advanced needs there’s <a href="https://capawesome.io/insiders/">Capawesome Insiders</a>: premium, production-ready SDKs built and maintained by official Ionic Developer Experts, with priority support. Insiders covers native features like <a href="https://capawesome.io/docs/sdks/capacitor/nfc/">NFC</a>, <a href="https://capawesome.io/docs/sdks/capacitor/biometrics/">Biometrics</a>, <a href="https://capawesome.io/docs/sdks/capacitor/bluetooth-low-energy/">Bluetooth Low Energy</a>, and <a href="https://capawesome.io/docs/insiders/">more</a>. Most Capawesome Cloud plans already include a couple of Insider SDKs.</p><h3>Step 14: Add Live Updates (OTA)</h3><p>Normally, every change to a native app (even a one-word typo fix) has to go through app store review, which can take days. <a href="https://capawesome.io/cloud/live-updates/">Capawesome Cloud Live Updates</a> let you push changes to the web part of your app (the screens, styling, logic and images Lovable generated) over the air, straight to users’ devices in minutes, with no review required.</p><p><strong>Add the plugin in your first release</strong></p><p>Adding a plugin requires a fresh native build and another store review. So install Live Updates now, before you have updates to ship. That way you’re never stuck waiting on review when you need to push a fix. (We’ll use exactly this capability in Step 16.)</p><p>Install and configure the plugin:</p><pre>npm install @capawesome/capacitor-live-update@latest<br>npx cap sync</pre><p>Add the plugin settings to capacitor.config.ts, pasting in the app ID you copied in Step 7:</p><pre>import type { CapacitorConfig } from &#39;@capacitor/cli&#39;;<br><br>const config: CapacitorConfig = {<br>  appId: &#39;com.spendly.app&#39;,<br>  appName: &#39;Spendly&#39;,<br>  webDir: &#39;dist&#39;,<br>  plugins: {<br>    LiveUpdate: {<br>      appId: &#39;00000000-0000-0000-0000-000000000000&#39;,<br>      autoUpdateStrategy: &#39;background&#39;,<br>      readyTimeout: 10000,<br>      autoBlockRolledBackBundles: true,<br>    },<br>  },<br>};<br><br>export default config;</pre><ul><li>autoUpdateStrategy: &#39;background&#39;: the app checks for updates when it opens, downloads them silently, and applies them the next time it opens. No prompts, no extra code.</li><li>readyTimeout + autoBlockRolledBackBundles: safety nets that <a href="https://capawesome.io/docs/cloud/live-updates/rollbacks/">automatically undo</a> a broken update, so a bad release can&#39;t leave users with an app that won&#39;t start.</li></ul><p>A quick word on channels: a <a href="https://capawesome.io/docs/cloud/live-updates/channels/">channel</a> is like a named mailbox for updates. Each installed app checks one mailbox, and you can use different ones for different audiences, for example staging for testers and production for everyone else. We&#39;re not setting one here, so the plugin uses your app&#39;s built-in default channel, which is where we&#39;ll deliver the update in Step 16.</p><p>The safety net needs your app to report “I started fine” as early as possible, which is what ready() does. In a Lovable app, open src/main.tsx and add near the top:</p><pre>import { LiveUpdate } from &#39;@capawesome/capacitor-live-update&#39;;<br><br>void LiveUpdate.ready();</pre><p>Then sync:</p><pre>npx cap sync</pre><p>✅ <strong>Success:</strong> The Live Update plugin is installed, configured with your app ID, and ready() is called on startup.</p><h3>Step 15: Rebuild the Native App in the Cloud</h3><p>We added two plugins (Live Update and Camera) and a new permission. Those are native changes, so they need a fresh native build. A Live Update alone can’t deliver them. First commit and push your changes:</p><pre>git add .<br>git commit -m &quot;Add Live Updates and Camera plugin&quot;<br>git push</pre><p>Then trigger a new build exactly like in Step 10: in the Console, open the <strong>Builds</strong> page → <strong>Build from Git</strong> → select main, your platform, the signed build type, and your certificate → <strong>Build</strong>.</p><p>Install this new build on your iPhone (TestFlight or direct install, as in Step 11). Your phone now runs a version of the app that includes the camera and can receive live updates.</p><p>✅ <strong>Success:</strong> The updated build with the camera installs and runs on your iPhone.</p><h3>Step 16: Fix the Status Bar via Live Update</h3><p>Look closely at the app on your iPhone. There’s a good chance the very top, your header or title, is tucked underneath the status bar (the clock and battery), or behind the notch. The bottom looks fine; the top is cut off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*p5endSWfuMtgOsJZ.png" /></figure><p>This happens because Capacitor draws your app across the <em>entire</em> screen, including behind the status bar and the notch. The part of the screen those cover is called the safe area, and the phone tells your app how big it is through built-in CSS values named env(safe-area-inset-top), -bottom, -left and -right. Your app has to add that much space itself.</p><p>Why the bottom often looks right but the top doesn’t</p><p>Many Lovable apps already add env(safe-area-inset-bottom) at the bottom, so that side is handled. The top headers usually use a fixed amount of space (like pt-6) that ignores the safe area, so they slip under the status bar.</p><p>First, confirm the &lt;meta name=&quot;viewport&quot;&gt; line in index.html includes viewport-fit=cover (Lovable apps usually already do; it&#39;s what switches the safe-area values on):</p><pre>&lt;meta name=&quot;viewport&quot; content=&quot;width=device-width, initial-scale=1, viewport-fit=cover&quot; /&gt;</pre><p>Then add the safe-area space to the top of each page header. The trick is max(): keep the original spacing in the browser, and grow to the safe area on phones that need it:</p><pre>- &lt;header className=&quot;... px-5 pt-6 pb-2&quot;&gt;<br>+ &lt;header className=&quot;... px-5 pt-[max(1.5rem,env(safe-area-inset-top))] pb-2&quot;&gt;</pre><p>Do this for each screen’s top header. If a header has a colored or gradient background, this is exactly what you want: the background still fills the screen edge-to-edge, and only the <em>content</em> shifts down below the status bar.</p><p><strong>Let Lovable do the edit</strong></p><p>You can ask Lovable: <em>“The app content runs under the status bar at the top on mobile. Add </em><em>env(safe-area-inset-top) to the top padding of each page header using </em><em>max(), keeping the existing padding as the minimum.&quot;</em></p><h3>Ship the Fix with a Web Build</h3><p>This fix only touches styling (no new plugin, nothing native), so we can push it straight to the installed app without a new native build or a trip through app review.</p><p>A live update is created with a <strong>Web Build</strong>. It works exactly like the iOS and Android builds you already did, except you pick <strong>Web</strong> as the platform. It’s the same Builds page, fully in the Console, no terminal.</p><p>First, push your fix to GitHub so the cloud can build from it:</p><pre>git add .<br>git commit -m &quot;Fix top safe area&quot;<br>git push</pre><p>Then, in the Console:</p><ol><li>Open the <strong>Builds</strong> page and click <strong>Build from Git</strong>.</li><li>Select your main branch and choose <strong>Web</strong> as the <strong>Platform</strong>, then click <strong>Build</strong>. (Web builds run your npm run build in the cloud in a few seconds.)</li><li>When it finishes, <strong>deploy</strong> that build to your app’s default channel. Since we didn&#39;t set up a custom channel in Step 14, that&#39;s the one your installed app checks automatically.</li></ol><p>You can watch it on the <a href="https://console.cloud.capawesome.io/apps/_/deployments">Deployments</a> page, and roll back to a previous build from there anytime.</p><p>Channels are how the right update reaches the right app</p><p>A web build is deployed to a channel, and each installed app checks one channel. Every app comes with a default channel, which is what we use here. Once you have real users on several app versions, <a href="https://capawesome.io/docs/cloud/live-updates/channels/#versioned-channels">versioned channels</a> make sure each update only reaches the app versions it <a href="https://capawesome.io/docs/cloud/live-updates/binary-compatible-changes/">works with</a>. (See also <a href="https://capawesome.io/blog/announcing-capawesome-cloud-web-builds/">Web Builds</a>.)</p><p>Watch the full Live Updates Console walkthrough:</p><p><a href="https://youtu.be/rF1yxzR8tnE">https://youtu.be/rF1yxzR8tnE</a></p><p>Full guides:</p><ul><li><a href="https://capawesome.io/docs/cloud/live-updates/setup/">Getting Started with Live Updates</a></li><li><a href="https://capawesome.io/blog/capacitor-live-updates-guide/">Capacitor Live Updates: The Complete Guide to OTA Updates</a></li></ul><p><strong>Force-close to trigger the update during testing:</strong></p><p>With the background setting from Step 14, the app checks for updates when it opens (and when you come back to it, if the last check was over 15 minutes ago). While testing, fully close and reopen the app, wait ~15–30 seconds, then open it once more to see the change applied.</p><p>✅ <strong>Success:</strong> The header now sits below the status bar, fixed on your device without rebuilding the native app or going through review.</p><h3>Step 17: Prepare Your App Store Listing</h3><p>Your app is built, installable, and you can already push instant updates. What remains before it goes live on the public stores is mostly paperwork. Apple and Google both want a complete listing before you can submit: an icon, screenshots (Apple insists on iPhone 6.9-inch captures), a name and description, a privacy policy URL even for free apps, an age rating, and the data-collection disclosures. <a href="https://capawesome.io/blog/how-to-prepare-your-app-store-listing/">How to Prepare Your App Store Listing</a> walks through each item with the exact sizes.</p><h3>What’s Left to Submit</h3><p>This guide got you all the way to a signed, installable app with live updates wired in. To publish, you still need to:</p><ol><li><strong>Complete Google Play’s closed testing period</strong> (personal accounts created after Nov 13, 2023): at least 12 testers for 14 consecutive days before you can request production access. iOS has no equivalent. <a href="https://capawesome.io/blog/11-steps-to-get-your-web-app-on-the-app-store/#step-8-complete-google-plays-closed-testing-period">Details here</a>.</li><li><strong>Submit for review.</strong> In App Store Connect, assign your build and click Submit for Review (Apple review: ~3–5 days). For Google Play, apply for production access after closed testing (review: ~3–7 days). Capawesome Cloud <a href="https://capawesome.io/cloud/app-store-publishing/">App Store Publishing</a> can automate both submissions with one click, or automatically on every successful build via <a href="https://capawesome.io/docs/cloud/automations/setup/">Automations</a>.</li></ol><p>Our companion guide covers this end of the journey in full detail: <a href="https://capawesome.io/blog/11-steps-to-get-your-web-app-on-the-app-store/">Convert a Web App to a Mobile App in 11 Steps</a>.</p><h3>Common Errors and Fixes</h3><p>Setting this up for the first time almost always involves a little back-and-forth. Several of these came up live in the companion video, which is a good thing, because you get to see exactly how to fix them. Here are the ones you’re most likely to hit:</p><ul><li><strong>Could not find the web assets directory: ./dist</strong> (when running npx cap add or npx cap sync). You ran the command before building. Run npm run build first so the dist/ folder exists, then retry. If your app builds into a folder with a different name, make sure webDir in capacitor.config.ts matches it.</li><li><strong>“This App ID … is not available” / bundle ID already taken</strong> (registering the App ID in Apple). Bundle IDs are globally unique. Pick a reverse-domain ID based on a domain you control (e.g. com.yourcompany.spendly).</li><li><strong>iOS build fails after changing the bundle ID.</strong> If you change the bundle ID in Apple but not in your project (or vice versa), they no longer match and the build fails. The bundle ID in your native project must equal the App ID registered in Apple. Find-and-replace it across ios/ and android/, commit, and rebuild.</li><li><strong>“Google Play Android Developer API has not been used in project … or it is disabled.”</strong> Open the link in the error to the Google Cloud Console, enable the API, wait a moment, and re-run the deployment.</li><li><strong>“APK has been signed in debug mode.”</strong> Google Play won’t accept a debug-signed build. Create an <strong>Android → Release</strong> build signed with your keystore, then deploy that.</li><li><strong>Deployment rejected: version already exists.</strong> Both stores reject a build whose version number they already have. Increase your app’s version number, create a new build, and deploy that one. To have the number increase on its own, see <a href="https://capawesome.io/blog/introducing-capver/">Introducing CapVer</a>.</li></ul><p>When a <strong>build</strong> fails, the Console keeps full logs, and <a href="https://capawesome.io/docs/cloud/assist/">Ask AI</a> turns the error into a plain-English cause and fix. For deployment issues, see <a href="https://capawesome.io/docs/cloud/app-store-publishing/troubleshooting/">App Store Publishing Troubleshooting</a> and <a href="https://capawesome.io/docs/cloud/live-updates/troubleshooting/">Live Updates Troubleshooting</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VEOP9IQMvSvrI4Zq.png" /></figure><h3>Can Lovable publish my app to the App Store or Google Play directly?</h3><p>No. Lovable publishes to the web only, as its own <a href="https://lovable.dev/faq/capabilities/mobile/publish-app-store-google-play">mobile FAQ</a> states. To reach the stores, export the code to GitHub, add Capacitor, and build the native iOS and Android apps yourself or in the cloud, which is what this guide does. Your Lovable project stays the single codebase; the native shell is generated around it.</p><h3>My Lovable app is server-rendered. Do I need to rebuild it as a single-page app?</h3><p>Not from scratch, but Capacitor does need a folder with an index.html that contains the whole app, and a server-rendered app doesn&#39;t produce one. Ask Lovable to switch the existing project to a single-page app (or to a static build); it keeps your screens and logic and only changes how the app is packaged. Then point webDir at the folder it produces.</p><h3>Why does my build fail with “Could not find the web assets directory: ./dist”?</h3><p>You ran npx cap add or npx cap sync before building the web app, so the dist/ folder Capacitor expects doesn&#39;t exist yet. Run npm run build first, then retry. Double-check that webDir in capacitor.config.ts matches the folder your build actually produces.</p><h3>Do I have to install Xcode or Android Studio to follow this guide?</h3><p>No, for the main path. The entire build-and-install flow (cloud builds, TestFlight, direct device installs) works without either, since Capawesome Cloud builds on its own Apple computers. Xcode and Android Studio are only needed if you want a virtual phone on your own computer, which the guide calls out as optional and considerably heavier to set up.</p><p>No. Adding a plugin changes the native part of the app, so it needs a fresh native build and a new store submission; a Live Update can only change the web part. That is why the guide installs the Live Update plugin in the very first release: by the time you need to ship a fix, the app already knows how to receive it.</p><p>Because most Lovable-generated apps already add safe-area space at the bottom with env(safe-area-inset-bottom), but top headers typically use a fixed amount of space that ignores the status bar. Since Capacitor draws your app across the whole screen, the header needs the same treatment on top ( max() combined with env(safe-area-inset-top)) that the bottom likely already has.</p><h3>Try Capawesome Cloud</h3><p>Build your Lovable app for iOS and Android in the cloud, push fixes over the air, and submit to the stores from one place, on any operating system.</p><p><a href="https://capawesome.io/">Try Capawesome Cloud Free</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mUrTGPOYDqSkLi48H-16pA.png" /></figure><h3>Final Thoughts</h3><p>If your Lovable app is already a single-page app, start at Step 4 and let the cloud handle the native side. If it is server-rendered, switch it to a single-page app first, because nothing else in this guide works until it does.</p><p>Add the Live Update plugin to your very first release, even with nothing to ship yet. Every other feature you can add with a new native build, but a missing Live Update plugin means another store review before you can push your first over-the-air fix.</p><p>From here, finish publishing with the store listing, Google’s closed testing and the submission itself in <a href="https://capawesome.io/blog/11-steps-to-get-your-web-app-on-the-app-store/">Convert a Web App to a Mobile App in 11 Steps</a>, let <a href="https://capawesome.io/docs/cloud/automations/setup/">Automations</a> turn every git push into a build, a store submission and a live update, and browse the <a href="https://capawesome.io/docs/sdks/capacitor/">Capacitor plugin library</a> for biometrics, push notifications and geolocation.</p><p>Got stuck somewhere? The <a href="https://discord.gg/VCXxSVjefW">Capawesome Discord server</a> is active and friendly, so drop your question there. And subscribe to the <a href="https://capawesome.io/newsletter/">Capawesome newsletter</a> to stay up to date on new plugins, Cloud features, and guides like this one.</p><p><em>Originally published at </em><a href="https://capawesome.io/blog/convert-lovable-app-to-mobile-app/"><em>https://capawesome.io</em></a><em> on June 26, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b0b5eb44a78" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learn-ionic-framework/convert-lovable-app-to-ios-and-android-apps-1b0b5eb44a78">Convert Lovable Apps to iOS and Android Apps</a> was originally published in <a href="https://medium.com/learn-ionic-framework">Learn Ionic Framework</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[11 Steps to Get Your Web App on the App Store]]></title>
            <link>https://medium.com/learn-ionic-framework/11-steps-to-get-your-web-app-on-the-app-store-5299d80a67d0?source=rss-f05e27e8a50e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5299d80a67d0</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ios-development]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Dayana Jabif]]></dc:creator>
            <pubDate>Thu, 04 Jun 2026 00:00:32 GMT</pubDate>
            <atom:updated>2026-06-10T17:46:51.426Z</atom:updated>
            <content:encoded><![CDATA[<p>You have a web app. Maybe you built it yourself, maybe you vibe-coded it with an AI assistant over a weekend. It works, you like it — and now you want it on the App Store and Google Play.</p><p>The problem is that every tutorial you find was written for people who already live in Xcode and Android Studio. They assume you have a Mac, know what a provisioning profile is, and have configured Gradle before. If you’re coming from the web world — or you’re an indie maker who just shipped a React or Vue app — those guides feel like they start three levels above where you are.</p><p>This guide starts at zero. It covers every step from “I have a web app” to “my app is live on both stores and I can push fixes without waiting for review” — using tools that handle the painful parts for you.</p><p>We’ve walked hundreds of users through this exact process. Here’s everything we’ve learned, in one place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7SgtjPvDpBewjpD-DOwFOw.png" /><figcaption><strong>11 Steps</strong> to Launch Your App on the App Store</figcaption></figure><h3>Who This Guide Is For</h3><p>This guide is for you if any of these sound familiar:</p><ul><li>You built a web app with React, Next.js, Vue, Angular, Svelte, or any other framework and want to ship it as a native app</li><li>You’re vibe-coding a product with Claude, Cursor, or Copilot and want to reach mobile users</li><li>You have a working app but have no idea how to get it into the App Store</li><li>You’ve been burned by App Store and Google Play Store review delays and want a way to push fixes instantly</li><li>You need to build for iOS but don’t own a Mac</li></ul><p>By the end of this guide you’ll have:</p><ul><li>A native iOS and Android app built from your existing web code</li><li>Both apps live on the App Store and Google Play</li><li>A system to push bug fixes and new features to users in minutes — without app store review</li></ul><h3>Step 1 — Convert Your Web App to Native with Capacitor</h3><p><a href="https://capacitorjs.com/">Capacitor</a> is an open-source runtime that wraps your web app in a native iOS and Android shell. Your code — React, Angular, Vue, Svelte, plain HTML, whatever — runs inside a WebView, and a native bridge connects it to device APIs through plugins.</p><p>This is fundamentally different from React Native or Flutter. There’s no rewrite. No new framework. If you can npm run build your app today, you can have a native version of it running on a phone by the end of this afternoon.</p><h3>Why Not a PWA?</h3><p>Progressive Web Apps are great for some use cases, but they have hard limits: you can’t publish them on the App Store or Google Play, iOS PWAs have persistent bugs with notifications and offline support, and you can’t access device APIs like biometrics, NFC, or Bluetooth. A Capacitor app is a real, store-listed native app — it just happens to be powered by web code.</p><h3>Who Uses Capacitor?</h3><p>Capacitor isn’t a new framework. It’s the runtime behind production apps used by millions of people every day — from indie makers to <a href="https://ionic.io/customers">Fortune 500 companies</a> across fintech, healthcare, logistics, and consumer products. The framework is maintained by the Ionic team, has over 12,000 GitHub stars, and ships regular releases.</p><p>If you’re worried about picking something that gets abandoned: Capacitor is the foundation of an entire ecosystem of tools, services, and companies that depend on it long-term. It’s not going anywhere.</p><h3>Setting Up Capacitor</h3><p>Install Capacitor in your existing web project:</p><pre>npm install @capacitor/core @capacitor/cli<br>npx cap init</pre><p>Add the iOS and Android platforms:</p><pre>npm install @capacitor/ios @capacitor/android<br>npx cap add ios<br>npx cap add android</pre><p>Build your web assets and sync them to the native projects:</p><pre>npm run build<br>npx cap sync</pre><p>That’s it. You now have a ios/ and android/ folder at the root of your project containing full native Xcode and Android Studio projects — pointing at your web build output. Every time you run npx cap sync, Capacitor compiles your web assets and copies them into the native projects, so the app always reflects your latest code.</p><h3>Works With Any Framework</h3><p>Capacitor is genuinely framework-agnostic. The setup is the same whether you use:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*qphg48BTDmx0Z1VFrmpRRw.png" /><figcaption>Capacitor Works With Any Framework</figcaption></figure><p><strong>Deep-dive guides:</strong> For more specific walkthroughs related to this topic, check the following guides:</p><ul><li><a href="https://capawesome.io/blog/build-mobile-apps-with-any-web-framework-and-capacitor/">Build Mobile Apps with Any Web Framework and Capacitor</a></li><li><a href="https://capawesome.io/blog/how-to-wrap-an-angular-app-with-capacitor-and-firebase/">How to Wrap an Angular App with Capacitor and Firebase</a></li></ul><h3>The Vibe Coding Path: Let an AI Agent Do the Setup</h3><p>If you’re building with an AI coding assistant, install the <a href="https://capawesome.io/skills/">Capawesome Skills</a> to give your agent deep Capacitor knowledge:</p><pre>npx skills add capawesome-team/skills --skill capacitor-app-creation</pre><p>Then prompt your agent (Claude Code, Cursor, Copilot):</p><pre>Use the `capacitor-app-creation` skill to set up Capacitor in my project.</pre><p>The agent will initialize Capacitor, add the platforms, fix your capacitor.config.ts, and sync everything - correctly, on the first try, without you having to know what npx cap sync does.</p><h3>Step 2 — Add Native Features with Plugins</h3><p>A plain Capacitor app renders your web UI on a phone. That’s useful, but the real power comes from connecting your JavaScript code to native device features through plugins.</p><p>Here’s a sample of what’s possible with the <a href="https://capawesome.io/docs/plugins/">Capawesome plugin library</a>:</p><h3>Authentication &amp; Security</h3><p><a href="https://capawesome.io/docs/plugins/biometrics/"><strong>Biometrics Plugin</strong></a> — Add Face ID, Touch ID, and fingerprint authentication to your app. One call to authenticate() handles the platform-specific prompt on both iOS and Android.</p><p><a href="https://capawesome.io/docs/plugins/vault/"><strong>Vault Plugin</strong></a> — Store secrets (tokens, keys, passwords) behind biometric or device-passcode protection. Backed by hardware-level encryption on both platforms.</p><p><a href="https://capawesome.io/docs/plugins/apple-sign-in/"><strong>Apple Sign-In</strong></a><strong> / </strong><a href="https://capawesome.io/docs/plugins/google-sign-in/"><strong>Google Sign-In</strong></a> — Native OAuth flows that look right on every device.</p><p><a href="https://capawesome.io/docs/plugins/audio-player/"><strong>Audio Player</strong></a><strong> / </strong><a href="https://capawesome.io/docs/plugins/audio-recorder/"><strong>Audio Recorder</strong></a> — Record and play back audio with full platform integration. Background playback, lock screen controls, the works.</p><p><a href="https://capawesome.io/docs/plugins/file-picker/"><strong>File Picker</strong></a> — Let users pick files from their device with the native file browser. Returns the file URI or base64 data.</p><h3>Scanning &amp; Recognition</h3><p><a href="https://capawesome.io/docs/plugins/mlkit/barcode-scanning/"><strong>ML Kit Barcode Scanning</strong></a> — On-device barcode and QR code scanning using Google’s ML Kit. No server required.</p><p><a href="https://capawesome.io/docs/plugins/mlkit/document-scanner/"><strong>ML Kit Document Scanner</strong></a> — Let users scan documents with edge detection and automatic cropping, just like a proper scanner app.</p><p><a href="https://capawesome.io/docs/plugins/nfc/"><strong>NFC Plugin</strong></a> — Read and write NFC tags on both Android and iOS.</p><h3>Connectivity</h3><p><a href="https://capawesome.io/docs/plugins/bluetooth-low-energy/"><strong>Bluetooth Low Energy</strong></a> — Connect to BLE peripherals: fitness trackers, IoT devices, medical devices, beacons.</p><p><a href="https://capawesome.io/docs/plugins/wifi/"><strong>WiFi Plugin</strong></a> — Get WiFi state, SSID, and signal strength.</p><h3>Payments &amp; Monetization</h3><p><a href="https://capawesome.io/docs/plugins/purchases/"><strong>Purchases Plugin</strong></a> — In-app purchases and subscriptions via RevenueCat. One SDK, both stores.</p><p><a href="https://capawesome.io/docs/plugins/superwall/"><strong>Superwall Plugin</strong></a> — A/B test paywalls without app updates.</p><h3>Firebase Integration</h3><p>The full <a href="https://capawesome.io/docs/plugins/firebase/">Firebase plugin suite</a> covers Analytics, Authentication, Crashlytics, Cloud Messaging (push notifications), Remote Config, Firestore, Cloud Storage, and more — each as a separate, tree-shakeable package.</p><h3>And Many More</h3><p>Capawesome maintains <a href="https://capawesome.io/docs/plugins/">50+ plugins</a> covering sensors (accelerometer, barometer, pedometer), productivity (contacts, app shortcuts, badge count), printing, screen orientation, speech recognition and synthesis, SQLite, geolocation, and more.</p><p>Can’t find the plugin you need?</p><p>Capawesome offers custom plugin development — the team has built custom Capacitor plugins for dozens of companies. <a href="https://capawesome.io/consulting/">Get in touch.</a></p><h3>Step 3 — Create Your Developer Accounts</h3><p>You need accounts on both platforms before anything can go live. This is a one-time setup, but it has real timelines you need to plan around.</p><h4>Apple Developer Program — $99/year</h4><p>Sign up at <a href="https://developer.apple.com/programs/enroll/">developer.apple.com/programs/enroll</a>. Apple takes up to 48 hours to approve new accounts. If you’re registering as an organization (to publish under a company name rather than your personal name), you’ll also need a D-U-N-S number, which takes 5–7 business days to obtain.</p><p><strong>Start this process first.</strong> It’s the most common cause of delayed launches.</p><h4>Google Play Console — $25 one-time</h4><p>Sign up at <a href="https://play.google.com/console/signup">play.google.com/console/signup</a>. The $25 fee is paid once and your account never expires. Identity verification usually completes within a few hours.</p><p>Full walkthrough: <a href="https://capawesome.io/blog/how-to-create-apple-developer-and-google-play-accounts/">How to Create Your Apple Developer and Google Play Developer Accounts</a></p><h3>Step 4 — Generate Your Signing Certificates</h3><p>Every app submitted to the stores must be cryptographically signed — this is how Apple and Google verify the build came from you. You need:</p><ul><li><strong>iOS:</strong> a distribution certificate + provisioning profile</li><li><strong>Android:</strong> a keystore file</li></ul><p>This is where most first-timers get stuck. The official Apple documentation for code signing is notoriously opaque. The good news: you can generate everything you need directly in your browser, without Xcode or Android Studio.</p><h3>Free Browser Tools</h3><p><a href="https://capawesome.io/tools/ios-certificate-generator/"><strong>iOS Certificate Generator</strong></a> generates iOS development and distribution certificates along with a CSR file — the same thing you’d normally do through Keychain Access on a Mac, but in your browser. No sign-up, nothing leaves your device.</p><p><a href="https://capawesome.io/tools/android-keystore-generator/"><strong>Android Keystore Generator</strong></a> creates a PKCS#12 keystore file for signing your Android app. Fill in the fields, download the file, store it somewhere safe — you’ll need it for every future release.</p><p><a href="https://capawesome.io/tools/ios-udid-finder/"><strong>iOS UDID Finder</strong></a> — if you need to register a test device for development builds, this finds your device UDID from any browser.</p><p>Once you have your certificates, upload them to Capawesome Cloud once. Every subsequent build picks them up automatically — no local keychain required, no credentials in your CI environment variables.</p><ul><li><a href="https://capawesome.io/docs/cloud/native-builds/certificates/ios/">Docs: iOS signing certificates</a></li><li><a href="https://capawesome.io/docs/cloud/native-builds/certificates/android/">Docs: Android signing certificates</a></li></ul><p>For a detailed explanation of what certificates and provisioning profiles actually are:</p><p><a href="https://capawesome.io/blog/ios-certificates-and-provisioning-profiles-explained/">iOS Certificates and Provisioning Profiles Explained</a></p><h3>Step 5 — Build Your Native App in the Cloud</h3><p>Traditionally, building an iOS app requires a Mac with the right version of Xcode. Building a production Android APK requires Android Studio with the right Java and Gradle versions configured. Both need your signing credentials stored locally.</p><p>Capawesome Cloud <a href="https://capawesome.io/cloud/native-builds/">Native Builds</a> eliminates all of that. You connect your Git repository, and the build happens on <strong>Apple Silicon M4 Pro hardware</strong> in the cloud — delivering typical build times of 2–5 minutes. You can trigger builds from Windows, Linux, or a Chromebook. No Mac required.</p><h3>How It Works</h3><p><strong>Step 1: Connect your repository</strong></p><p>Link your GitHub, GitLab, Bitbucket, or Azure DevOps repository to Capawesome Cloud. This is a one-time OAuth authorization.</p><p><strong>Step 2: Trigger a build</strong></p><p>From the Capawesome Cloud Console, choose your branch, select iOS or Android, pick your build type (Debug, Release, Simulator), and hit Build.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WHUYv-mUqEwSQTdQ.png" /><figcaption>capawesome cloud console</figcaption></figure><p><strong>Step 3: Download or deploy</strong></p><p>When the build completes, download the IPA or APK/ABB directly — or chain it into an App Store Publishing destination with one click.</p><h3>Build From the CLI</h3><p>You can also trigger builds from the terminal with the <a href="https://capawesome.io/docs/cloud/cli/">Capawesome CLI</a>:</p><pre>npx @capawesome/cli apps:builds:create \<br>  --platform ios \<br>  --buildType release</pre><p>This makes it easy to plug Capawesome Cloud into any existing CI pipeline — GitHub Actions, GitLab CI, Bitbucket Pipelines, Jenkins, or anything else.</p><h3>Advanced Features</h3><ul><li><a href="https://capawesome.io/docs/cloud/native-builds/environments/"><strong>Environments</strong></a> — define separate configurations for dev, staging, and production builds</li><li><a href="https://capawesome.io/docs/cloud/native-builds/guides/auto-incrementing-build-numbers/"><strong>Auto-increment build numbers</strong></a> — never manually bump your build number again</li><li><a href="https://capawesome.io/docs/cloud/native-builds/guides/build-without-git/"><strong>Build without Git</strong></a> — upload a ZIP if you don’t want to connect a repository</li><li><a href="https://capawesome.io/docs/cloud/assist/"><strong>Assist — Ask AI</strong></a> — when a build fails, click Ask AI to get a plain-English diagnosis with a suggested fix</li></ul><p>Full setup guide: <a href="https://capawesome.io/docs/cloud/native-builds/setup/">Getting Started with Native Builds</a></p><h3>Step 6 — Distribute to Testers</h3><p>Before going to the public stores, get your app onto real devices. Finding bugs on a physical device — especially iOS — is consistently different from finding them in a simulator.</p><p>Capawesome Cloud App Store Publishing supports all the major testing channels:</p><p><strong>TestFlight (iOS)</strong> — Upload your IPA to TestFlight and invite testers by email. Testers install the app from the TestFlight app. Internal testers (up to 100) skip the review queue; external testers go through a simplified review that usually takes a few hours.</p><p><strong>Google Play Internal Testing</strong> — Share your app via a link immediately after upload, with no review. Testers install it directly from the Play Store.</p><p>You can also install a build directly on a device from the Capawesome Cloud Console without going through any store:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DiOre3KrGDeTAyTJ.png" /><figcaption>distribute mobile app to testers</figcaption></figure><p>Full guide: <a href="https://capawesome.io/blog/how-to-distribute-ios-and-android-apps-to-testers/">How to Distribute iOS and Android Apps to Testers</a></p><h3>Step 7 — Prepare Your Store Listing</h3><p>This is where most first-timers hit an unexpected wall. The app is built, it works, but you can’t submit it without a complete store listing. Apple and Google require:</p><ul><li><strong>App icon</strong> — 1024×1024px for iOS (no transparency), 512×512px for Google Play</li><li><strong>Screenshots</strong> — Apple now requires iPhone 6.9&quot; (1320×2868px) screenshots; these are mandatory</li><li><strong>App name and description</strong> — Apple gives you 30 characters for the name, 30 for a subtitle, and 100 characters of keywords (comma-separated, don’t repeat what’s in the name)</li><li><strong>Privacy policy URL</strong> — Required by both platforms, even for free apps with no data collection</li><li><strong>Age rating</strong> — Calculated from a questionnaire in each store’s console</li><li><strong>Data collection disclosures</strong> — Apple’s Privacy Nutrition Labels and Google’s Data Safety section both require you to declare every type of data your app collects, including data from third-party SDKs</li></ul><p>The full checklist with every requirement, device size, and tool recommendation:</p><p><a href="https://capawesome.io/blog/how-to-prepare-your-app-store-listing/">How to Prepare Your App Store Listing</a></p><h3>Step 8 — Complete Google Play’s Closed Testing Period</h3><p><strong>This is the most common surprise for first-time publishers, and it can delay your Android launch by weeks.</strong></p><p>For <strong>personal developer accounts created after November 13, 2023</strong>, Google Play requires new apps to complete a <strong>closed testing period</strong> before they can publish to the public ( <a href="https://support.google.com/googleplay/android-developer/answer/14151465">source</a>):</p><ul><li>You need <strong>at least 12 testers</strong> who actively opt in via a special link</li><li>The testing period must run for <strong>at least 14 consecutive days</strong></li><li>After 14 days with 12+ active testers, you can apply for production access</li></ul><p>Organization accounts are not subject to this requirement.</p><p>This means your Google Play launch is a minimum of two weeks from when you have 12 testers opted in. <strong>Start recruiting testers the moment your first Android build is ready</strong> — don’t wait until you’re “ready to launch.”</p><p>Good places to find testers: your existing user base (if any), the <a href="https://discord.gg/VCXxSVjefW">Capawesome Discord community</a>, your company’s Slack, friends, family.</p><p>The App Store does not have this requirement — iOS apps go live immediately after Apple’s review.</p><h3>Step 9 — Submit for Review</h3><p>With your store listing complete and testing done, you’re ready to submit.</p><h3>App Store (iOS)</h3><p>In App Store Connect, set your app’s release strategy (manual or automatic after approval), assign the build you want to submit, and click Submit for Review. Apple’s review typically takes 3–5 days for new apps.</p><p>Common reasons for rejection: — Missing privacy policy — App crashes on launch (test on a real device, not just a simulator) — Metadata mismatch (screenshots don’t match the app’s actual UI) — Missing required functionality explanations — Login credentials not provided. You must provide the review team with an active and functional test account. Because App Review is an automated and manual process, the reviewers cannot access account-restricted features without valid login information.</p><p>Be careful with all these requirements, because even though you can resubmit your app after a rejection, each resubmission takes longer to be reviewed.</p><h3>Google Play</h3><p>After your closed testing period, apply for production access in the Google Play Console. Once approved, your initial review typically takes 3–7 days.</p><h3>Automated Submissions with Capawesome Cloud</h3><p>Capawesome Cloud <a href="https://capawesome.io/cloud/app-store-publishing/">App Store Publishing</a> automates the submission step entirely. You connect your App Store Connect API key and Google Play service account once, configure your store destinations, and then publish with a single click — or automatically on every successful native build via <a href="https://capawesome.io/docs/cloud/automations/setup/">Automations</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8ITNcMWe5UbL3Muj.png" /><figcaption>deploy native apps</figcaption></figure><p>Supported destinations: — Apple App Store (production) — TestFlight (internal and external) — Google Play (Internal, Alpha, Beta, Production) — Firebase App Distribution</p><p>When a submission fails, <a href="https://capawesome.io/docs/cloud/assist/">Ask AI</a> in the Capawesome Console parses Apple’s or Google’s validator output and tells you exactly what went wrong and how to fix it — in plain language.</p><h3>Step 10 — Set Up Live Updates: Your Biggest Advantage</h3><p>Once your app is approved, this is the feature that changes everything about how you iterate.</p><p><strong>The problem with native app updates:</strong> Every change you ship — a bug fix, a copy tweak, a new feature — must go through the App Store review queue. That’s 1–5 days. For critical bugs, that’s an eternity.</p><p><strong>Live Updates bypass the queue entirely.</strong></p><p>Because Capacitor separates your app into a native shell and a web layer (HTML, CSS, JavaScript, and static assets), you can update the web layer over the air — directly to users’ devices, in minutes.</p><p><strong>Can update:</strong> any change to your HTML, CSS, JavaScript, images, fonts, JSON data, and other static assets.</p><p><strong>Cannot update:</strong> changes that require new native code, new Capacitor plugins, new iOS/Android permissions, or changes to Info.plist / AndroidManifest.xml. Those still need a native build and a store review.</p><p>In practice, the vast majority of day-to-day iteration — UI changes, bug fixes, new screens, content updates — falls in the “can update” category.</p><h3>Setup</h3><p>Install the Live Update plugin:</p><pre>npm install @capawesome/capacitor-live-update@latest<br>npx cap sync</pre><p>Configure it in capacitor.config.ts:</p><pre>import { CapacitorConfig } from &#39;@capacitor/cli&#39;;<br><br>const config: CapacitorConfig = {<br>  plugins: {<br>    LiveUpdate: {<br>      appId: &#39;your-app-id-from-capawesome-cloud&#39;,<br>      autoUpdateStrategy: &#39;background&#39;,<br>    },<br>  },<br>};<br><br>export default config;</pre><p>autoUpdateStrategy: &#39;background&#39; is the recommended default - the app checks for updates at every launch, downloads them silently in the background, and applies them the next time the user opens the app. No code changes, no user prompts.</p><p>Shipping a fix from that point forward:</p><pre>npm run build<br>npx @capawesome/cli apps:liveupdates:upload</pre><p>Done. Every user gets the fix on their next app launch.</p><p>Capawesome Cloud Live Updates includes features that enterprise teams depend on:</p><p><a href="https://capawesome.io/docs/cloud/live-updates/channels/"><strong>Channels</strong></a> — ship different bundles to different user segments. Useful for A/B testing, staged rollouts, or keeping your beta users on a separate track.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9ojxTO4_uasEupxj.png" /></figure><p><a href="https://capawesome.io/docs/cloud/live-updates/advanced/rollouts/"><strong>Rollouts</strong></a> — gradually roll out a new bundle to 10%, 25%, 50%, then 100% of users. Watch your error rates before committing to a full release.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nWnMquMacHgfiwDN.png" /></figure><p><a href="https://capawesome.io/docs/cloud/live-updates/advanced/rollbacks/"><strong>Rollbacks</strong></a> — if something goes wrong, roll back to the previous bundle instantly from the console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AC4T4Kld2SbselFF.png" /></figure><p><a href="https://capawesome.io/docs/cloud/live-updates/advanced/code-signing/"><strong>Code Signing</strong></a> — RSA-sign your bundles so the Live Update SDK verifies authenticity on every device before applying an update.</p><p><a href="https://capawesome.io/docs/cloud/live-updates/advanced/delta-updates/"><strong>Delta Updates</strong></a> — only ship the files that changed, not the entire bundle. Dramatically reduces update size and delivery time for returning users.</p><p><a href="https://capawesome.io/docs/cloud/live-updates/devices/"><strong>Device Management</strong></a> — force specific devices to a specific channel. Great for QA devices, internal testing, or enterprise deployments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DcaWRQRM7YSTmAGu.png" /></figure><p>Include the Live Update plugin in your first release — even before you have updates to ship. Adding a new plugin requires a new Native Build and another store review, and that’s exactly the situation you don’t want to be in when you’re trying to push a critical fix.</p><p><strong>Full documentation:</strong></p><ul><li><a href="https://capawesome.io/docs/cloud/live-updates/setup/">Getting Started with Live Updates</a></li><li><a href="https://capawesome.io/blog/capacitor-live-updates-guide/">Capacitor Live Updates: A Complete Guide to OTA Updates</a></li><li><a href="https://capawesome.io/docs/cloud/live-updates/guides/update-strategies/">Update Strategies</a></li><li><a href="https://capawesome.io/docs/cloud/live-updates/guides/best-practices/">Live Updates Best Practices</a></li></ul><h3>Step 11 — Automate Everything</h3><p>Once you’re comfortable with the flow, the final step is connecting the pieces so that a git push triggers the entire pipeline without you touching a dashboard.</p><p><a href="https://capawesome.io/docs/cloud/automations/setup/">Capawesome Cloud Automations</a> lets you define end-to-end pipelines:</p><pre>git push to main<br>  → Trigger Native Build (iOS + Android)<br>  → On success: publish to TestFlight + Google Play Internal<br>  → On build approval: deploy Live Update to production channel</pre><p>Automations can be triggered on a <strong>Git push</strong> to a specific branch or tag. When a build or deployment completes, Capawesome Cloud can send a <a href="https://capawesome.io/docs/cloud/automations/webhooks/">webhook</a> with the result — making it easy to post notifications to Slack, Microsoft Teams, Discord, or any other tool, so your team knows when a build succeeds or fails without watching the console.</p><p>For CI/CD pipelines you already have, the <a href="https://capawesome.io/docs/cloud/cli/">Capawesome CLI</a> and <a href="https://capawesome.io/docs/cloud/api/">REST API</a> let you trigger any action from GitHub Actions, GitLab CI, Bitbucket Pipelines, Azure DevOps, or Jenkins.</p><p><strong>Guides:</strong></p><ul><li><a href="https://capawesome.io/blog/ci-cd-for-capacitor-apps/">Capacitor CI/CD in 2026: Why Specialization Wins</a></li><li><a href="https://capawesome.io/blog/ci-cd-for-capacitor-common-pitfalls/">CI/CD for Capacitor: Common Pitfalls and How to Avoid Them</a></li><li><a href="https://capawesome.io/docs/cloud/live-updates/integrations/github-actions/">GitHub Actions integration</a></li><li><a href="https://capawesome.io/docs/cloud/live-updates/integrations/gitlab-ci/">GitLab CI/CD integration</a></li></ul><h3>Everything Inside Capawesome Cloud</h3><p>Here’s the full picture of what Capawesome Cloud gives you — all under one roof, one subscription, one dashboard. All plans include a <strong>14-day free trial</strong>.</p><h3>Native Builds</h3><p>Cloud-based iOS and Android builds on Apple Silicon M4 Pro. No Mac, no build servers to manage. Average build time: 2–5 minutes. Includes managed code signing, build history, downloadable artifacts, environment variables, and full build logs.</p><p><strong>Thousands of native builds</strong> are completed on Capawesome Cloud every month.</p><p>OTA updates delivered over a global CDN. Includes channels, rollouts, rollbacks, RSA code signing, delta updates, device management, and analytics.</p><h3>App Store Publishing</h3><p>One-click submissions to TestFlight, the App Store, Google Play (all tracks), and Firebase App Distribution. Supports multiple destinations per app — ideal for <a href="https://capawesome.io/solutions/white-label/">white-label</a> products or regional variants. Encrypted credentials, protected destinations with role-based access control, and full audit logs.</p><p><strong>Thousands of App Store updates</strong> deployed every month.</p><h3>Automations</h3><p>Automatically trigger native builds from Git events — on every push to a branch or on tag creation. Chain builds with store publishing and live update deployments in a single pipeline. When a build completes, Capawesome Cloud sends a <a href="https://capawesome.io/docs/cloud/automations/webhooks/">webhook</a> with the result so you can connect it to any notification tool.</p><h3>Assist — AI Diagnostics</h3><p>When a build or deployment fails, Ask AI turns the raw validator output from Apple, Google, or your build logs into a plain-language cause → explanation → suggested fix. Opt-in per click, zero data retention.</p><h3>Integrations</h3><p>GitHub, GitLab, Bitbucket, Azure DevOps, GitHub Enterprise, GitLab Self-Managed, Slack, Microsoft Teams, Discord.</p><h3>Security &amp; Compliance</h3><ul><li>GDPR compliant, data hosted in Germany</li><li>ISO 27001 certified (our data center partners)</li><li>SOC 2 Type II (report available on request)</li><li>All credentials encrypted at rest</li><li>RSA code signing for live update bundles</li></ul><h3>Need Expert Help? We Do That Too</h3><p>Building a Capacitor app is learnable, but sometimes you need someone who’s already made all the mistakes.</p><p>The Capawesome team offers <a href="https://capawesome.io/consulting/">consulting services</a> for teams that need hands-on help:</p><ul><li><strong>Capacitor app development</strong> — architecture, development, deployment, and maintenance</li><li><strong>Custom Capacitor plugins</strong> — if no existing plugin does what you need, we build it. We’ve delivered custom plugins for dozens of companies, often within a few days</li><li><strong>Collaborative support</strong> — work alongside your team for architecture reviews, code reviews, debugging, and pairing sessions</li><li><strong>CI/CD setup</strong> — get your build and deployment pipeline configured correctly from the startThe Complete Checklist to Deploy a Mobile app</li></ul><p>Check: <a href="https://capawesome.io/blog/11-steps-to-get-your-web-app-on-the-app-store/">The Complete Checklist to Deploy a Mobile app</a></p><h3>Final Thoughts</h3><p>The mobile app store process has a reputation for being painful — and for good reason. The certificate maze, the review queue, the toolchain requirements, the surprise gotchas like Google’s closed testing period — none of it is developer-friendly by default.</p><p>But the actual hard parts are a small fraction of what people worry about. With Capacitor handling the native layer, Capawesome Cloud handling the build and deployment infrastructure, and a handful of free browser tools handling the certificate setup, the genuinely difficult stuff is gone. What’s left is building your product.</p><p>If you get stuck at any step, the <a href="https://discord.gg/VCXxSVjefW">Capawesome Discord</a> is active and the team is there. And if you want someone in the trenches with you, <a href="https://capawesome.io/consulting/">consulting is available</a>.</p><p>Subscribe to the <a href="https://capawesome.io/newsletter/">Capawesome newsletter</a> for updates on new plugins, Cloud features, and guides like this one.</p><p><a href="https://console.cloud.capawesome.io/">Start your 14-day free trial</a></p><p><em>Originally published at </em><a href="https://capawesome.io/blog/11-steps-to-get-your-web-app-on-the-app-store/"><em>https://capawesome.io</em></a><em> on June 4, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5299d80a67d0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learn-ionic-framework/11-steps-to-get-your-web-app-on-the-app-store-5299d80a67d0">11 Steps to Get Your Web App on the App Store</a> was originally published in <a href="https://medium.com/learn-ionic-framework">Learn Ionic Framework</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Complete Guide to OTA Updates for Mobile Apps]]></title>
            <link>https://medium.com/@dayanajabif/the-complete-guide-to-ota-updates-for-mobile-apps-d7615ddad83f?source=rss-f05e27e8a50e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7615ddad83f</guid>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ionic-framework]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Dayana Jabif]]></dc:creator>
            <pubDate>Sat, 16 May 2026 00:00:12 GMT</pubDate>
            <atom:updated>2026-05-18T12:39:30.520Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Complete Guide to OTA Updates for Capacitor Apps</h3><p>Shipping a fix used to mean a bundled binary, an app store review, and a few days of hoping users would tap “update”. With Capacitor Live Updates that loop shrinks to minutes. You push a new web bundle, devices pick it up on the next launch, and the next version of your app is already in users’ hands.</p><p>This guide is the long version. We’ll walk through how live updates actually work under the hood, the three choices every team has to make, the security model, the production best practices that keep you out of trouble, and a complete end-to-end example based on a real-world app. Whether you’re evaluating live updates for the first time or already shipping them, you should leave with a clear picture of the recommended path and the tradeoffs behind it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uFwlNe7suW9Vv1xZDFB81w.png" /><figcaption>Capacitor Live Updates: A Complete Guide to OTA Updates</figcaption></figure><h3>What Are Live Updates?</h3><p>A Capacitor app has two layers. The <strong>native layer</strong> is the compiled binary that’s installed from the App Store or Google Play — it contains the WebView, the native plugins, and the platform glue. The <strong>web layer</strong> is everything that runs inside that WebView: your HTML, CSS, JavaScript, and static assets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/591/0*2AdNWOg4B551HFfO" /><figcaption>Capacitor App Layers</figcaption></figure><p>A live update is an Over-the-Air (OTA) update of the web layer only. The native binary stays untouched. Instead of pushing a new build to the stores, you upload a new web bundle to a delivery service, and the <a href="https://capawesome.io/docs/plugins/live-update/">Live Update</a> plugin in your app downloads it, swaps it in, and reloads.</p><p>That’s the whole idea. The constraint is also the feature: because nothing native changes, you don’t need an app store review and you don’t need users to take any action.</p><h3>Why Use Live Updates?</h3><p>A few reasons teams reach for them:</p><ul><li><strong>Hotfixes in minutes, not days.</strong> A critical bug — broken login, wrong API URL, regression in checkout — can be patched before most users notice.</li><li><strong>Faster feature iteration.</strong> Ship small improvements as soon as they’re ready instead of batching them into a monthly native release.</li><li><strong>Staged rollouts and A/B testing.</strong> Roll a new bundle out to 5% of users, watch the dashboards, then expand. Run different bundles on different channels for beta testers, internal builds, or geographic segments.</li><li><strong>Smaller user friction.</strong> Users don’t have to manually tap “update” in the store, and you’re not waiting on whoever postpones store updates for weeks.</li></ul><h3>Binary-Compatible vs. Non-Binary-Compatible Changes</h3><p>The single most important rule with live updates: <strong>you can only update what already exists in the native binary.</strong> Changes that don’t touch native code are called <em>binary-compatible</em>. Anything else needs a real app store release.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jSqHhL0KnZwBywUUM3YPSw.png" /></figure><p>A useful mental model: if your change only modifies files inside your web project — your src/, your build output - and doesn&#39;t add, remove, or upgrade a Capacitor plugin or any native code or config, it&#39;s binary-compatible. We&#39;ll come back to this when we talk about versioning, because the most common production bug with live updates is delivering a bundle that depends on a native feature the installed binary doesn&#39;t have yet.</p><h3>How It Works Under the Hood</h3><p>The Capacitor WebView doesn’t load your HTML from https://example.com. It loads it from a local path on disk - Capacitor calls this the <em>server base path</em>. By default, that path points to the public/ folder bundled inside the native app, which is exactly the output of npm run build at the time you shipped the binary.</p><p>A live update is, at its core, swapping that path:</p><ol><li>The plugin downloads a new bundle and writes it to a local directory inside the app’s sandbox.</li><li>It updates two values that Capacitor reads: the <em>current</em> server path (the one the WebView is using right now) and the <em>next</em> server path (the one Capacitor will use on the next app start).</li><li>On the next launch — or immediately, if you call reload() - the WebView loads from the new path instead of the bundled public/ folder.</li></ol><p>On Android, the <em>next</em> path lives in SharedPreferences under the CapWebViewSettings group. On iOS, it&#39;s stored in UserDefaults via Capacitor&#39;s KeyValueStore class, with one quirk: only paths under /Library/NoCloud/ionic_built_snapshots are valid, and only the last path component matters.</p><p>If you want the full deep dive, including how the plugin uses the Capacitor Bridge’s setServerBasePath() to swap paths at runtime, see <a href="https://capawesome.io/blog/how-live-updates-for-capacitor-work/">How Live Updates for Capacitor Work Under the Hood</a>.</p><h3>Are Live Updates Compliant With App Store Policies?</h3><p>Yes. Both Apple and Google explicitly allow downloading and executing code inside a WebView or scripting runtime, which is exactly what live updates do.</p><p><strong>Apple’s App Store Review Guidelines</strong> (section 3.3.2) allow downloading interpreted code as long as it (a) doesn’t change the primary purpose of the app, (b) doesn’t create a store or storefront for other code, and © doesn’t bypass the system’s signing, sandbox, or security features. Web code running in a WKWebView checks all three boxes.</p><p><strong>Google Play’s Device and Network Abuse policy</strong> forbids apps from modifying or replacing themselves outside of Play — with an explicit exception for “code that is interpreted in a virtual machine or runtime (like JavaScript in a webview or browser).”</p><p>In other words, app stores draw the line at <em>native</em> self-modification. Live updates only touch the web layer, so they stay safely on the right side of that line.</p><h3>Wiring It Up</h3><p>Before any choices, the SDK needs to be installed and connected to Capawesome Cloud. Install the plugin, create a Cloud app, and add it to your Capacitor config.</p><h4>AI-Assisted Setup</h4><p>For a more guided experience, add the <a href="https://github.com/capawesome-team/skills">Capawesome skills</a> to your project with npx skills add capawesome-team/skills --skill capawesome-live-updates and use the following prompt with your preferred AI coding assistant:</p><pre>Use the `capawesome-live-updates` skill from `capawesome-team/skills` to help me set up live updates in my Capacitor app.</pre><p>If you’d rather do it by hand, install the plugin and sync the native projects:</p><pre>npm install @capawesome/capacitor-live-update <br>npx cap sync</pre><p>Then create an app in Capawesome Cloud — the CLI prompts for the organization and app name, and prints the resulting app ID:</p><pre>npx @capawesome/cli apps:create</pre><p>Finally, add the plugin to your Capacitor config with the app ID you just got back:</p><pre>//File: capacitor.config.ts<br><br>const config: CapacitorConfig = {<br>  plugins: {<br>    LiveUpdate: {<br>      appId: &#39;00000000-0000-0000-0000-000000000000&#39;,<br>      autoUpdateStrategy: &#39;background&#39;,<br>      autoBlockRolledBackBundles: true,<br>      readyTimeout: 10000<br>    }<br>  }<br>};</pre><p>For full setup instructions including the Capacitor 6 and 7 variants, see the <a href="https://capawesome.io/docs/cloud/live-updates/setup/">Live Updates setup guide</a>.</p><h3>Three Choices to Make</h3><p>With the SDK installed, three choices shape how live updates behave in your app. Pick a default for each, and you have a production setup.</p><h4>Decision 1: Update Strategy</h4><p>The <em>strategy</em> decides <strong>when</strong> an update is downloaded, <strong>when</strong> it’s applied, and <strong>whether the user is involved.</strong> It’s as much a UX decision as a technical one — each option trades freshness against friction differently, and the right choice depends on how important it is that users are on the latest code versus how much you’re willing to interrupt them to get them there.</p><p>The plugin supports four patterns, ranging from “set it once and forget about it” to “fire an update across the install base on demand”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E0loqbIjZNL_1uLBJ0EPXg.png" /></figure><p>The sections below walk through each one in turn, with the config and code to wire it up.</p><h4>Background</h4><p>The simplest option, with zero app-side code. You set it once in your config:</p><pre>//File: capacitor.config.ts<br><br>plugins: {<br>  LiveUpdate: {<br>    appId: &#39;...&#39;,<br>    autoUpdateStrategy: &#39;background&#39;<br>  }<br>}</pre><p>The plugin automatically checks for updates on app start and on resume, downloads new bundles in the background, and applies them the next time the app launches. Users get the new version on their next cold start — no prompts, no waiting. There’s a built-in 15-minute minimum between checks so the plugin can’t be accidentally turned into a polling loop that drains the battery.</p><p>The tradeoff is that the update is invisible. Users won’t know a new version exists until the app silently behaves differently on their next session, which can be confusing if something visibly changed. Reach for this strategy when the update doesn’t need user attention.</p><h4>Always Latest (Recommended)</h4><p>Our recommended strategy. You still get the <em>background</em> strategy’s silent download, but instead of making the user wait for the next cold start, you prompt them to apply the update as soon as it’s ready. Users find out when something new is available, and they decide whether to apply it now or keep working with the current version.</p><p>You opt in by listening for the nextBundleSet event:</p><pre>import { LiveUpdate } from &#39;@capawesome/capacitor-live-update&#39;;<br><br>LiveUpdate.addListener(&#39;nextBundleSet&#39;, async ({ bundleId }) =&gt; {<br>  if (!bundleId) {<br>    return;<br>  }<br>  const shouldReload = confirm(&#39;A new version is available. Install it now?&#39;);<br>  if (shouldReload) {<br>    await LiveUpdate.reload();<br>  }<br>});</pre><p>The download still happens in the background, so the prompt only appears once the bundle is fully on disk — there’s no waiting on a network call when the user taps “install”. This is the strategy the real-world example later in this guide uses.</p><h4>Force Update</h4><p>The “user must be on the latest version before they can use the app” strategy. First, disable the Splash Screen’s auto-hide so it stays visible while the update check runs:</p><pre>// File: capacitor.config.ts<br><br>plugins: {<br>  SplashScreen: {<br>    launchAutoHide: false<br>  },<br>  LiveUpdate: {<br>    appId: &#39;...&#39;,<br>    autoUpdateStrategy: &#39;none&#39;<br>  }<br>}</pre><p>Then on app start, sync, and either reload (if there’s a new bundle) or hide the splash (if there isn’t):</p><pre>import { LiveUpdate } from &#39;@capawesome/capacitor-live-update&#39;;<br>import { SplashScreen } from &#39;@capacitor/splash-screen&#39;;<br><br>const { nextBundleId } = await LiveUpdate.sync();<br>if (nextBundleId) {<br>  await LiveUpdate.reload();<br>} else {<br>  await SplashScreen.hide();<br>}</pre><p>This guarantees freshness, but it costs you. Every cold start on a slow connection means the user stares at the splash screen while a multi-megabyte bundle downloads. Reserve it for cases where running a stale version is genuinely unsafe (e.g. some kinds of regulated apps). Always set autoUpdateStrategy: &#39;none&#39; to avoid two update mechanisms running at once.</p><h4>Instant</h4><p>For genuinely critical updates — a bad bug already in production, a security patch — the fastest path is a silent push notification that tells the app “go check for an update <em>now</em>”:</p><pre>import { FirebaseMessaging } from &#39;@capacitor-firebase/messaging&#39;;<br>import { LiveUpdate } from &#39;@capawesome/capacitor-live-update&#39;;<br><br>FirebaseMessaging.addListener(&#39;notificationReceived&#39;, async ({ data }) =&gt; {<br>  if (data?.type !== &#39;live-update&#39;) {<br>    return;<br>  }<br>  const { nextBundleId } = await LiveUpdate.sync();<br>  if (nextBundleId) {<br>    const shouldReload = confirm(&#39;Critical update available. Install now?&#39;);<br>    if (shouldReload) {<br>      await LiveUpdate.reload();<br>    }<br>  }<br>});</pre><p>This requires push infrastructure (typically <a href="https://capawesome.io/docs/plugins/firebase/cloud-messaging/">Firebase Cloud Messaging</a>) and is meant for the long tail of “someone has the broken bundle open right now, and we need to fix it before they touch checkout.” Set autoUpdateStrategy: &#39;none&#39; and don&#39;t use this as your default strategy - it&#39;s a <em>break-glass</em> tool, not an everyday flow.</p><h3>Decision 2: Versioning Strategy</h3><p>This is the decision that prevents the most common production failure: <strong>shipping a web bundle that doesn’t match the installed native binary.</strong></p><p>Picture a user with version 5 of your native app. You ship a new web bundle that calls a method on a plugin you only added in version 6. If that bundle reaches the v5 user, their app crashes on launch — and the only way out is reinstalling from the store.</p><p>You prevent this by binding each web bundle to the range of native versions it’s compatible with. There are two ways to do it.</p><h4>Versioned Bundles</h4><p>You attach min/max/equals version ranges to each upload:</p><pre>npx @capawesome/cli apps:liveupdates:upload \<br>  --android-min 10 --android-max 12 \<br>  --ios-min 10 --ios-max 12</pre><p>The Cloud only serves the bundle to devices inside the range. Simple, but error-prone: you have to remember the right flags on every upload, and rollouts get awkward because the rollout percentage is calculated over <em>all</em> devices in the channel, including ones that can’t install the bundle.</p><h4>Versioned Channels (Recommended)</h4><p>A cleaner pattern: one channel per native version. Bundle uploaded to production-10 only reaches devices on native version 10, and so on.</p><p>The cleanest way to wire this up is <strong>at build time</strong>, in the native configuration. Then your app code doesn’t have to know anything about channels — Capacitor reads the channel directly from the platform config.</p><p>On Android, add a resource value in android/app/build.gradle:</p><pre>android {<br>    defaultConfig {<br>        versionCode 60003<br>        resValue &quot;string&quot;, &quot;capawesome_live_update_default_channel&quot;,<br>                 &quot;production-&quot; + defaultConfig.versionCode<br>    }<br>}</pre><p>On iOS, add a key to ios/App/App/Info.plist:</p><pre>&lt;key&gt;CapawesomeLiveUpdateDefaultChannel&lt;/key&gt;<br>&lt;string&gt;production-$(CURRENT_PROJECT_VERSION)&lt;/string&gt;</pre><p>Every native release ships pinned to its own channel. Bumping the native version automatically opens a fresh channel for compatible web bundles. No JavaScript-side state to manage.</p><p>If you can’t use the native config (e.g. you want to switch channels at runtime based on something other than the version code), you can pass the channel inline on every sync — pass it directly to sync() or fetchLatestBundle() rather than calling setChannel() separately, so the channel selection is always explicit at the call site:</p><pre>import { LiveUpdate } from &#39;@capawesome/capacitor-live-update&#39;;<br><br>const { versionCode } = await LiveUpdate.getVersionCode();<br>await LiveUpdate.sync({ channel: `production-${versionCode}` });</pre><p>The real win is safety. Every deployment is addressed to a specific native version by name, so it’s much harder to accidentally ship a bundle to a binary that can’t run it. There are no version-range flags to remember on each upload, and no way for a typo to push a bundle to devices outside the intended set. For most teams, channels are the right answer.</p><p>For the long version, see <a href="https://capawesome.io/blog/how-to-restrict-capacitor-live-updates-to-native-versions/">How to Restrict Capacitor Live Updates to Native Versions</a>.</p><h3>Decision 3: Update Delivery Method</h3><p>How is the bundle packaged for transport?</p><h4>Zip (Recommended)</h4><p>The whole web folder is compressed into a single .zip and uploaded:</p><pre>npx @capawesome/cli apps:liveupdates:upload --artifact-type zip</pre><h4>Manifest (Delta Updates)</h4><p>The device downloads one compressed file and extracts it. This is the default and almost always the right choice — compression typically halves the size, the download is a single HTTP request, and it works regardless of how your build tool names files.</p><p>The alternative is a per-file manifest: each file is uploaded individually, and the device only downloads files whose hash changed since its current bundle.</p><p>In theory, this is great for apps that mostly change one or two files between releases. In practice, modern bundlers (Vite, Angular CLI, Webpack 5+, Nuxt, Next-to-static) all use <em>content-hashed filenames</em> — main.7f3a91c2.js, chunk-3a7f2b.js, and so on. The whole point of content hashing is that filenames change whenever content changes, which defeats delta comparison: every file looks new, so every file gets downloaded, and you lose the single-zip compression on top.</p><p>We’ve seen this in the wild. One team’s bundle was 20 MB on manifest and 9 MB on zip for the exact same web output - just because the manifest mode couldn&#39;t take advantage of compression while their content-hashed filenames defeated the delta comparison. Another team got from 48 MB to 9 MB by switching to zip and dropping source maps. The data is consistent: start on zip, and only consider manifest if you have specific, stable-named, large static assets you know don&#39;t change between builds.</p><p>For the full breakdown, see <a href="https://capawesome.io/blog/how-to-reduce-the-bundle-size-of-capacitor-live-updates/">How to Reduce the Bundle Size of Capacitor Live Updates</a>.</p><h3>Security: Code Signing</h3><p>Live updates run on the same trust model as your native binary: whatever code you ship will execute in your app’s context. If someone can replace a bundle in transit — say, on a hostile Wi-Fi network with a forged certificate, or by compromising your delivery server — they get code execution inside your app. Even though the Cloud uses HTTPS, defense in depth matters here.</p><p>Code signing closes that gap with two guarantees:</p><ul><li><strong>Authenticity</strong> — the bundle was produced by someone holding your signing key.</li><li><strong>Integrity</strong> — the bundle wasn’t modified between upload and install.</li></ul><p>The mechanism is a standard RSA keypair. You generate a private key and a public key. The private key is used to sign each bundle when you upload it. The public key is embedded in your app config and used to verify the signature of every downloaded bundle before it’s applied. If the signature doesn’t match, the bundle is rejected.</p><p>Generate the keypair with the CLI:</p><pre>npx @capawesome/cli apps:liveupdates:generatesigningkey</pre><p>This produces private.pem and public.pem. Add private.pem to your .gitignore. Sign every upload by passing the private key:</p><pre>npx @capawesome/cli apps:liveupdates:upload --private-key private.pem</pre><p>And add the public key to your Capacitor config (the CLI prints it preformatted, with the line breaks stripped, so you can paste it directly):</p><pre>{<br>  &quot;plugins&quot;: {<br>    &quot;LiveUpdate&quot;: {<br>      &quot;publicKey&quot;: &quot;-----BEGIN PUBLIC KEY-----MIGfMA0GCSqGSIb3DQEBAQUAA4G...IDAQAB-----END PUBLIC KEY-----&quot;<br>    }<br>  }<br>}</pre><p>From that point on, your app verifies every downloaded bundle and refuses to apply anything that isn’t signed by your private key. We strongly recommend enabling code signing in production, especially if you operate multiple channels or self-host your bundles. For the full setup including key rotation considerations, see <a href="https://capawesome.io/docs/cloud/live-updates/advanced/code-signing/">Code Signing</a>.</p><h3>Best Practices</h3><p>Five patterns that consistently separate a smooth live update setup from a painful one.</p><h4>1. Automatic Rollbacks</h4><p>This is the single most important safety net. The pattern: tell the plugin to roll back to the previous bundle if the new one fails to start, and tell it not to retry a bundle that’s already failed once.</p><p>Two config options do the work:</p><pre>{<br>  &quot;plugins&quot;: {<br>    &quot;LiveUpdate&quot;: {<br>      &quot;readyTimeout&quot;: 10000,<br>      &quot;autoBlockRolledBackBundles&quot;: true<br>    }<br>  }<br>}</pre><p>readyTimeout is the deadline: if your app doesn&#39;t call LiveUpdate.ready() within this many milliseconds of starting, the plugin assumes the new bundle is broken and reverts to the previous one on the next launch. autoBlockRolledBackBundles prevents the rollback loop where a broken bundle keeps getting re-downloaded - once a bundle has triggered a rollback, the device blocks it from ever installing again.</p><p>On the app side, call ready() as early as you can - typically in your root component&#39;s initialization. This is the &quot;I started successfully&quot; signal:</p><pre>import { LiveUpdate } from &#39;@capawesome/capacitor-live-update&#39;;<br><br>await LiveUpdate.ready();</pre><p>You don’t need to wait until your app is fully hydrated. As soon as your bootstrap code has executed without crashing, call ready(). The whole mechanism only works if you do.</p><h4>2. Bundle Size Optimization</h4><p>Bundle size is a user-experience problem: every megabyte is bandwidth on someone’s mobile plan and seconds of waiting. It’s also a deliverability problem — the bigger the bundle, the more updates fail on flaky connections.</p><p>Three optimizations cover most of the wins:</p><ol><li><strong>Drop source maps.</strong> They’re often 75% of bundle size and they don’t belong in production downloads. In Vite, set build.sourcemap: false. In Angular, --source-map=false. If you need source maps for error tracking, upload them to Sentry or your APM separately - don&#39;t ship them to devices.</li><li><strong>Stick with </strong><strong>zip.</strong> Unless you have specific evidence that delta updates will work for your bundle layout (see Decision 3), zip is smaller in practice.</li><li><strong>Move heavy static assets out of the bundle.</strong> Hero images, marketing media, downloadable PDFs — anything large that doesn’t <em>have</em> to live in the bundle should be served from a CDN and loaded on demand.</li></ol><p>Tree-shaking and minification matter too, but most modern build tools handle them by default. Audit with rollup-plugin-visualizer or webpack-bundle-analyzer if your bundle is mysteriously large.</p><p>For a real-world case study going from 48 MB to 9 MB, see <a href="https://capawesome.io/blog/how-to-reduce-the-bundle-size-of-capacitor-live-updates/">How to Reduce the Bundle Size of Capacitor Live Updates</a>.</p><h4>3. Reasonable Update Checks</h4><p>A pattern we see surprisingly often:</p><pre>// Don&#39;t do this.<br>setInterval(() =&gt; {<br>  LiveUpdate.sync();<br>}, 60_000);</pre><p>There’s no reason to poll. The built-in autoUpdateStrategy: &#39;background&#39; already does the right thing - it checks on app start and on resume, with a 15-minute minimum between checks. That&#39;s enough freshness for almost every app, and it doesn&#39;t burn battery, data, or rate limit.</p><p>If you genuinely need to push out an update faster than that, use the <strong>Instant</strong> strategy with a silent push notification. That’s the right tool — polling isn’t.</p><h4>4. Gradual Rollouts</h4><p>You don’t have to release to 100% of users at once. The plugin supports rollouts at the channel level:</p><pre>npx @capawesome/cli apps:liveupdates:upload --rollout-percentage 10</pre><p>That bundle reaches 10% of devices on the channel. You watch your error tracking, your crash dashboards, your support inbox — and if things look good, you bump it up:</p><pre>npx @capawesome/cli apps:liveupdates:rollout --channel production --percentage 50</pre><p>For high-stakes releases, an even safer pattern is <strong>multi-channel rollouts</strong>: a dedicated production-rollout channel for the new bundle, with the app checking the rollout channel first and falling back to the stable channel:</p><pre>import { LiveUpdate } from &#39;@capawesome/capacitor-live-update&#39;;<br><br>const { versionCode } = await LiveUpdate.getVersionCode();<br><br>const rolloutResult = await LiveUpdate.sync({<br>  channel: `production-rollout-${versionCode}`<br>});<br>if (rolloutResult.nextBundleId) {<br>  return;<br>}<br>await LiveUpdate.sync({ channel: `production-${versionCode}` });</pre><p>As confidence grows, you copy the same bundle to the stable channel. The plugin recognizes it’s the same bundle ID and doesn’t re-download anything.</p><p>For the deeper dive, see <a href="https://capawesome.io/blog/how-to-gradually-roll-out-capacitor-live-updates/">How to Gradually Roll Out Capacitor Live Updates</a>.</p><h4>5. Channel Hygiene</h4><p>Channels are cheap, but a few habits keep them tidy:</p><ul><li><strong>Set bundle limits.</strong> Configure a max number of bundles per channel; older ones get garbage-collected automatically.</li><li><strong>Set expirations on short-lived bundles.</strong> If you’re shipping a test bundle for a single QA cycle, use --expires-in-days to clean it up automatically.</li><li><strong>Use protected channels for sensitive deploys.</strong> Protected channels reject any bundle that isn’t code-signed.</li><li><strong>Watch the logs.</strong> The Cloud Console exposes a <a href="https://capawesome.io/docs/cloud/live-updates/logs/">logs view</a> showing every device-to-cloud request — invaluable when “why isn’t user X getting the update?” turns up in your support inbox.</li></ul><h3>End-to-End Example: A Real-World Setup</h3><p>Let’s put all of this together with a real example. The <a href="https://github.com/dhbw-vs/app">DHBW VS app</a> is the official student app for a German university — a Capacitor app shipping to thousands of students across iOS and Android, maintained by a small team. It uses the full recommended stack:</p><ul><li><strong>Strategy:</strong> Always Latest — background download, plus a confirm prompt before applying.</li><li><strong>Versioning:</strong> Versioned channels via native config, no JS-side state.</li><li><strong>Delivery:</strong> Zip.</li><li><strong>Synchronized version codes:</strong> <a href="https://www.npmjs.com/package/commit-and-tag-version">commit-and-tag-version</a> bumps package.json from conventional commits, and <a href="https://capawesome.io/blog/introducing-capver/">Capver</a> mirrors that version into Android and iOS.</li><li><strong>Safety:</strong> autoBlockRolledBackBundles: true, readyTimeout: 10000, ready() called at app start.</li><li><strong>CI/CD:</strong> Two GitHub Actions workflows — one for native releases, one for live updates — both triggered manually via workflow_dispatch to keep release timing in the team&#39;s hands.</li></ul><p>If Capver is new to you, it’s a <a href="https://capawesome.io/blog/introducing-capver/">small open-source CLI from Capawesome</a> that mirrors a single semantic version into iOS, Android, and package.json so they stay aligned across every release. The mapping is the slightly opaque part: a release tagged 6.0.3 becomes Android versionCode 60003 and iOS CURRENT_PROJECT_VERSION 60003 - three two-digit groups for major, minor, and patch. That deterministic mapping is what makes the build-time channel pinning below work without any manual bookkeeping.</p><p>The patterns below are excerpts from that codebase. They’d look nearly identical in any other framework — the Angular wrapper is incidental.</p><h4>Capacitor Config</h4><p>The plugin is configured in capacitor.config.json with the app ID, the update strategy, and the automatic rollback settings:</p><pre>// File: capacitor.config.json<br>{<br>  &quot;appId&quot;: &quot;de.dhbw.vs.standortapp&quot;,<br>  &quot;appName&quot;: &quot;DHBW VS&quot;,<br>  &quot;webDir&quot;: &quot;www&quot;,<br>  &quot;plugins&quot;: {<br>    &quot;LiveUpdate&quot;: {<br>      &quot;appId&quot;: &quot;70922e93-0944-48cc-a560-61135ab291ad&quot;,<br>      &quot;autoBlockRolledBackBundles&quot;: true,<br>      &quot;autoUpdateStrategy&quot;: &quot;background&quot;,<br>      &quot;readyTimeout&quot;: 10000<br>    }<br>  }<br>}</pre><p>autoUpdateStrategy: &#39;background&#39; does the heavy lifting. autoBlockRolledBackBundles: true and readyTimeout: 10000 together implement automatic rollback. No defaultChannel here - the channel is set natively, per platform.</p><h4>Android</h4><p>On Android, the channel name is baked into a string resource at build time, derived from the versionCode:</p><pre>// File: android/app/build.gradle<br><br>android {<br>    defaultConfig {<br>        versionCode 60003<br>        versionName &quot;6.0.3&quot;<br>        resValue &quot;string&quot;, &quot;capawesome_live_update_default_channel&quot;,<br>                 &quot;production-&quot; + defaultConfig.versionCode<br>        // ...<br>    }<br>}</pre><p>Every Android build pins itself to production-60003. When capver bumps the version code to 60004, the channel name changes automatically - there&#39;s no JS code to update.</p><h4>iOS</h4><p>On iOS, the equivalent is a single Info.plist key that interpolates the project version:</p><p>File: ios/App/App/Info.plist</p><pre>&lt;key&gt;CapawesomeLiveUpdateDefaultChannel&lt;/key&gt;<br>&lt;string&gt;production-$(CURRENT_PROJECT_VERSION)&lt;/string&gt;</pre><p>$(CURRENT_PROJECT_VERSION) is the iOS equivalent of versionCode, and capver keeps it in sync with the Android version on every release.</p><h4>App Initialization</h4><p>At startup, the root component calls ready() immediately and registers a listener for nextBundleSet to prompt the user when a new bundle has been staged. In Angular this lives in the root component&#39;s constructor; in React it would be a useEffect, in Vue an onMounted:</p><pre>// File: app.component.ts<br><br>private initializeLiveUpdate(): void {<br>  if (!Capacitor.isNativePlatform()) {<br>    return;<br>  }<br>  void LiveUpdate.ready();<br>  LiveUpdate.addListener(&#39;nextBundleSet&#39;, async event =&gt; {<br>    if (!event.bundleId) {<br>      return;<br>    }<br>    const confirmed = confirm(&#39;A new version is available. Install it now?&#39;);<br>    if (confirmed) {<br>      await LiveUpdate.reload();<br>    }<br>  });<br>}</pre><p>Two things to notice. First, ready() is called unconditionally on app start, before anything else can fail - this is what makes automatic rollback work. Second, the prompt only fires when event.bundleId is non-null, which happens once the bundle has been fully downloaded and staged. The user never waits for a network call.</p><h3>GitHub Actions</h3><p>The live update workflow is intentionally minimal. One input — the channel name — and one job that builds the web bundle in the cloud and deploys it to that channel.</p><p><strong>File: .github/workflows/live-update.yml</strong></p><pre>on:<br>  workflow_dispatch:<br>    inputs:<br>      channel:<br>        description: &quot;Channel name&quot;<br>        required: true<br>        type: string<br><br>env:<br>  CAPAWESOME_CLI_VERSION: 4.9.3<br>  CAPAWESOME_CLOUD_APP_ID: 00000000-0000-0000-0000-000000000000<br>  NODE_VERSION: 24<br><br>jobs:<br>  deploy-live-update:<br>    name: Deploy Live Update<br>    runs-on: ubuntu-latest<br>    steps:<br>      - uses: actions/setup-node@v4<br>        with:<br>          node-version: ${{ env.NODE_VERSION }}<br>      - name: Authenticate with Capawesome Cloud<br>        run: npx @capawesome/cli@${{ env.CAPAWESOME_CLI_VERSION }} login --token ${{ secrets.CAPAWESOME_CLOUD_TOKEN }}<br>      - name: Create channel<br>        env:<br>          CHANNEL: ${{ inputs.channel }}<br>        run: |<br>          npx @capawesome/cli@${{ env.CAPAWESOME_CLI_VERSION }} apps:channels:create \<br>            --app-id ${{ env.CAPAWESOME_CLOUD_APP_ID }} \<br>            --name &quot;$CHANNEL&quot; \<br>            --ignore-errors<br>      - name: Build and deploy live update<br>        env:<br>          CHANNEL: ${{ inputs.channel }}<br>        run: |<br>          npx @capawesome/cli@${{ env.CAPAWESOME_CLI_VERSION }} apps:builds:create \<br>            --app-id ${{ env.CAPAWESOME_CLOUD_APP_ID }} \<br>            --platform web \<br>            --channel &quot;$CHANNEL&quot; \<br>            --git-ref ${{ github.sha }} \<br>            --yes</pre><p>A few details worth calling out:</p><ul><li><strong>workflow_dispatch instead of auto-on-merge.</strong> Live updates ship when a human says they do. Merging to main doesn&#39;t trigger a release - the team triggers the workflow when they&#39;re ready, with the channel name they want to deploy to. The same dispatch model is used for native releases.</li><li><strong>apps:channels:create --ignore-errors is idempotent.</strong> First deploy to a brand-new native version creates the channel; every deploy after that is a no-op. No conditional logic needed, and unused channels get cleaned up automatically by Capawesome Cloud - there&#39;s nothing to garbage-collect on your side.</li><li><strong>apps:builds:create --platform web builds in the cloud, not on the runner.</strong> The web bundle is built inside Capawesome Cloud, so every deploy uses the same environment, the same Node version, and the same secrets. No &quot;works on my machine,&quot; no drift between local builds and CI builds.</li><li><strong>Pinning the CLI version.</strong> @capawesome/cli@4.9.3 is pinned. Workflows are reproducible, and CLI upgrades happen on purpose, not silently.</li></ul><p>To deploy a live update for native version 60003, the team triggers the workflow with production-60003 as the channel. The Cloud builds the bundle from the current main, uploads it, and devices on native version 60003 pick it up on their next launch.</p><p>For the matching native release workflow (which builds and submits binaries to TestFlight and the Play Store), the <a href="https://github.com/dhbw-vs/app/blob/main/.github/workflows/release.yml">release.yml</a> in the same repo is a good companion read.</p><h3>Bonus: Video Walkthrough</h3><p>If you’d rather see the full Capawesome Cloud setup walked through end-to-end, this companion video covers the first deployment, channel setup, and runtime behavior in a real Capacitor project:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FrF1yxzR8tnE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DrF1yxzR8tnE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FrF1yxzR8tnE%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/dfad1363c0c620d864ba8fb569d08ea9/href">https://medium.com/media/dfad1363c0c620d864ba8fb569d08ea9/href</a></iframe><h3>Get Started</h3><p>You have two paths:</p><ol><li><strong>With an AI agent.</strong> Add the <a href="https://capawesome.io/blog/announcing-open-source-ai-agent-skills-for-capacitor/">Capawesome agent skills</a> to your project and ask Claude Code or Cursor to set up live updates. The capawesome-live-updates skill walks the agent through everything: creating the Cloud app, installing the SDK, wiring up channels, generating signing keys, and integrating with CI/CD.</li></ol><p><strong>2. By hand.</strong> Follow the <a href="https://capawesome.io/docs/cloud/live-updates/setup/">Live Updates setup guide</a>. Start with autoUpdateStrategy: &#39;background&#39; plus a nextBundleSet listener for the &quot;Always Latest&quot; prompt, versioned channels in your native config, and the rollback options on. That&#39;s a production-ready setup in under an hour.</p><p><a href="https://capawesome.io/">Try Capawesome Cloud Free</a></p><h3>Conclusion</h3><p>Live updates are the difference between releasing fixes in minutes and releasing them in days. The recommended path is the same for almost every team: the <strong>Always Latest</strong> strategy so users are informed when an update is ready, <strong>versioned channels</strong> configured natively so version compatibility is automatic, <strong>zip</strong> delivery for predictable bundle sizes, <strong>automatic rollback</strong> so a broken bundle is self-healing, and <strong>code signing</strong> when you ship to production. Everything else — rollouts, force updates, push-driven hotfixes, self-hosting — sits on top of that core.</p><p>If you want to go deeper from here:</p><ul><li><a href="https://capawesome.io/blog/exploring-the-capacitor-live-update-api/">Exploring the Capacitor Live Update API</a> — a tour of every method the plugin exposes, with code samples for each.</li><li><a href="https://capawesome.io/blog/how-live-updates-for-capacitor-work/">How Live Updates for Capacitor Work Under the Hood</a> — the internals: server paths, platform-specific storage, code signing mechanics, and the App Store compliance story in detail.</li><li><a href="https://capawesome.io/blog/how-to-reduce-the-bundle-size-of-capacitor-live-updates/">How to Reduce the Bundle Size of Capacitor Live Updates</a> — the optimization playbook with a real before-and-after.</li><li><a href="https://capawesome.io/blog/capacitor-app-update-guide/">Capacitor App Updates: The Complete Guide</a> — pairing live updates with native app store updates for a complete update strategy.</li></ul><p>Questions, feedback, or war stories from your own live update rollout? Drop into the <a href="https://discord.gg/VCXxSVjefW">Capawesome Discord server</a> — that’s where we’re always happy to chat. And if you’d like the next deep-dive in your inbox, subscribe to the <a href="https://capawesome.io/newsletter">Capawesome newsletter</a>.</p><p><em>Originally published at </em><a href="https://capawesome.io/blog/capacitor-live-updates-guide/"><em>https://capawesome.io</em></a><em> on May 16, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7615ddad83f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web app or mobile app? You don’t have to choose.]]></title>
            <link>https://medium.com/@dayanajabif/web-app-or-mobile-app-you-dont-have-to-choose-a15e885086de?source=rss-f05e27e8a50e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a15e885086de</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ios-development]]></category>
            <category><![CDATA[android-development]]></category>
            <dc:creator><![CDATA[Dayana Jabif]]></dc:creator>
            <pubDate>Tue, 12 May 2026 16:52:15 GMT</pubDate>
            <atom:updated>2026-05-12T16:52:15.029Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5zo4rU__ysGihz3y" /></figure><p>If you’ve been building for the web, chances are you’ve asked yourself at some point:</p><p>And if you have, you probably already know the usual trade-offs:</p><ul><li>Rewriting everything natively is expensive</li><li>Maintaining two codebases is painful</li><li>Learning mobile development takes time</li></ul><p>But what if you didn’t have to choose?</p><p>With Capacitor, you can turn your existing web app into a real mobile app, without rewriting it from scratch.</p><p>You keep your stack, your codebase, your velocity, and extend it to iOS and Android.</p><p>At its core, Capacitor is a native runtime that lets you run your web app (React, Angular, Vue, or even plain HTML) inside a native container, while giving you access to native device features through plugins.</p><p>That means:</p><ul><li>You keep your web codebase</li><li>You ship to iOS and Android</li><li>You progressively enhance with native capabilities</li></ul><p>Yes, but that’s only part of the story.</p><p>Modern mobile apps built with Capacitor are not just “wrapped websites”. You get:</p><ul><li>Native APIs (camera, filesystem, push notifications, etc.)</li><li>Full control over native projects when needed</li><li>A bridge that lets your web code talk to native code seamlessly</li></ul><p>And this is where plugins come in.</p><p>Capacitor plugins let you access device features using simple JavaScript APIs.</p><p>For example:</p><ul><li>Camera</li><li>Push Notifications</li><li>Background behavior</li><li>Filesystem</li><li>Offline support</li></ul><p>All of this is handled via plugins, so your web code can talk to native APIs without switching languages. Instead of learning Swift or Kotlin, you can stay in your web stack and still build powerful mobile experiences.</p><p>Now, here’s the part people often underestimate: UI/UX.</p><p>A web app ≠ a great mobile app by default.</p><p>You’ll likely need to adapt:</p><ul><li>Navigation patterns</li><li>Gestures</li><li>Layouts for smaller screens</li><li>Platform-specific expectations</li></ul><p>One popular solution is Ionic Framework, which provides mobile-optimized UI components that feel native on both iOS and Android.</p><p>But it’s not the only option.</p><p>You can also:</p><ul><li>Use your existing design system</li><li>Combine with Tailwind or other CSS frameworks</li><li>Go fully custom</li></ul><p>Capacitor doesn’t force you into any UI layer — it just gives you the runtime.</p><p>Here’s where things get really interesting.</p><p>With tools like <a href="https://capawesome.io/">Capawesome</a>, you can push updates to your app instantly, without waiting for app store approvals.</p><p>That means:</p><ul><li>Fix bugs in production instantly</li><li>Ship small improvements continuously</li><li>Iterate faster, like you would on the web</li></ul><p>It fundamentally changes how you build and maintain mobile apps.</p><p>If you’ve ever dealt with mobile releases, you know they can be… complicated.</p><p>Signing, builds, store submissions — it’s a lot.</p><p>Platforms like <a href="https://capawesome.io/">Capawesome</a> bring modern CI/CD workflows to mobile apps:</p><ul><li>Automated builds</li><li>Seamless deployments</li><li>Integrated live updates</li><li>Less manual work</li></ul><p>So you can focus on building features instead of fighting the release process.</p><p>The answer is: both.</p><p>You don’t need to choose between:</p><ul><li>Speed vs reach</li><li>Web vs native</li><li>Simplicity vs capability</li></ul><p>With Capacitor and the right tooling, you can:</p><ul><li>Start with a web app</li><li>Turn it into a mobile app</li><li>Gradually enhance it with native features</li></ul><p>All while keeping a single codebase.</p><p>All sounds great… but where do you even start? 😄 Shoot me a DM and I’ll help you figure it out.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/web-app-mobile-you-dont-have-choose-dayana-jabif-xcqmf"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a15e885086de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build Mobile Apps with Any Web Framework and Capacitor]]></title>
            <link>https://medium.com/@dayanajabif/build-mobile-apps-with-any-web-framework-and-capacitor-0d1485f38f0b?source=rss-f05e27e8a50e------2</link>
            <guid isPermaLink="false">https://medium.com/p/0d1485f38f0b</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Dayana Jabif]]></dc:creator>
            <pubDate>Mon, 11 May 2026 00:00:14 GMT</pubDate>
            <atom:updated>2026-05-12T17:03:39.651Z</atom:updated>
            <content:encoded><![CDATA[<p>If your team already ships a modern web app with React, Angular, Vue, Svelte, or another framework, you don’t need to start from scratch to reach the iOS and Android stores. Capacitor lets you wrap your existing frontend code in native projects and add mobile capabilities where you actually need them.</p><p>This guide walks through the full workflow across frameworks, from setup and native platform generation to Xcode and Android Studio integration, live reload, and release automation. We also cover common pitfalls, how to add native functionality with plugins, and where Capawesome Cloud fits when you want to automate builds and deployment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eor_zDxSb9G9ftev.png" /></figure><h3>Why Capacitor Works with Any Web Framework</h3><p>Capacitor is an open-source runtime developed by the Ionic team that runs your web app as a native iOS and Android app. It packages your built web assets into a native shell and renders them inside a WebView, while a thin native bridge exposes device APIs to your JavaScript code through plugins.</p><p>Because Capacitor only cares about your final build output, the framework you use to produce that output is mostly irrelevant. Whether you’re building with React, Angular, Vue, Svelte, or another JavaScript framework, the core workflow stays almost identical. In practice, the biggest differences are your build command and the output directory you point Capacitor at.</p><p>Start from your existing web project root.</p><h3>1. Install Capacitor</h3><pre>npm install @capacitor/core@latest<br>npm install -D @capacitor/cli@latest</pre><h3>2. Initialize Capacitor</h3><pre>npx cap init</pre><p>The CLI prompts you for your app name, app ID (e.g. io.company.app), and web output directory (dist, build, www, .output/public, and so on). See <a href="https://capawesome.io/blog/build-mobile-apps-with-any-web-framework-and-capacitor/#framework-specific-configuration">Framework-Specific Configuration</a> below for typical values per framework.</p><h3>3. Add Native Platforms</h3><pre>npm install @capacitor/ios@latest @capacitor/android@latest<br>npx cap add ios<br>npx cap add android</pre><h3>4. Build Web Assets and Sync</h3><pre>npm run build<br>npx cap sync</pre><h3>5. Open Native Projects</h3><pre>npx cap open ios<br>npx cap open android</pre><p>This becomes your core dev loop: build -&gt; sync -&gt; open/run.</p><h3>Framework-Specific Configuration</h3><p>Most of the workflow is identical across frameworks. The main difference is the webDir value in your <a href="https://capacitorjs.com/docs/config">Capacitor configuration</a> file, which must match your framework&#39;s build output directory. <a href="https://capawesome.io/blog/build-mobile-apps-with-any-web-framework-and-capacitor/#framework-specific-configuration">Check here</a> for a typical capacitor.config.ts for each framework.</p><p>If you prefer JSON, you can use capacitor.config.json with the same fields. If webDir doesn&#39;t match your real build output, you&#39;ll see a blank screen on launch - see <a href="https://capawesome.io/blog/build-mobile-apps-with-any-web-framework-and-capacitor/#common-pitfalls-and-fixes">Common Pitfalls</a> below.</p><h3>Connecting Your Project to Xcode and Android Studio</h3><p>After cap add, Capacitor creates two native projects:</p><p>Your frontend stays the source of truth for UI and business logic. The native projects handle permissions, signing, native configuration, and app store packaging.</p><p>A practical daily workflow looks like this:</p><ol><li>Change web code.</li><li>Run npm run build.</li><li>Run npx cap sync.</li><li>Run and debug from Xcode or Android Studio.</li></ol><p>When native settings change (permissions, Gradle config, Xcode signing), edit the native project directly. When web assets change, always rebuild and sync to avoid platform drift.</p><h3>Live Reload Workflow During Development</h3><p>To speed up feedback during development, you can use live reload on a real device:</p><pre>npx cap run android -l --external<br>npx cap run ios -l --external</pre><p>A few prerequisites and gotchas:</p><ul><li>Start your framework’s dev server first (npm run start, npm run dev, etc.) and make sure your computer and device are on the same network.</li><li>--external binds the dev server to all network interfaces, so allow incoming connections on the dev server port if your firewall asks.</li><li>Live reload is a development workflow, not a production deployment strategy — disable it before shipping a real build.</li></ul><h3>App Icons and Splash Screens</h3><p>Instead of manually resizing assets, generate platform assets with the official tool:</p><pre>npm install -D @capacitor/assets@latest<br>npx capacitor-assets generate --ios<br>npx capacitor-assets generate --android</pre><p>Recommended workflow:</p><ol><li>Keep your icon and splash screen original files in a resources/ directory.</li><li>Generate iOS and Android assets from those sources.</li></ol><p>Tool reference: <a href="https://github.com/ionic-team/capacitor-assets">@capacitor/assets</a>.</p><h3>Adding Native Functionality with Plugins</h3><p>Use plugins when your app needs device features that a browser alone can’t provide reliably.</p><p>In many cases, native plugins are also the more performant option. Browser APIs are powerful, but plugins can use native execution paths and platform-specific capabilities that are better suited for heavy mobile workloads.</p><p>A few examples:</p><p>Plugin usage is intentionally minimal — call a method, get a typed result. Here’s how taking a photo with the Camera plugin looks from your web code:</p><pre>import { Camera, CameraResultType } from &quot;@capacitor/camera&quot;;<br><br>const takePhoto = async () =&gt; {<br>  const photo = await Camera.getPhoto({<br>    quality: 90,<br>    allowEditing: false,<br>    resultType: CameraResultType.Uri<br>  });<br><br>  return photo.webPath;<br>};</pre><p>The returned webPath can be assigned directly to an &lt;img&gt; src, so the same call works whether the user took a fresh shot or picked an existing photo from their gallery.</p><p>Live Updates let you ship web-layer changes (HTML, CSS, JavaScript) without waiting for app store review on every bug fix. This shortens release cycles and improves response time for production issues.</p><p>But the limits matter:</p><ul><li>Live Updates don’t replace native binary updates.</li><li>Native changes (a new plugin, a native SDK update, an entitlement change) still require app store builds.</li></ul><p>Use Live Updates for fast iteration on the web layer, and native releases for native code changes.</p><p>For deeper context, read <a href="https://capawesome.io/blog/how-live-updates-for-capacitor-work/">How Live Updates for Capacitor Work</a> and <a href="https://capawesome.io/blog/how-live-updates-are-changing-mobile-app-deployment/">How Live Updates Are Changing Mobile App Deployment</a>.</p><h3>Native vs Web Changes Decision Matrix</h3><p>Use this quick matrix to decide whether you should ship through Live Updates or create a new native store build:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K1gpRENvPRY9_GdBbEAQdQ.png" /><figcaption>Native vs Web Changes Decision Matrix</figcaption></figure><p>If a change touches native code or native project configuration, plan for a store release. If it’s only web assets, Live Updates is typically the faster path.</p><h3>Common Pitfalls and Fixes</h3><p>Teams usually hit the same issues during the first week of integration. These are the most common ones and how to fix them quickly:</p><ul><li><strong>Blank screen on app launch:</strong> webDir doesn&#39;t match your real build output. Run npm run build, confirm the folder exists, update capacitor.config.*, then run npx cap sync.</li><li><strong>Web changes not visible in the native app:</strong> you changed web code but skipped rebuild and sync. Always run npm run build &amp;&amp; npx cap sync before testing in Xcode or Android Studio.</li><li><strong>Plugin works on one platform only:</strong> platform setup, permissions, or native project files are incomplete. Recheck the plugin installation docs, update the iOS and Android configs, then run npx cap sync.</li><li><strong>iOS signing errors in Xcode:</strong> team, bundle ID, provisioning profile, and certificate are misaligned. Verify those values in Xcode and your Apple Developer account.</li><li><strong>Android build failures after SDK updates:</strong> Gradle and Android SDK versions drift apart. Align toolchain versions and run a clean rebuild in Android Studio.</li></ul><h3>Performance Tips in the WebView</h3><p>Performance issues in mobile WebViews usually come from oversized assets and heavy startup work. These practices consistently improve startup time and runtime responsiveness:</p><ul><li>Prefer native plugins for device-heavy operations when possible. For example, the <a href="https://capawesome.io/docs/plugins/audio-player/">Audio Player</a> plugin uses native playback capabilities and supports background audio, which is important for uninterrupted playback when the app isn’t in the foreground. In real projects, native integrations can also improve reliability and throughput for large file operations, as described in <a href="https://capawesome.io/blog/how-to-wrap-an-angular-app-with-capacitor-and-firebase/">How to Wrap an Angular App with Capacitor and Firebase</a>.</li><li>Keep your initial JavaScript bundle small with route-based code splitting, and defer non-critical scripts until after first render.</li><li>Optimize images and use modern formats where possible — they’re cheap on a dev machine and expensive on a phone.</li><li>Avoid large synchronous tasks during app startup, since they block the WebView from rendering the first paint.</li><li>Test on lower-end Android devices (not just current flagships) and watch memory-heavy screens like file previews and long lists, which are where mobile WebViews crack first.</li></ul><h3>Automating Build and Deploy with Capawesome Cloud</h3><p>Once your app runs reliably on real devices, the next step is automating delivery. Capawesome Cloud handles the parts that would otherwise eat your time: <a href="https://capawesome.io/docs/cloud/native-builds/setup/">Native Builds</a> produces reproducible iOS and Android binaries in a consistent environment, <a href="https://capawesome.io/docs/cloud/live-updates/setup/">Live Updates</a> ships web-layer releases between store submissions, and <a href="https://capawesome.io/docs/cloud/app-store-publishing/">App Store Publishing</a> delivers builds straight to TestFlight or Google Play.</p><p>A pattern that works well in practice is combining the two release tracks — ship stable native builds through the stores, and use Live Updates for fast iteration on the web layer in between. Wire it all together with <a href="https://capawesome.io/docs/cloud/automations/">Automations</a> so the build and deploy pipeline triggers automatically on commit, branch, or tag.</p><h3>Try Capawesome Cloud</h3><p>Automate native builds, Live Updates, and app store delivery so your team can focus on product work instead of release chores.</p><p><a href="https://capawesome.io/">Try Capawesome Cloud Free</a></p><h3>Conclusion</h3><p>Capacitor gives teams a practical way to ship iOS and Android apps from a single modern web codebase. The core workflow stays consistent across React, Angular, Vue, Svelte, and other frameworks: build web assets, sync the native shells, validate on devices, and automate delivery.</p><p>If you have questions, join the <a href="https://discord.gg/VCXxSVjefW">Capawesome Discord server</a> and ask us anything related to Capacitor. To stay up to date on new guides and releases, subscribe to the <a href="https://capawesome.io/newsletter">Capawesome newsletter</a>.</p><p><em>Originally published at </em><a href="https://capawesome.io/blog/build-mobile-apps-with-any-web-framework-and-capacitor/"><em>https://capawesome.io</em></a><em> on May 11, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0d1485f38f0b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Day Your Mobile Release Process Breaks — And How CI/CD Fixes It]]></title>
            <link>https://medium.com/learn-ionic-framework/the-day-your-mobile-release-process-breaks-and-how-ci-cd-fixes-it-892162f0caab?source=rss-f05e27e8a50e------2</link>
            <guid isPermaLink="false">https://medium.com/p/892162f0caab</guid>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ionic]]></category>
            <category><![CDATA[capacitor]]></category>
            <dc:creator><![CDATA[Dayana Jabif]]></dc:creator>
            <pubDate>Wed, 11 Mar 2026 13:07:36 GMT</pubDate>
            <atom:updated>2026-03-23T12:14:23.749Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Day Your Mobile Release Process Breaks (And Why CI/CD Fixes It)</h3><p>At some point, every mobile team hits the same realization 🤯.</p><p><strong>CI/CD is the moment your app stops depending on one person’s laptop.</strong></p><p>It’s the moment when builds become reproducible, releases become predictable, and shipping stops feeling stressful.</p><p><strong>Suddenly you have:</strong></p><ul><li>reproducible builds</li><li>fewer app store rejections</li><li>no certificate headaches</li><li>faster hotfixes</li><li>and a team that can ship without fear</li></ul><p>But many mobile apps still ship the old way.</p><p>Manually.</p><p>And that’s where the problems start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pcEScMp07oyK0H-5k20IFQ.jpeg" /></figure><h3>The Hidden Cost of Manual Mobile Releases</h3><p>Every team eventually runs into the pain of manual releases.</p><p>If your team hasn’t yet, don’t worry.<br>It will happen 😬.</p><p>Manual release processes usually look something like this:</p><ul><li>someone has “the machine that does the builds”</li><li>the keystore is somewhere… hopefully backed up</li><li>certificates expire at the worst possible moment</li><li>the release checklist lives in a Notion doc nobody reads</li><li>and everyone holds their breath during release day</li></ul><p>And then one day it happens…</p><p>You need to ship an urgent fix.</p><p>But the person who usually makes the build is…</p><p>on vacation.</p><p>Somewhere.</p><p>Possibly hiking.</p><p>Maybe halfway up a mountain.</p><p>With no signal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gh4VHogn71rSgqLLFv8BwQ.png" /></figure><p>Now the team has two options:</p><ol><li>Wait until they come back.</li><li>Try to reproduce the build on another machine and pray it works.</li></ol><p>Neither option is great.</p><p><strong>A proper CI/CD pipeline solves exactly this problem.</strong></p><p>No panic.<br>No mystery steps.<br>No “special laptop required”.</p><p>Anyone on the team can trigger a reproducible build at any time.</p><p>And that’s a huge difference.</p><p>Studies on software delivery show that teams with mature CI/CD practices deploy <strong>up to 46× more frequently</strong> and experience <strong>significantly fewer failures</strong> than teams without automation.</p><p>That’s not just a DevOps improvement.</p><p><a href="https://capawesome.io/blog/why-every-capacitor-team-needs-ci-cd/">That’s a business advantage</a>.</p><h3>CI/CD for Web Apps Is Easy</h3><p>If you’ve set up CI/CD for a web application before, you might wonder what the big deal is.</p><p>For web apps, the process is usually simple:</p><ol><li>Install dependencies</li><li>Run tests</li><li>Build static files</li><li>Deploy to a server or CDN</li></ol><p>Done.</p><p>But mobile apps are a completely different story 😵‍💫.</p><h3>Why Mobile CI/CD Is Harder</h3><p>Mobile apps introduce complexity that simply doesn’t exist in web deployments.</p><p>Let’s break down the main four reasons.</p><h4>1. Native compilation</h4><p>Mobile apps include native Android and iOS projects.</p><p>That means your pipeline must build:</p><ul><li>Android with <strong>Gradle</strong></li><li>iOS with <strong>Xcode</strong></li></ul><p>And here’s the catch:</p><p><strong>Xcode only runs on macOS.</strong></p><p>So your CI/CD environment needs macOS build machines in order to compile iOS apps.</p><p>This alone already makes mobile CI/CD more complex than most web pipelines.</p><h4>2. Code signing</h4><p>Mobile apps must be cryptographically signed before distribution.</p><p><strong>For Android, you need:</strong></p><ul><li>a keystore</li><li>signing configuration</li><li>secure key storage</li></ul><p><strong>For iOS, things get even more complicated:</strong></p><ul><li>distribution certificates</li><li>provisioning profiles</li><li>Apple Developer account integration</li></ul><p>Managing these assets securely inside CI/CD pipelines is one of the most common causes of mobile build failures.</p><h4>3. Two platforms, double the complexity</h4><p>Most teams ship to both platforms: Android and iOS.</p><p>Every release potentially produces two different artifacts: APK or AAB, and IPA.</p><p>Each platform has its own:</p><ul><li>toolchain</li><li>signing process</li><li>configuration</li><li>store submission flow</li></ul><p>So your pipeline has to orchestrate <strong>two completely different ecosystems</strong>.</p><h4>4. App store review cycles</h4><p>Unlike web apps, mobile apps cannot deploy instantly (*).</p><p>Every update must go through store review:</p><ul><li>Apple App Store</li><li>Google Play Store</li></ul><p>This introduces delays that can make rapid iteration harder.</p><p>(*) But here’s where things get interesting. Many teams combine CI/CD with <a href="https://cloud.capawesome.io/live-updates/"><strong>Live Updates</strong></a> to bypass this bottleneck for web-layer changes.</p><p><strong>If you’re building your mobile app with Capacitor, you already have a bit of a superpower: your app’s UI, logic, and assets live in the web layer. Which means that many changes don’t actually require a full app store submission.</strong></p><p>Instead of: wait → review → wait → approval → release</p><p>You can simply push updated web assets directly to your users.</p><p>No review queue.<br>No waiting days for approval.<br>No staring nervously at Native Stores.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t8mr7QKLzvRekYCL2eU4dw.jpeg" /></figure><p>Think of it like deploying a web app… except it’s already installed on thousands of devices. Suddenly hotfixes, small UI tweaks, copy changes, and minor improvements can ship in minutes instead of days 🚀.</p><p>And your users get the update the next time they open the app — like magic.</p><p>Not bad for what is essentially a <strong>web deployment disguised as a mobile update</strong>.</p><h3>The Real Goal of CI/CD</h3><p><strong>CI/CD is not just about automation. It’s about making releases boring.</strong></p><p>When CI/CD is done right:</p><ul><li>builds are reproducible</li><li>releases are predictable</li><li>failures are easier to diagnose</li><li>hotfixes ship quickly</li></ul><p>High-performing DevOps teams are able to deploy multiple times per day, while low-performing teams may deploy only once every several months.</p><p>Automation is what closes that gap.</p><h3>CI/CD for Capacitor Apps</h3><p>Capacitor apps add another dimension to the pipeline.</p><p>Your CI/CD system needs to handle:</p><ul><li>web builds</li><li>native sync</li><li>Android builds</li><li>iOS builds</li><li>code signing</li><li>artifact storage</li><li>distribution to testers or stores</li></ul><p>Setting all this up manually with generic CI tools like GitHub Actions is possible.</p><p>But it often requires a lot of configuration and ongoing maintenance.</p><p>That’s where <a href="https://capawesome.io/blog/choosing-the-right-ci-cd-approach-for-capacitor-apps/">specialized mobile CI/CD platforms</a> can help 🥁.</p><h3>Automating Mobile Builds with Capawesome Cloud</h3><p>One solution designed specifically for Capacitor apps is <strong>Capawesome Cloud</strong>.</p><p>👉 <a href="https://cloud.capawesome.io/">https://cloud.capawesome.io/</a></p><p><strong>Capawesome Cloud provides CI/CD infrastructure tailored for mobile development.</strong></p><p>Instead of maintaining complex pipelines, you can trigger mobile builds directly from your Git repository.</p><p><strong>Typical workflow:</strong></p><ol><li>Connect your Git repository</li><li>Trigger builds from a branch, tag, or commit</li><li>Build Android and iOS apps in the cloud</li><li>Download artifacts (APK, AAB, IPA)</li><li>Distribute builds to testers or stores</li></ol><p>The platform takes care of many of the painful parts of mobile CI/CD:</p><ul><li>manage Android and iOS build environments</li><li>secure certificate and keystore management</li><li>reproducible builds from Git references</li><li>artifact storage and distribution</li></ul><p><strong>I know it sounds like magic… but sometimes the best engineering tricks feel that way 🪄.</strong></p><h3>Migrating from Appflow (or Any Other CI/CD Tool)</h3><p>Many teams in the Ionic ecosystem are currently reevaluating their CI/CD setup.</p><p>Especially with the <strong>sunsetting of Appflow</strong>.</p><p>The good news is that <a href="https://capawesome.io/blog/migrating-from-ionic-appflow-to-capawesome-cloud/">migrating to Capawesome Cloud </a>is often easier than expected.</p><p>Because the APIs and update strategies are so similar, most teams can migrate without major architectural changes to their apps.</p><p>Beyond the migration itself, many teams choose Capawesome Cloud because it provides:</p><ul><li><strong>Native builds, Live Updates, and store publishing in one platform</strong></li><li><strong>3–5× faster builds with modern infrastructure</strong></li><li><strong>significantly lower costs compared to Appflow</strong></li><li><strong>active development and new features</strong> instead of a platform approaching end-of-life</li></ul><blockquote>In other words, migrating isn’t just about replacing Appflow — it’s an opportunity to modernize your mobile CI/CD pipeline and simplify your release workflow.</blockquote><h3>Final Thoughts</h3><p>CI/CD is one of the highest-leverage improvements a mobile team can make.</p><p>It reduces risk.<br>It speeds up releases.<br>And it removes a surprising amount of stress from release days.</p><p>If you’re still doing mobile releases manually, the cost is probably higher than it seems — in time, in risk, and in the releases that never happen because shipping is too painful.</p><p>Automation changes that.</p><p><strong>If you’re building Capacitor apps and want help: setting up CI/CD from scratch, improving your current pipeline, or migrating from Appflow or another platform, feel free to reach out.</strong></p><p>I’m always happy to help teams design a reliable mobile build and release workflow.</p><p>You can explore <a href="https://cloud.capawesome.io/"><strong>Capawesome Cloud</strong></a> and if you have any questions or run into issues with mobile CI/CD, feel free to message me.</p><p><a href="https://x.com/dayujabif">Follow me on X </a>for more content like this.</p><p>Happy shipping 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=892162f0caab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learn-ionic-framework/the-day-your-mobile-release-process-breaks-and-how-ci-cd-fixes-it-892162f0caab">The Day Your Mobile Release Process Breaks — And How CI/CD Fixes It</a> was originally published in <a href="https://medium.com/learn-ionic-framework">Learn Ionic Framework</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customizing Ionic Components — How to build any UI with Ionic]]></title>
            <link>https://medium.com/learn-ionic-framework/customizing-ionic-components-how-to-build-any-ui-with-ionic-d932a19b9ca9?source=rss-f05e27e8a50e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d932a19b9ca9</guid>
            <category><![CDATA[ionic]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[web-components]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Dayana Jabif]]></dc:creator>
            <pubDate>Thu, 21 Oct 2021 11:06:50 GMT</pubDate>
            <atom:updated>2021-10-21T11:06:50.084Z</atom:updated>
            <content:encoded><![CDATA[<h3>Customizing Ionic Components — How to build any UI with Ionic</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*to8_Kt7j32PvTAa6.png" /></figure><p>In this post we want to share with you the recipe we use at <a href="https://ionicthemes.com/">IonicThemes</a> to build our starter templates. Hopefully you would learn how to approach the task of building <strong>reusable UI kits</strong> or design systems and create your own components to <strong>improve the efficiency</strong> in future projects.</p><p>I would like to start this post by talking about the term “<strong>Composition</strong>”. I believe the essence of software development is composition. And by composition I mean: <strong>The act of combining parts or elements to form a bigger element.</strong></p><p>Compositions are formed by adding new objects to the previous ones, so that each of the latter is part of the former.</p><p>The process of software development is breaking down large problems into smaller ones.</p><p>Then, we can build components to solve those smaller problems, and compose them together to form a complete application.</p><h4>Look around: composition is everywhere!</h4><p>Components can be very diverse. We could define a component as something that can be useful on its own or that can also be combined with another element to form a bigger one.</p><p>Now think about this idea recursively. Because composition has no limits. You can compose objects as many times as you want.</p><p>But, composition is not only about software, it’s around us everywhere.</p><p>Almost everything in this world is made up of different elements or components and can be broken down into smaller pieces.</p><p>Getting back to building Ionic applications, we can divide elements in two categories: <strong>UI Components and Functionalities</strong>.</p><p>Let me show you a clear example of how we can apply composition when creating a classic Sign Up form.</p><h3>Creating a Sign-up Form with Ionic components</h3><p>For instance, let’s start by combining a few inputs, labels, and a button. We can agree that this is a decent sign-up form, right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*IV0VzryxJPvlDQyW.png" /></figure><p>But, let’s go a step further and think about what will happen when the user submits the form with an invalid value. The app should suggest that there are existing errors which must be corrected. As a result, the user experience will be improved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*7UuE-3DI1cWC3vj-.png" /></figure><p>Also, adding a <a href="https://ionicthemes.com/templates/features/show-hide-password">show/hide password component</a> is really helpful to improve the UX for users on mobile devices or small screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*ZvDx5D9bzmC08nc-.png" /></figure><p>Nowadays, we also need to add social sign in to the sign-up form, because nobody wants to remember another password. Also, <a href="https://ionicthemes.com/tutorials/firebase-authentication-in-ionic-framework-apps#ionic-authenication-options">adding social sign in to our mobile apps</a> has a lot of benefits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*nXnI8q1OLGrwL6xc.png" /></figure><p>Do you see the difference between the first and the last form example? Picture this process as a composition of different elements, we combined different elements (labels, inputs, buttons, copy) and interactions (validations, hints, OAuth integrations) to drastically improve the usability and user experience for the sign-up form.</p><blockquote>By having a bunch of individual pieces already built, you can combine them to create better experiences.</blockquote><p>Well, that was just for the UI of a classic sign up page, but take a second to think of all the pieces and elements that any given app includes such as <a href="https://ionicthemes.com/templates/features/authentication">authentication flows</a>, user management, all the <strong>UI components</strong> such as:</p><ul><li><a href="https://ionicthemes.com/templates/components/lists">Ionic lists</a></li><li><a href="https://ionicthemes.com/templates/components/modals">Ionic modals</a></li><li><a href="https://ionicthemes.com/templates/components/cards">Ionic cards</a></li><li><a href="https://ionicthemes.com/templates/components/side-menu">Ionic menus</a></li><li><a href="https://ionicthemes.com/templates/components/tabs">Ionic tabs</a></li><li><a href="https://ionicthemes.com/templates/components/slider">Ionic slides</a></li><li><a href="https://ionicthemes.com/templates/components/image-gallery">Image gallery in Ionic</a></li><li>and this is just to mention a few.</li></ul><p><strong>As for functionalities:</strong></p><ul><li><a href="https://ionicthemes.com/templates/features/google-maps">Maps in Ionic</a></li><li><a href="https://ionicthemes.com/templates/features/forms">Ionic forms</a></li><li><a href="https://ionicthemes.com/templates/features/navigation">Navigation in Ionic</a></li><li>notifications</li><li>payments</li><li><a href="https://ionicthemes.com/tutorials/ionic-2-image-handling">Ionic image handling</a></li><li>and trust me, the list goes on and on.</li></ul><p><strong>In case you don’t get my point, what I want to show you is how an app is built by composing hundreds of building blocks and functionalities.</strong></p><blockquote>So if you, as a developer, pretend to build every piece of your application…, you are absolutely out of your mind!</blockquote><h3>Using and reusing Ionic components</h3><p>Composition enables us to use and reuse components. And these components can either be created by you or by others.</p><p>I mean, if you are like us that <a href="https://ionicthemes.com/templates">builds multiple Ionic apps,</a> you’ve probably gone through the sign-up page a couple of times, so, there’s no point in coding it each time.</p><p>You can focus on building it once and then reuse it as often as necessary and just customize the styles for each application.</p><p>I loved this quote from Eric Elliot, <strong>“A software developer who doesn’t understand composition is like a home builder who doesn’t know about bolts or nails.”</strong></p><h3>Save time, don’t repeat yourself</h3><p>When building an app there are many repetitive tasks that you can avoid. Like the example from the sign-up page we saw before.</p><p>Thanks to the composition of multiple elements, we can save a lot of time. This frees us from having to be experts regarding all the aspects of developing an app.</p><blockquote><em>You don’t have to be an expert in every aspect of creating an app. We just need to be good assemblers to combine all the building blocks that will result in our unique application.</em></blockquote><p>What is more, the beauty of open source is collaboration. Being able to share your knowledge and extend the creation of other developers is something we have to be very grateful for. Personally, I learn a lot from seeing other people’s code.</p><p>From my point of view, collaboration and community are also a big part of composition, because you can use an element built by someone else and use it as it is, or you can use it as a suitable starter to build something else.</p><p>Okay, enough talking about all this theory, let’s see how to build any UI with Ionic.</p><h3>Customizing and composing Ionic Elements</h3><p>One of the features I love the most about Ionic Framework is the immense amount of <a href="https://ionicframework.com/docs/components">components</a> that are ready to use, customize and extend.</p><p>These elements are also beautifully crafted as <a href="https://ionicthemes.com/tutorials/tag/web-components">Web Components</a> enabling encapsulation and allowing them to be portable and easily reused.</p><p>In addition to this, each of these Ionic components consists of one or more custom elements.</p><p>For example, a card can be composed of images, labels and buttons. And this happens with many other Ionic UI components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/333/0*jaD1EKkKkMndUsLR.png" /></figure><p>Regarding web components, I won’t go into details here but, if you aren’t familiar with them or if you are interested in learning more, we have an extensive article about <a href="https://ionicthemes.com/tutorials/ionic-4-tutorial-mastering-web-components-in-ionic-4">Web Components in Ionic Apps</a>.</p><p>For the purpose of this post, let’s divide elements in two categories:</p><ul><li>UI Elements</li><li>Functionalities</li></ul><h3>Ionic Components customization strategies</h3><p>There are different strategies we can use to customize and enhance Ionic components. Some of them are pretty straight forward, others require adding more code (HTML and CSS).</p><p>In the following sections I will explain how to progressively customize an <a href="https://ionicframework.com/docs/api/checkbox">Ion Checkbox</a> using four different strategies.</p><p>Why a checkbox? Because I want to show you how we can achieve beautiful UIs through composition even with a dull and plain checkbox.</p><p>In the following image you can see a basic and raw Ion-Checkbox component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/0*jW5v3a9eRktdGNzH.png" /></figure><p>I broke the customization down into four levels of effort and complexity and I built some <a href="https://ioniconf-2021.web.app/tabs/tab1">code examples</a> for each of these scenarios, so you can better understand what I’m trying to explain here. <a href="https://ionicthemes.com/tutorials/how-to-build-any-ui-with-ionic">You can download all the source code of this example app.</a></p><ol><li><a href="https://ionicthemes.com/tutorials/how-to-build-any-ui-with-ionic#css-variables-and-shadow-parts">Ionic CSS variables and Shadow Parts</a></li><li><a href="https://ionicthemes.com/tutorials/how-to-build-any-ui-with-ionic#html-and-css">Adding HTML and CSS</a></li><li><a href="https://ionicthemes.com/tutorials/how-to-build-any-ui-with-ionic#customization-based-on-the-component-api">Customization based on component events</a></li><li><a href="https://ionicthemes.com/tutorials/how-to-build-any-ui-with-ionic#adding-functionalities">Customization based on functionalities</a></li></ol><blockquote><strong>If you want to go over each of these customization strategies please refer to the </strong><a href="https://ionicthemes.com/tutorials/how-to-build-any-ui-with-ionic"><strong>original post</strong></a><strong>.</strong></blockquote><p>Hope you enjoyed this Ionic Customization post. Thank you very much for reading and if you have any questions or feedback please leave a comment below.</p><p><em>Originally published at </em><a href="https://ionicthemes.com/tutorials/how-to-build-any-ui-with-ionic"><em>https://ionicthemes.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d932a19b9ca9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learn-ionic-framework/customizing-ionic-components-how-to-build-any-ui-with-ionic-d932a19b9ca9">Customizing Ionic Components — How to build any UI with Ionic</a> was originally published in <a href="https://medium.com/learn-ionic-framework">Learn Ionic Framework</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Create a Show / Hide Password Component in Ionic & Angular]]></title>
            <link>https://medium.com/learn-ionic-framework/create-a-show-hide-password-component-in-ionic-angular-a3960094726a?source=rss-f05e27e8a50e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3960094726a</guid>
            <category><![CDATA[ionic]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[angularjs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[ionic-framework]]></category>
            <dc:creator><![CDATA[Dayana Jabif]]></dc:creator>
            <pubDate>Mon, 19 Oct 2020 23:33:58 GMT</pubDate>
            <atom:updated>2021-02-21T18:09:33.023Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Add this show/hide password component to your Ionic Angular App in 3 simple steps.</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FQjJ5E4nP2-s%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQjJ5E4nP2-s&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FQjJ5E4nP2-s%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4b418b77f3b02a2237bbb4fb5bfeeb06/href">https://medium.com/media/4b418b77f3b02a2237bbb4fb5bfeeb06/href</a></iframe><h3>Step 1 — Create the Angular component</h3><ul><li>Create an Angular Component with a ContentChild IonInput.</li><li>Add a toggle method that will be triggered when clicking the eye icon.</li><li>This method will switch between showing the password text and the dots.</li><li>Define a showPassword boolean var.</li></ul><pre>import { Component, ContentChild } from &#39;@angular/core&#39;;<br>import { IonInput } from &#39;@ionic/angular&#39;;</pre><pre>@Component({<br>  selector: &#39;app-show-hide-password&#39;,<br>  templateUrl: &#39;./show-hide-password.component.html&#39;,<br>  styleUrls: [&#39;./show-hide-password.component.scss&#39;]<br>})<br>export class ShowHidePasswordComponent {<br>  showPassword = false;</pre><pre>@ContentChild(IonInput) input: IonInput;</pre><pre>constructor() {}</pre><pre>toggleShow() {<br>    this.showPassword = !this.showPassword;<br>    this.input.type = this.showPassword ? &#39;text&#39; : &#39;password&#39;;<br>  }<br>}</pre><h3>Step 2 — Add the html markup for the component</h3><ul><li>Create a simple anchor with our toggle method binded to the click event.</li><li>Change the icon between eye open and eye closed depending on the showPassword var.</li></ul><pre>&lt;ng-content&gt;&lt;/ng-content&gt;<br>&lt;a class=&quot;type-toggle&quot; (click)=&quot;toggleShow()&quot;&gt;<br>   &lt;ion-icon class=&quot;show-option&quot; [hidden]=&quot;showPassword&quot; name=&quot;eye-off-outline&quot;&gt;&lt;/ion-icon&gt;<br>   &lt;ion-icon class=&quot;hide-option&quot; [hidden]=&quot;!showPassword&quot; name=&quot;eye-outline&quot;&gt;&lt;/ion-icon&gt;<br>&lt;/a&gt;</pre><p>This is my <strong>show-hide-password.component.scss, </strong>to add some styles.</p><pre>:host {<br>  display: flex;<br>  width: 100%;<br>  align-items: center;</pre><pre>.type-toggle {<br>    padding-inline-start: 0.5rem;</pre><pre>.show-option,<br>    .hide-option {<br>      font-size: 1.2rem;<br>      display: block;</pre><pre>// In case you want to use text instead of icons<br>      &amp;:not(ion-icon) {<br>        text-transform: uppercase;<br>        font-size: 1rem;<br>      }<br>    }<br>  }<br>}</pre><h3>Step 3 — Use the Show / Hide password component</h3><p>Just use the component with a <em>&lt;ion-input&gt;</em> as a content child.</p><pre>&lt;ion-item&gt;<br>  &lt;app-show-hide-password&gt;<br>      &lt;ion-input type=&quot;password&quot; placeholder=&quot;Password&quot; formControlName=&quot;password&quot;&gt;&lt;/ion-input&gt;<br>  &lt;/app-show-hide-password&gt;<br>&lt;/ion-item&gt;</pre><p>That’s all.</p><p>That was easy right?</p><p>Go ahead and add it to your Ionic Framework App and show me the result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/1*udHYIJSqkc60LHBPcNI00Q.png" /><figcaption>show hide password icon</figcaption></figure><p><a href="https://ionicthemes.com/tutorials">Learn more about Ionic Framework!</a></p><p>Need help with the styling? Let me know in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3960094726a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learn-ionic-framework/create-a-show-hide-password-component-in-ionic-angular-a3960094726a">Create a Show / Hide Password Component in Ionic &amp; Angular</a> was originally published in <a href="https://medium.com/learn-ionic-framework">Learn Ionic Framework</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Angular Charts]]></title>
            <link>https://medium.com/learn-angular/angular-charts-879c7bbd710?source=rss-f05e27e8a50e------2</link>
            <guid isPermaLink="false">https://medium.com/p/879c7bbd710</guid>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[charts]]></category>
            <category><![CDATA[visualization]]></category>
            <dc:creator><![CDATA[Dayana Jabif]]></dc:creator>
            <pubDate>Fri, 19 Jun 2020 12:28:33 GMT</pubDate>
            <atom:updated>2020-10-05T14:40:19.010Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to choose your angular charting library?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YtbPde61XyKVfytP.png" /><figcaption>angular charts</figcaption></figure><blockquote>We are living in a visual era, so it may not surprise you to see different types of visualizations widgets such as charts, graphs, tables and many others in almost every website and mobile app you visit. The main purpose of visualizations is to help displaying data in a visual, lively, sexy and summarized way.</blockquote><p>In <a href="https://angular-templates.io/product/fully-angular-admin-template">Fully — Angular Admin Template</a>, we designed and developed many beautiful visualization widgets that developers can reuse when building they Angular apps. In this particular post, we will discuss about charts and graphs in Angular projects.</p><p>A chart is a graphical representation of data, the data is represented by symbols, such as slices in a pie chart, bars in a bar chart or lines in a line chart.</p><p>As developers, we can take advantage of charts in situations where a simple table won’t adequately demonstrate important relationships or patterns between data points. The main goal of a chart is to display data and invite the user for a further exploration of a topic.</p><h3>How to choose your angular charting library?</h3><p>f you perform a quick search in google, you will find many different angular charting libraries. So, how to choose which one to use?</p><p>The hard part is taking into consideration the many aspects that will lead you to choose the right library for the use case.<br>It’s tempting to go straightforward, pick the library that has the most stars on GitHub, install it with npm and voilà.<br>Don&#39;t want to be a party pooper, but there&#39;s much more in between.</p><h3>Things you need to consider:</h3><h4><strong>SVG or Canvas?</strong></h4><p>You first need to understand the nature of the use case you have in mind to choose the underlying technology.<br>Are you going to use SVG or Canvas based charts? Each has its pros and cons, more on that later.</p><h4><strong>Angular friendly?</strong></h4><p>Secondly, you should search for up to date libraries that work seamlessly with Angular (latest Angular, not AngularJS or Angular 2).</p><h4><strong>What about the license?</strong></h4><p>Most libraries are free and open source, but others don’t. Depending on your project and budget, the pool of options available. For example, there are some great libraries like <a href="https://shop.highsoft.com/highcharts">Highcharts</a> and <a href="https://www.zingchart.com/pricing">Zingchart</a>, but you have to buy a license in order to use them.</p><h4><strong>Up to date</strong></h4><p>Don’t forget to look at the library’s GitHub activity (number of stars, date of last commit, future plans, etc). This isn’t decisive but it’s good to start with a library that show signs of being well maintained with planned enhancements and new features down the road.</p><h4><strong>Get to know the limitations</strong></h4><p>Not all charting libraries provide the full set of visualizations such as 2D, 3D, map, scientific, financial, and statistical charting. Also, some provide great customization, others don’t.<br>Depending on how elaborate is your use case you should target for libraries that enable advanced customization or more simple ones that provide less configuration options.<br>Are you planning on supporting legacy browsers? That may be a bummer for some libraries.</p><h4><strong>Start building the visualization</strong></h4><p>Are you going to build the visualization from the ground up or start from the closest example you find in the charting library documentation page?<br>Either way you will need to deep dive into the library’s documentation and crunch a bit.<br>This is when you will fall in love or hate the documentation page of each charting library under consideration.</p><h4><strong>Customization</strong></h4><p>Again, depending on the complexity of your chart design, and the library you choose whether you will be able to implement your visualization easily or going to spend quite some hours figuring out the nasty little quirks.<br>Do you have in mind any custom interaction? Hovers, clicks, loaders or maybe merge the chart with some html to enhance the overall visualization.</p><h4><strong>Data integration</strong></h4><p>Once you have a UI and UX you are comfortable with, you need to take care of the data source, fetching technique and integration with your Angular services.<br>Are you also considering adding filters to your data source? That’s a whole different story and it may as well be time consuming.</p><h4><strong>Clean code</strong></h4><p>Every developer prefers to work with understandable, extendable, clean and tidy source code. You should spend some time ensuring future collaborators can extend your work seamlessly.</p><h4><strong>Final tweaks</strong></h4><p>Did your ensure your visualization is responsive?</p><blockquote>As you can see, there’s a ton more going on after running npm install. On average, it took us around 20 hours of skilled designers and developers to build each visualization for our latest <a href="https://angular-templates.io/product/fully-angular-admin-template">Angular Dashboards Template</a>.</blockquote><p>Considering it includes 25 visualizations, that’s around $30.000 worth of skilled developers just for the visualizations.</p><p>When building <a href="https://angular-templates.io/product/fully-angular-admin-template">Fully — Angular Admin Dashboard Template</a>, we followed the process described above, tried many charting libraries, built some proof of concepts, and finally implemented not just one but a set of Angular chart libraries because we acknowledge there are users with a wide range of requirements.</p><p>The set of charting libraries we packed into Fully Angular Template feature both SVG and Canvas based options to satisfy different scenarios, detailed UI/UX customizations, real time or large amount of data, responsiveness, etc.<br>Not to mention we carefully ensured each library works well with our Angular code base.</p><p>That’s why we felt motivated to create this <a href="https://angular-templates.io/tutorials/about/angular-charts">Angular Charts Guide</a> to help other developers like you deciding how to add charts to your angular applications.</p><h3>The right tool for the job</h3><p>At a lower level, there are basically two graphic primitives that charting libraries are built upon:</p><ul><li><strong>Bitmap</strong> graphics that rely on pixels to represent images</li><li><strong>Vector</strong> graphics that rely on geometric shapes to represent images</li></ul><p>Both underlying graphic primitives have its abstraction technology. Canvas relies on bitmaps and SVG on vectors.</p><h4>Canvas Charts</h4><p>The Canvas specification defines objects, methods, and properties to draw and manipulate graphics using a &lt;canvas/&gt; HTML element.</p><p>Canvas uses a &quot;fire and forget&quot; model, there is no DOM that can be referenced once an element has been drawn. This is a drawback in terms of interactivity.</p><h4>SVG Charts</h4><p>On the other hand, the SVG specification defines the features and syntax for a modularized language for describing two-dimensional vector graphics using XML.</p><p>SVG typically creates a DOM node per point. This is great for flexibility on UI/UX customization and interactivity because programming languages can connect to the page and easily make changes to the structure, style and content of the visualization.</p><p>Initially, having every element available in the DOM seems beneficial, however the browser is constantly re-computing every element which leads to a slowdown impacting performance. Since Canvas doesn&#39;t have the memory of every element that SVG has, it&#39;s quick and easy when we need to draw thousands of data points.</p><p><strong>Note:</strong> Most charting libraries are either based on a Canvas or SVG rendering engine. That’s why, when choosing between them, you will reduce the charting libraries options considerably.</p><p><strong>We come up with a flow chart to help you analyze the critical aspects of your use case to start crossing out charting library options.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yo6VAss0ChynTlTw3vpwNA.png" /><figcaption>Which Chart library should you use?</figcaption></figure><h3>Best Angular Chart Libraries</h3><p>We tried different charting libraries and stuck with the ones that meet the requirements listed above.</p><p>We choose different libraries, based on both SVG and Canvas, to provide a wide range of options for the different use cases that may arise when building an Angular dashboard.</p><p>Without further ado, here are our top three picks in order of preference:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D_Gx_dVoCi8vk-Tq8GCKmA.png" /><figcaption>angular charts libraries</figcaption></figure><p>They all have similar names, (and that’s confusing, at least for me), but they are all based on different underlying charting libraries and provide distinct opinionated Angular wrapper directives.</p><p>In terms of popularity we need to assess the different charting libraries they are based on.</p><p>Both <strong>Echarts</strong> and <strong>Charts.js</strong> are based on Canvas to draw the visualizations. They have healthy GitHub repositories and differ a bit by the amount of built-in chart types available and the customization options they provide.<br>We found that <strong>Echarts</strong> provides more chart types with deeper customization options than <strong>Charts.js</strong>. Though, they are both great alternatives, that’s why we included chart examples of both of them.</p><p>On the other hand, <strong>D3.js</strong> is mainly based on SVG, thus the building blocks and customization is closely related to SVG nodes manipulation. <strong>D3.js</strong> has probably the widest set of chart types available among the three options discussed here, but the customization is notoriously harder.<br>We believe that’s a no-go for many users with simple use cases and that’s why we didn’t place it in the first spot. We really felt the need to include an advanced SVG based option for advanced use cases, and found <strong>ngx-charts</strong> the best alternative in this category.</p><p><strong>Worth to mention:</strong></p><ul><li><strong>HighCharts</strong> and <strong>Zingchart</strong> are great alternatives, but unfortunately they are not open source. You can use them for free for non commercial purposes. Otherwise you need to buy a license. Again, this is a no-go for many of our users, that’s why we didn’t proceed evaluating them.</li><li><strong>ng2-nvd3</strong> (another Angular wrapper for <strong>D3.js</strong>) was once very popular, but its GitHub repository has been stuck for quite some time. <strong>ngx-charts</strong> was a clear winner over this alternative.</li><li>I’m very curious about trying out <strong>billboard.js</strong> as another option that’s based on <strong>D3.js</strong>. For the moment, I haven’t found the time nor a proper Angular wrapper to continue assessing it.</li></ul><blockquote><a href="https://angular-templates.io/tutorials/about/angular-charts#best-angular-chart-libraries">Check the complete tutorial</a> to see the Pros and Cons of each of these charting libraries as well as some code examples.</blockquote><h3>Angular Charts Examples</h3><p>Before wrapping up this charting angular guide I would like to show you some nice examples you can build with the above mentioned libraries.</p><h4>Sparklines in Angular apps:</h4><p>This super cool sparklines or minicharts are very useful to summarize a trend.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MlW-i7qh7pd-t2m5.png" /></figure><h4>Line charts in Angular:</h4><p>Line charts are useful to show changes over periods of time. Line graphs can also be used to compare changes over the same period of time for more than one group of data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3GHCZDv--hkTvqv7.png" /></figure><h4>Pie charts in Angular:</h4><p>Pie charts are mainly used for comparing the proportions of different categories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/617/0*5xf7qIj8fP-vcdyv.png" /></figure><h4>Doughnut charts in Angular:</h4><p>The Doughnut Chart is similar to the pie chart. It’s also used to express a “part-to-whole” relationship where all pieces together represent 100%. Some visualization experts say that this type of charts are more efficient than the pie charts because they are easier to read.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*Z3d5BiIh4_ebP7jK.png" /></figure><h4>Bar Charts in Angular:</h4><p>The purpose of a Bar chart is to compare different sets of data through the height of a bar. For this example I included a video so you can also see the chart’s animations.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FpLMZe_kM7Kg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DpLMZe_kM7Kg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FpLMZe_kM7Kg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7f403d603a2c66e14cf54e9375f55e49/href">https://medium.com/media/7f403d603a2c66e14cf54e9375f55e49/href</a></iframe><h3>Angular Charts Summary</h3><p>When it comes to implement visualizations and charts in Angular there are plenty of considerations before you start writing the first line of code.</p><p>We carefully reviewed many of the charting libraries available and shared our analysis on the top three Angular chart libraries.</p><p>In this post we exposed all the gotchas for you to make an informed decision and avoid underestimating the effort of building visualization use cases in Angular. Depending on the complexity and detail of your use case, you can easily spend +40 hours worth of experienced developers on the task. <a href="https://angular-templates.io/tutorials/about/angular-charts"><strong>Read the complete post</strong></a><strong>.</strong></p><blockquote>For all of you out there with a tight budget or schedule, we packed plenty of examples using the top three Angular charting libraries in our latest <a href="https://angular-templates.io/product/fully-angular-admin-template">Fully — Angular Admin Template</a>. <strong>By including different libraries we ensure covering many different use cases.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*W6kqVKXsCZwYkTrR.jpg" /><figcaption>Angular Admin Template <a href="https://angular-templates.io/product/fully-angular-admin-template">https://angular-templates.io/product/fully-angular-admin-template</a></figcaption></figure><p>Any other library you think we should consider? Leave me a message!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=879c7bbd710" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learn-angular/angular-charts-879c7bbd710">Angular Charts</a> was originally published in <a href="https://medium.com/learn-angular">Learn Angular</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s new in Ionic 5? — Free example starter to jump start your ionic app development!]]></title>
            <link>https://medium.com/learn-ionic-framework/whats-new-in-ionic-5-free-example-starter-to-jump-start-your-ionic-app-development-aeae53fdc28e?source=rss-f05e27e8a50e------2</link>
            <guid isPermaLink="false">https://medium.com/p/aeae53fdc28e</guid>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[ionic-framework]]></category>
            <category><![CDATA[ionic]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Dayana Jabif]]></dc:creator>
            <pubDate>Fri, 12 Jun 2020 19:30:48 GMT</pubDate>
            <atom:updated>2020-06-12T19:30:48.063Z</atom:updated>
            <content:encoded><![CDATA[<h3>What’s new in Ionic 5 —Free example app</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5TtBnHpopNTkSvLqHZ8s-A.jpeg" /><figcaption>ionic 5 introduction tutorial</figcaption></figure><p>Around this time last year, we were writing about the new <a href="https://ionicthemes.com/tutorials/about/ionic-4-vs-ionic-3">Ionic Framework version 4</a>. It was a great deal compared to its predecessor, Ionic 3.</p><p>Luckily, the team at Ionic is very committed to keep pursuing their goal of <strong>making app development easier</strong> and recently announced the latest and much awaited <strong>Ionic 5 release</strong>.</p><p>It’s clear to me, as an insider, that Ionic is one of the top frameworks regarding the peace of innovation they bring to the game on each iteration (now supporting both Angular, React, and Vue!). They are fearless and confident in the direction they envision for the future of mobile and web development.</p><p>In this post we want to explain how to take advantage of the new benefits from Ionic 5. We will describe the main changes and show you how to migrate your applications from Ionic 4 to Ionic 5.</p><blockquote>For this post we created an Ionic 5 free demo app. It’s a CRUD app with some of the new Ionic 5 features such as swipeable modals, collapsible headers, segments, animations, as well as, lists, reactive forms, and navigation examples. <strong>Download it for free in </strong><a href="https://ionicthemes.com/tutorials/about/ionic5-tutorial-migration-and-starter"><strong>IonicThemes</strong></a><strong>.</strong></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FgENv7OYepHk%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DgENv7OYepHk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FgENv7OYepHk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1bcffcb67ad5d956f528d14be613dc34/href">https://medium.com/media/1bcffcb67ad5d956f528d14be613dc34/href</a></iframe><h3>What’s new in Ionic 5?</h3><p>The highlights of this new release are mainly centered around design and UI/UX, featuring a brand new API to create outstanding animations, new and improved Ionicons icon library, components featuring iOS 13 design spec and also some useful customization improvements regarding component styling.</p><h3>Animations API</h3><p>The new <a href="https://ionicframework.com/docs/utilities/animations">Ionic Animations API</a>, presents a shift from Javascript-driven animation libraries. This legacy approach followed by many well known animation libraries is problematic in many ways. Mostly because the browser is responsible for both rendering your animation and executing your animation event loop code at every frame in the same thread as the rest of your app’s code. This traduces on performance loss as the browser is forced to waste CPU time by executing your code on every frame.</p><p>Harnessing the Web Animations API, the new Ionic Animations API can offload to the browser all of the work required to run your animations. This way, the browser will be able to schedule and make optimizations so your animations will run smoothly. This new, open source animation utility is not only framework agnostic (yes, that means you can use it in Angular, React, Vue or just vanilla Javascript), but it also shines in the <a href="https://blog.ionicframework.com/wp-content/uploads/2020/01/animation-benchmark-results.pdf">benchmarks performed by the Ionic team</a>.</p><p>To be honest, this looked so promising that I had to give it a try. I included a custom animation to the Ionic 5 starter included in this post to showcase the new feature. The results are amazing, I would highly recommend giving the Ionic Animation utility a try.</p><p>We created a very simple animation when pressing a heart icon that can be useful when giving a fav or a like to something.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*Zi59rQ--NfubP1tp.gif" /></figure><h3>Improved components and UI/UX</h3><p>Besides reworking many of the components ( <a href="https://github.com/ionic-team/ionic/blob/master/BREAKING.md#segment">Segment</a>, <a href="https://github.com/ionic-team/ionic/blob/master/BREAKING.md#list-header">List Header</a>, among many more) to match the latest iOS 13 design spec, the new release includes changes that make customizing components easier.</p><p><a href="https://ionicthemes.com/tutorials/about/ionic-4-tutorial-mastering-web-components-in-ionic-4">Since Web Components and Shadow DOM were introduced in Ionic 4</a>, customizing components has been one of the most arduous things to achieve. In part because of the encapsulation provided by Shadow DOM and part because of the lack of CSS custom variables available to tweak Shadow components.</p><p>In addition, Ionic 5 also shipped a new and vibrant color palette style guide including a set of colors specially tailored for <a href="https://ionicframework.com/docs/theming/dark-mode">dark mode support</a>.</p><h3>Ionicons 5</h3><p>One of the highlights of this new release is the new version of Ionicons, the amazing web component icons library. As well as its predecessor, Ionicons 5 is distributed as a set of SVG icons instead of a font icon, for much better performance and less complexity.</p><p>With over 1200 icons, Ionicons 5 brings a massive number of new icons. Additionally, each icon now comes in three distinct weight variants outline, fill, and sharp. With this new approach, the set of icons position itself as a system inspired by the best of both (Material Design and iOS) platforms.</p><p>I have to say, though, that if you are migrating from Ionicons 4, there are some minor <a href="https://github.com/ionic-team/ionicons/blob/master/CHANGELOG.md#breaking-changes">breaking changes</a>.</p><h3>Compatibility with other Frameworks</h3><p>As you may know, apart from the original Angular official support (@ionic/angular), Ionic released an official react integration (@ionic/react) and they are working on a Vue integration as well (@ionic/vue, still in beta. <a href="https://twitter.com/Ionicframework/status/1229431909815640065">They are waiting</a> till Vue 3 stabilizes).</p><p>This multi-framework approach is possible thanks to the web components core implementation of the framework (@ionic/core). This means you can target almost any platform (desktop, mobile, browser, native) using the same toolset.</p><p>Also, I want to mention <a href="https://ionicthemes.com/tutorials/about/native-cross-platform-web-apps-with-ionic-capacitor">Ionic Capacitor</a>, a cross-platform app runtime that makes it easy to build web apps that run natively on iOS, Android, Electron, and the web. Lately, we have been using it on every Ionic project and we are very happy with it. If you are new to the Ionic ecosystem learn more about the <a href="https://ionicthemes.com/tutorials/about/native-cross-platform-web-apps-with-ionic-capacitor#capacitor-vs-cordova">main differences between Capacitor and Cordova</a>. It’s a really great contribution from the Ionic Team.</p><h3>Performance</h3><p>For all of you Angular developers out there, Ionic 5 brings great news regarding performance and optimizations to your Ionic Angular apps. The new <a href="https://ionicframework.com/blog/angular-9-0-0-and-ivy-improvements/">Angular renderer (Ivy)</a> enables apps to only require pieces of the renderer that they actually need, instead of the whole thing. This translates into smaller output files and consequently better load performance.</p><h3>Angular 9?</h3><p>Angular 9 and Ivy are supported in Ionic 5, however, they are optional. In fact, if you create a new Ionic app right now using the CLI, it will use Angular 8. If you want to upgrade to Angular 9 make sure to follow <a href="https://update.angular.io/">this guide</a>.</p><h3>Developer Experience</h3><p>Starter templates are a great way to kickstart your project. The bare bones, basic starters that come with Ionic have been redesigned to match the new Ionic 5 UI.</p><blockquote><em>The default starters are very limited in the functionality they showcase, that’s why we built a more in-depth starter for this post.</em></blockquote><p>You can download the free code of this Ionic 5 starter app in <a href="https://ionicthemes.com/tutorials/about/ionic5-tutorial-migration-and-starter">IonicThemes website</a>.</p><p><strong>If you are more serious about your Ionic endeavor, or if you want to start creating your Ionic Framework app but don’t know how to start, I suggest you try our most advanced ionic starter template: </strong><a href="https://ionicthemes.com/product/ionic5-full-starter-app"><strong>Ionic 5 Full Starter App</strong></a><strong>.</strong></p><p>Use it to jump start your Ionic app development and save hundreds of hours of design and development. With more than 100 carefully designed views and components, it will help you grasp best practices and the new concepts of Ionic 5 development.</p><p><a href="https://ionicthemes.com/product/ionic5-full-starter-app"><strong>Try it both as a native app or as a full PWA on your mobile browser!</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U5YzHQFXTQXjlzc4LK75AA.png" /><figcaption>ionic template</figcaption></figure><h3>How to migrate from Ionic 4 to Ionic 5?</h3><p>As usual, we get our hands on before writing any review or tutorial. In our case we choose to migrate our most complete starter template before writing this review. Considering <a href="https://ionicthemes.com/product/ionic5-full-starter-app">Ionic Full Starter App</a> a mid size project that touches almost every corner of the Ionic framework, its components and features, <strong>we can confidently say that migrating from Ionic 4 to Ionic 5 is a breeze.</strong></p><p>I’m not going to lie to you, there are some breaking changes, but the Ionic Team did a great job documenting everything with lots of details and examples. In the following section I’m going to mention these breaking changes and point you in the right direction to resolve them.</p><blockquote><a href="https://ionicthemes.com/tutorials/about/ionic5-tutorial-migration-and-starter#how-to-migrate-from-ionic4-to-ionic5">Get the complete migration guide from ionic 4 to ionic 5.</a></blockquote><h3>Final thoughts on Ionic Framework 5</h3><p>I hope this article helped you get to know the highlights of the new Ionic 5 release, and above all to calm fears about the migration process. As mentioned above, migrating from Ionic 4 to Ionic 5 does not mean rewriting your application, and can be easily achieved with minor effort.</p><p>If you want to learn more about Ionic Framework, at IonicThemes we have lots of <a href="https://ionicthemes.com/tutorials/tag/ionic-4">free ionic 5 tutorials</a> with practical examples so you can learn how to create the best mobile apps using Ionic Framework.</p><blockquote><em>Remember that if you need help starting your Ionic 5 application we have built a </em><a href="https://ionicthemes.com/product/ionic5-full-starter-app"><em>super complete starter app</em></a><em> that will help you in all the steps of developing an Ionic and Angular application. You can </em><a href="https://ionicthemes.com/product/ionic5-full-starter-app/live-preview"><em>try the demo</em></a><em> to see all the beautiful pages and components we built using Ionic Framework 5.</em></blockquote><p><strong>Need help with Ionic 5? Leave me a comment.</strong></p><p><em>Originally published at </em><a href="https://ionicthemes.com/tutorials/about/ionic5-tutorial-migration-and-starter"><em>https://ionicthemes.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aeae53fdc28e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learn-ionic-framework/whats-new-in-ionic-5-free-example-starter-to-jump-start-your-ionic-app-development-aeae53fdc28e">What’s new in Ionic 5? — Free example starter to jump start your ionic app development!</a> was originally published in <a href="https://medium.com/learn-ionic-framework">Learn Ionic Framework</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>