<?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 Nikki Eke on Medium]]></title>
        <description><![CDATA[Stories by Nikki Eke on Medium]]></description>
        <link>https://medium.com/@nikkieke001?source=rss-b7ee6504128f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MkQhZFm9dryA-32KXAAO3g.jpeg</url>
            <title>Stories by Nikki Eke on Medium</title>
            <link>https://medium.com/@nikkieke001?source=rss-b7ee6504128f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:07:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nikkieke001/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[What No One Tells You About Building with Apple’s Screen Time API]]></title>
            <link>https://medium.com/@nikkieke001/what-no-one-tells-you-about-building-with-apples-screen-time-api-e061d14d1f66?source=rss-b7ee6504128f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e061d14d1f66</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[mdm]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[screen-time-control]]></category>
            <dc:creator><![CDATA[Nikki Eke]]></dc:creator>
            <pubDate>Tue, 02 Jun 2026 09:57:24 GMT</pubDate>
            <atom:updated>2026-06-02T09:57:24.527Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sCcWYlt6JAgkznYYyLjJBA.png" /></figure><p>User privacy is a foundational priority in iOS. While building for device usage monitoring and control with Apple Screen Time API I quickly realized that this API was never designed to give third-party developers the same level of control Apple’s own native Screen Time has internally.</p><p>This decision shapes every part of the developer experience. From opaque tokens that prevent you from identifying your user’s apps to heavily restricted extensions with no network access. Building with this API exposes you to the different creative ways Apple keeps developers locked out in a bid to protect users privacy.</p><p>This made it very challenging for developers like me that tried to build really ambitious features; because to build certain control features you do need a level of access. So I had a lot of experiences like: starting out with a plan and changing it midway due to platform restrictions, spending a lot of time going in circles due to undocumented limitations, discovering that some features were easy to build in Android but are simply impossible on iOS.</p><p>In this article I will be sharing my experience building with this API, observations made, lessons learnt, some workarounds I used and what is currently obtainable with Screen Time API at the time of writing this. If you are planning to build with this API, already building with it or simply curious, then you should read this.</p><h3>What is Apple’s Screen Time API and What Does It Do?</h3><p>Apple’s Screen Time API is a set of tools that allows developers to create third-party apps for parental controls, digital wellness, or productivity. It enables apps to monitor device usage, track time spent on specific apps or websites, and enforce usage restrictions.</p><p>This API is very recent as it was only introduced in WWDC 2021. Prior to this, many developers built screen time features using MDM and/or VPN. When Apple discovered that MDM gave developers unilateral access to user information — as you can expect they removed most of those apps from the store and then introduced this API as an alternative. The aim was to protect user data whilst giving developers the platform they need to build their own screen time and device control features.</p><p>The Apple Screen Time API comprises of three distinct frameworks that allow developers build features that implement screen time and device usage control features natively on a device.</p><p>These are the three frameworks in the Apple Screen Time API:</p><h3>FamilyControls (The Gateway)</h3><p>Family Controls is the gateway, as it allows the user authorize access to Screen Time for your app.</p><p>The Family Controls framework leverages on Family sharing so that access to screen time can only be authorized by the guardian of a child in a family sharing group or the owner of the device. Once it has been authorized by a guardian, the child will be unable to delete your app without guardian approval.</p><p>Family Controls also allows users choose which apps or websites they want to control through your app. It does this through the Family Activity Picker. When the user makes a selection, it returns an opaque token that only the device can identify as the app or website selected. This means your app would never know which apps were selected by the user. This information remains strictly with Apple and the user.</p><p>Before you can use any of the APIs exposed for managing screen time you need to enable the Family Controls entitlement for both development and production (Testflight &amp; Appstore Release). With the development entitlement you can complete your app development but to release the app you need the production entitlement.</p><p>This entitlement has to be specially requested for, through the Account holder of your Apple developer account. It has to requested for the main app and every single extension you’ll need for development. Review time takes any time from a few days to over three weeks and in bad cases a few months. Only when it’s approved can you then release for production, so it is wise to request for the production entitlement as early as possible. If you attempt to release the apps without approval, the APIs simply wouldn’t work.</p><h3>ManagedSettings (The Enforcer)</h3><p>ManagedSettings is the enforcer. It enforces all the restriction and control features you have set up, like: blocking apps, shielding apps, preventing password change, filtering web traffic and a host of others.</p><p>Through the ManagedSettingsUI you can also style how the blocked content visually appears to your users, like the shield screen UI and the custom messages shown to the user.</p><p>However, this customization is limited. On the shield you can only customize the text and the background color of the shield. You can’t add brand assets on the shield or change the background color to a gradient color. This was probably an intentional restriction to ensure that users are able to recognize the shield every time it pops up.</p><h3>DeviceActivity (The Scheduler &amp; Monitor)</h3><p>DeviceActivity allows your app to schedule the time that the restrictions you have set up becomes active on your user’s device. It also monitors user’s device usage and allows you to trigger restrictions when certain thresholds are reached.</p><p>DeviceActivity also allows you to generate custom device usage reports using SwiftUI. The usage data is accessed through an extension where developers can choose what usage data is displayed and how it is displayed.</p><p>But, if you attempt to extract the usage data to your main app, it returns absolutely nothing. The usage data can only be accessed in the extension and visually displayed using SwiftUI. Apple never shows the developer the usage data of the user.</p><h3>How the Three Frameworks Work Together</h3><p>Simply, FamilyControls asks the user for permission and what to control; ManagedSettings sets up the actual restriction; and DeviceActivity controls when that restriction is turned on and off.</p><h3>Apple’s Screen Time Architecture</h3><p>Apple ‘s Screen Time Architecture is set up to ensure that a larger percentage of control remains with the user and the OS. Your app may set the limitations but every restriction must be authorized by the user (or guardian of the user). Those rules are only then enforced through the ManagedSettings by the OS, not your app. Because of this, even if your app was force quit or the device restarted. The restrictions you have put in place still remains.</p><p>To implement Screen Time, Apple provides different extensions which allow them to handle sensitive processes without exposing user data. These extensions are isolated, heavily sandboxed, have little to no internet access, and have strict execution time. They exists separately, functioning outside your app. The only way they share data with your app or each other is via App Groups. All your extensions need to share the same App Group capability to effectively share data. When issues occur, extensions can be difficult to debug and it can be difficult to track bugs.</p><p>The architecture is structured in such a way that developers can participate in the Screen Time experience but the OS remains fully in control. The main app and extensions — working together but fully isolated from each other.</p><h3>My Research, Expectation and Reality</h3><h3>The Research</h3><p>As someone with no prior experience with the Screen Time API, I spent the first few weeks studying. I read up articles, skimmed through Apple developer forums, used AI to gather data and googled a lot. At last I felt satisfied having confirmed that using Screen Time API would help me build some of the features I planned to. It is also Apple’s preferred option.</p><p>Although, I discovered that there were a few other features that were simply impossible on iOS. For instance, Apple doesn’t allow developers access the names and/or bundle ids of the user’s installed apps. This was disappointing because it was a major product requirement and was already implemented on Android.</p><p>So I wrapped up my research knowing that a few features will be put on hold and that certain device control features could only be possible on supervised devices. Supervised devices are devices that have been configured to grant administrators deeper control over device behavior. The issue is, supervised devices are not ideal for commercial use.</p><h3>The Expectation</h3><p>From my research, I expected certain features to be straightforward to implement. I began actively thinking of workarounds for other essential features. It was now easier to estimate implementation time for certain features since I had a rough idea of the process. I used AI to try to find loop holes in the implementation plans I had but because the Screen Time API is quite undocumented, many times it made things up. After I noticed this, I started requesting for references to confirm its claims.</p><p>From skimming Apple developer Forums, I gathered that there were certain outstanding issues and unpredictable behaviors from some APIs. So I expected it to be an interesting challenge.</p><h3>The Reality</h3><p>Building with these APIs exposed me to a lot of things I didn’t find out during my research. I discovered new problems that I didn’t initially account for, I spent hours going round in circles trying to find solutions to certain issues, not knowing that the issue was an intentional restriction. I spent nights debugging with OSLog, surfed Apple developer forums searching for solutions from people with similar problems. I started implementing certain features and had to change how they work halfway due to platform restrictions.</p><p>Here are some of the issues I faced during implementation:</p><ul><li>User’s device usage data is completely unaccessible to the app, even though it can be visually displayed in the app with SwiftUI. It can’t be extracted or even logged. This is because the system runs such extensions in a read-only sandbox. Any attempts to write contents fail silently — no errors. It simply doesn’t work. Attempting to display usage data with Home Screen Widgets on iOS doesn’t work too.</li><li>Silent push doesn’t work once app is force quit. Since I used silent push to prompt the app to refresh device control rules, the moment the app is force quit there is no way for the app to sync with the backend until the user opens the app again. This meant stale rules and inconsistent behavior. Apparently silent push used to work even when app was force quit but in recent iOS versions that behavior was changed.</li><li>For Screen time authorized by individuals, it can be toggled off from app settings without any hindrance. This means that the user can simply toggle off screen time for the app, authenticate with face id or pin and all restrictions are automatically lifted. Ideally, one should be able to create a different passcode specifically for Screen Time just like it works for the native Apple Screen Time.</li><li>Opaque Tokens are what you get when the user selects apps or websites to be restricted through the family activity picker. The tokens are unidentifiable outside the app. It can’t be decrypted. It can’t be generated using bundle ids. This means there is absolutely no way for you to identify the apps/websites selected by your user. Aside from this, sometimes the OS silently changes the tokens and because of this restrictions won’t work, since ManagedSettings can’t identify the token. The user will need to select the apps again from the family activity picker for restrictions to work.</li><li>On the shield that restricts your users from having access, the secondary button is meant to be configured to request access through your app. The issue is aside from <strong>close,</strong> the only other possible responses that you can configure are <strong>defer</strong> and <strong>none</strong>. None of which can tell your app that the user has just made a request. Ideally one should be able to click on a button on the shield and open your app but Apple has currently confirmed that this action is not supported.</li></ul><p>Most of the issues that I experienced point to the fact that user privacy is prioritized over developer experience. Certain features are flat out impossible and there are boundaries to the kind of control your app can exert over the user’s device.</p><h3>Apple’s Choice of Privacy Over Control</h3><p>Understanding Apple’s choice of privacy over control will help you manage your expectations when attempting to build device control features on iOS platforms. Since Apple owns the platform, you are only going to be able to build what they let you build. This is why it is important to understand the limitations of the platform first and then plan the direction of your product.</p><p>This is also why apps that use MDM have a 85% chance of either being removed from Appstore or not even being approved at all. Apple prioritizes user privacy and data safety over anything else and it shows. While this is great for the users, as this action actively protects them from bad actors. It affects developers that are genuinely trying to build control features customized for different use cases or features that address loopholes in Apple’s own native Screen Time.</p><p>There are several open issues on the Screen Time API that have been lying unaddressed for a long time now. This may be due to the complexity of the Screen Time API itself, regressions and the burden of building while maintaining the balance between managing user privacy and giving developers access.</p><h3>Workarounds That Helped</h3><p>Building in a restrictive environment caused me put think of workarounds to achieve the results I needed. But because it is actually ideal to have these API handle most of these issues out the box, most of these workarounds have their shortcomings.</p><ul><li>Since I couldn’t open my app from the shield, I opted to trigger a local push notification and then write to the App group store of the pending request. When the user taps on the notification and it opens the app, then the app checks the store for any pending request and then shows the request more time/ request access screen. The drawback for this is that notifications can sometimes be blocked when device is on focus mode.</li><li>For the opaque tokens that were returned, in areas that I needed to know the selected app, I simply asked the user to name it themselves. This way the privacy still remains between the user and Apple but now at least I had something the user and I could use to identify the app.</li></ul><h3>Screen Time API vs Apple’s Native Screen Time</h3><p>The initial assumption I had was that the Screen Time API had the same capabilities with Apple native Screen Time. But that wasn’t the case, as third-party apps only receive a carefully controlled subset of the capabilities available to Apple’s own system app.</p><p>Apple’s native Screen Time is integrated in the OS, therefore it has direct, privileged access to iOS internals. This gives them unilateral access to everything on the device and this means they have liberty to create any kind of device usage control feature without restrictions.</p><p>So why do people want to build their own Screen Time apps? The answer is that while Apple native Screen Time does great on many areas, there are still some loopholes and gaps that many parents and individuals have noticed. Especially in this time when parents and guardians are fighting to protect vulnerable members of their families from all the vices that exist on the internet. That and also most people just want to build customized versions of Screen Time apps to suit specific needs.</p><p>But the limitation of the Screen Time API restricts that, giving the Apple native Screen Time the upper hand when one considers functionality and access. Here are some of the things that differentiate Apple native Screen Time from Screen Time API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jIglEnrPs9MNzwJx5HMyAw.png" /><figcaption>Screen Time API vs Apple’s Native Screen Time</figcaption></figure><p>You might wonder, what happens when Apple native Screen Time and your Screen Time app using the API are both active on a device?</p><p>Your app’s ManagedSettingsStore is separate from the one used by Apple’s native Screen Time. Each store operates independently and cannot read, modify, or override the other’s settings.</p><p>For example, if your app blocks YouTube but allows Twitter, while Apple’s Screen Time blocks Twitter but allows YouTube, both YouTube and Twitter will end up blocked. This is because restrictions are additive: if any managed settings store applies a restriction to an app, that restriction takes effect.</p><p>In practice, a “block” always takes precedence over a “don’t block” state. While the stores are isolated from one another, their restrictions are combined by the system when determining what the user can access. As a result, neither your app nor Apple’s native Screen Time can remove restrictions imposed by the other.</p><h3>Conclusion</h3><p>Building with the Apple Screen Time API was both rewarding and challenging. Getting to experience system restrictions, spending time reading through Apple developers forums in search for answers and understanding the design philosophy behind Apple Screen Time API was an interesting experience.</p><p>I understood that the best way to build is to build features within the constraints of the API. Perhaps until things change and the API is upgraded then can anyone build more ambitious features for device usage management. However, trying to build against the current restrictions only leads to frustration.</p><p>If you are starting out building with the Screen Time API, I will encourage to you to research and spend sometime understanding the architecture before delving into implementation. However, there are issues you’ll only get to see during implementation and that’s just part of the experience. If you’ll be using AI to research, ensure you validate it’s claims by checking the references and asking for proof. Since Screen Time is not very documented, AI will make things up many times and tell you something is possible when it isn’t.</p><p>Most of all, enjoy the journey and go ahead to build applications that help users develop healthier relationships with technology.</p><p>For any questions, you can find me on <a href="https://x.com/nikki_eke">X</a>, <a href="https://www.linkedin.com/in/nkechi-eke-software-developer/">LinkedIn</a> and <a href="https://github.com/nikkieke">Github</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e061d14d1f66" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Flutter Developer’s Introduction to Data Binding in Rive]]></title>
            <link>https://medium.com/@nikkieke001/a-flutter-developers-introduction-to-data-binding-in-rive-970009152f30?source=rss-b7ee6504128f------2</link>
            <guid isPermaLink="false">https://medium.com/p/970009152f30</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[rive]]></category>
            <category><![CDATA[flutter-app-development]]></category>
            <dc:creator><![CDATA[Nikki Eke]]></dc:creator>
            <pubDate>Wed, 04 Mar 2026 19:39:13 GMT</pubDate>
            <atom:updated>2026-03-04T19:39:13.183Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tOHQQDBz5S_9Wv-0WK48aw.png" /></figure><p>One of the most debated topics in Flutter development is state management. Developers have strong opinions, and discussions can get pretty heated. But this article isn’t about my views on state management. Instead, it’s about how Flutter’s approach where widgets rebuild automatically to reflect state changes is strikingly similar to Rive’s Databinding.</p><p>Imagine a world where animations in your app update automatically with state changes, no manual triggers, no controllers. Rive animations listen to your app’s state, and databound values adjust in real time. Let’s explore how this works.</p><h3>DataBinding Breakdown</h3><p>Databinding is essentially connecting your app data to elements in the Rive editor. This means that if an element in your animation should update at runtime, databinding exposes its value so it can be updated automatically within your app.</p><p>The process is straightforward. First, in the Rive editor, you create a viewmodel — similar to a class.</p><p>If you’re coming from Flutter, think of this like defining a model or state object. In Flutter, when that state changes, the widget rebuilds and reflects the new value. In Rive, when a viewmodel property changes, the animation updates to reflect that value. Instead of rebuilding widgets, you’re updating visual elements inside the animation.</p><p>In this viewmodel, you define all the properties you want to bind, which can be any of the following:</p><ul><li>Number</li><li>String</li><li>Boolean</li><li>Color</li><li>Trigger</li><li>Enum</li><li>Image</li><li>Artboard</li><li>List</li><li>Nested viewmodel</li></ul><p>To bind a property, you need a viewmodel instance, similar to creating an instance of a class in object-oriented programming. You can have multiple instances of the same viewmodel. Assign the instance to a Rive artboard, and then bind the viewmodel’s properties to elements in your animation.</p><p>For example, suppose you have a simple animated text in Rive. You create a viewmodel with a string property, assign the viewmodel instance to your animated text artboard, and bind the text to the string property. When the string property is updated in your code, the animated text updates automatically at runtime.</p><p>Databinding can also conditionally trigger animation transitions. For instance, imagine a loading animation with two states: loading start and loading stop with a boolean property that transitions between those two states based on it’s value. You bind a boolean property in the viewmodel to a boolean state in your app.</p><p>Instead of calling a controller to play the “stop” animation manually like you would do in Flutter, you simply update a boolean, similar to how setting isLoading = false in Flutter causes the UI to rebuild. The difference is that in Rive, the animation reacts directly to that value.</p><p>You can also switch assets and artboards depending on the state changes within your app. With Databinding you don’t have to create a new animation every time, a single animation becomes a reusable component.</p><h3>DataBinding In Flutter</h3><p>Here is a sample breakdown of how databinding works in Flutter:</p><ul><li>First add the rive dependency to your project</li><li>Then add the rive asset to your asset folder</li><li>Get the names of viewmodels, properties and other entities in the rive file, as you’ll need to reference them by name directly in your Flutter code.</li><li>Define viewmodel instance, property, rive controller and file:</li></ul><pre> File? file;<br>  RiveWidgetController? controller;<br> late ViewModelInstance viewModelInstance;<br> late ViewModelInstanceString stringProperty;</pre><ul><li>Initialize in the initState:</li></ul><pre>@override<br>  void initState() {<br>    super.initState();<br>    file = await File.asset(<br>      &#39;rive-asset-path&#39;,<br>      riveFactory: RiveExampleApp.getCurrentFactory,<br>    );<br>    controller = RiveWidgetController(file!);<br>    // Bind the default view model instance of the artboard to the controller<br>    viewModelInstance = controller!.dataBind(DataBind.auto());<br>    stringProperty = viewModelInstance.string(&#39;string&#39;)!;<br>  }</pre><ul><li>Connect property to state variable</li></ul><pre>stringProperty.value = state-variable;</pre><ul><li>Dispose</li></ul><pre>@override<br>  void dispose() {<br>    stringProperty.dispose();<br>    viewModelInstance.dispose();<br>    controller?.dispose();<br>    file?.dispose();<br>    super.dispose();<br>  }</pre><h3>Spotify’s Wrapped 2025</h3><p>To truly understand data binding in Rive, it helps to see it in action at scale.</p><p>The shift to data-driven animation was felt in Spotify’s Wrapped 2025. On the design and development side, personalizing an animation in video or a prototype would have been nearly impossible. Each design iteration would have required a full rebuild, making the process difficult and time-consuming. With Rive, designers worked independently, mimicked the flow with dummy data, and handed off the animations to developers, who then connected them to real user data.</p><p>For users, the experience felt personal and special, sparking a viral moment as people shared their Wrapped stats across social media. For the company, this translated into more subscriptions and increased revenue.</p><p>Data-driven animation benefits the entire team. Designers maintain creative freedom, developers focus on connecting animation elements to real data, and everyone enjoys a smoother, more effective workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*lY_LRvc0R4PTqZLrqyj7FA.gif" /><figcaption>spotify wrapped 2025</figcaption></figure><h3>Conclusion</h3><p>However, some animations are simply easier to build directly in Flutter. Rive is a third-party platform, and for beginners, there’s a small learning curve that comes with it.</p><p>The sweet spot is knowing when to use each tool. Build in Flutter when it’s straightforward and practical. Reach for Rive when you need dynamic, interactive animations that respond to your app state.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=970009152f30" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flutter CI/CD Guide: Choose the Right Workflow and Automate Your App Releases]]></title>
            <link>https://medium.com/@nikkieke001/flutter-ci-cd-guide-choose-the-right-workflow-and-automate-your-app-releases-0af8f2a9b3b5?source=rss-b7ee6504128f------2</link>
            <guid isPermaLink="false">https://medium.com/p/0af8f2a9b3b5</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[codemagic]]></category>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[cicd]]></category>
            <category><![CDATA[cicd-tools]]></category>
            <dc:creator><![CDATA[Nikki Eke]]></dc:creator>
            <pubDate>Wed, 04 Mar 2026 14:27:05 GMT</pubDate>
            <atom:updated>2026-03-10T11:30:43.133Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*48afrLjx55X5kha9.png" /></figure><p>If you are still building and releasing your Flutter apps manually, you are likely spending hours every week on tasks that could be fully automated. Setting up CI/CD can dramatically reduce that effort, freeing your time to focus on building features, experimenting with ideas, or even launching that side project you have been postponing.</p><p>The challenge, however, is deciding which CI/CD option is right for your team. With so many tools available, making the right choice can feel overwhelming.</p><p>In this article, you will learn the key benefits of CI/CD, the major CI/CD options available for Flutter teams, their pros and cons, and practical recommendations to help you choose the setup that best fits your product and workflow. Let’s dive in.</p><h3>What is Flutter CICD</h3><p>CICD (Continuous Integration / Continuous Delivery) is simply automating the building, testing and deployment of software by integrating code changes frequently and automatically while validating them through a pipeline.</p><p>Flutter CICD is specifically CICD for Flutter applications.</p><h3>Key Benefits of Flutter CICD</h3><ul><li>Faster release cycles: CICD automates build and deployment steps, allowing teams to release updates more frequently instead of waiting for manual processes.</li><li>Easier deployment: Releasing mobile apps involves complex setup steps that include app signing, dependency setup, build configurations. These complex steps are automated by CICD, freeing up the developers to focus on shipping new features.</li><li>Continuous monitoring: Integrating error monitoring and automatic testing to the CICD workflow helps the team catch bugs before and after release.</li></ul><h3>Major CICD Options for Flutter</h3><p>There are many CICD options for Flutter apps available. Below you will find a breakdown of these options, their pros and cons and the kind of teams they are best fit for.</p><h4>Codemagic (Flutter-focused CI/CD)</h4><p>Codemagic is a CI/CD platform designed specifically for Flutter and mobile development, with ready-to-run workflows.</p><p><strong>Pros</strong></p><ul><li>Built specifically for Flutter, so minimal configuration required</li><li>Automatically builds Android and iOS with default workflows</li><li>Supports publishing directly to Play Store and App Store</li><li>Easier setup compared to general CI platforms</li></ul><p><strong>Cons</strong></p><p><strong>Best for:</strong> Flutter first teams wanting fast setup and minimal configuration.</p><h4>Bitrise (mobile-focused CI/CD)</h4><p>Bitrise is a mobile-focused CI/CD platform with ready-made steps for mobile workflows including Flutter.</p><p><strong>Pros</strong></p><ul><li>Strong mobile ecosystem (Android + iOS optimized workflows)</li><li>Pre-configured steps for signing, testing, and deployment</li><li>Good support for device testing and automation</li></ul><p><strong>Cons</strong></p><ul><li>More complex setup than Codemagic</li><li>Build times are slower for Flutter than in Codemagic</li></ul><p><strong>Best for:</strong> Mobile focused teams needing deep third‑party integration support and workflow control.</p><h4>Appcircle (mobile-focused CI/CD)</h4><p>Appcircle is also a mobile-focused CI/CD platform with default workflow templates</p><p><strong>Pros</strong></p><ul><li>Built specifically for mobile apps (supports Flutter workflows)</li><li>Automates code signing and provisioning profile management</li><li>Provides a Workflow Marketplace where you can drag-and-drop workflow steps into your pipeline</li></ul><p><strong>Cons</strong></p><p><strong>Best for:</strong> Mobile focused teams needing fast setup for building and distribution.</p><h4>GitHub Actions</h4><p>A cloud CI/CD service integrated directly into GitHub repositories, widely adopted because of its seamless repository integration.</p><p><strong>Pros</strong></p><ul><li>Native integration with GitHub repositories</li><li>Highly customizable pipelines</li><li>Large marketplace of reusable workflow actions</li><li>No need to manage build servers</li></ul><p><strong>Cons</strong></p><ul><li>Requires more manual setup for Flutter pipelines</li><li>YAML configuration complexity can cause setup challenges</li></ul><p><strong>Best for:</strong> Teams already hosting code on GitHub wanting flexible automation.</p><h4>GitLab CI/CD</h4><p><strong>Overview:</strong></p><p>CI/CD system integrated into GitLab repositories with built-in security scanning and pipeline tooling.</p><p><strong>Pros</strong></p><ul><li>Integrated CI/CD inside GitLab platform</li><li>Built-in security testing and DevOps features</li><li>Flexible pipeline configuration</li></ul><p><strong>Cons</strong></p><ul><li>More configuration required compared to Flutter-specific platforms</li><li>Setup complexity for mobile signing and deployment</li></ul><p><strong>Best for:</strong> Organizations already using GitLab and want to maintain it for their entire DevOps lifecycle.</p><h4>CircleCI / Travis CI (general CI tools)</h4><p><strong>Overview:</strong></p><p>General-purpose CI/CD systems capable of running Flutter builds in containerized environments.</p><p><strong>Pros</strong></p><ul><li>Fast parallel builds (CircleCI)</li><li>Language-agnostic pipelines</li><li>Mature ecosystem of integrations</li></ul><p><strong>Cons</strong></p><p><strong>Best for:</strong> Teams already using these CI platforms for backend or web services and want to maintain it for their entire DevOps lifecycle.</p><h3>Pricing Breakdown</h3><p>Most CICD platforms already offer generous free tiers that allow you spin up and deploy your projects with ease. However, depending on your project needs, team size and frequency of releases you may need to pay to use certain CICD features. Understanding the pricing helps you make the right choice that’ll be beneficial for you and your team on the long run.</p><p>CICD tools generally charge for the following:</p><ul><li>Artifact storage</li><li>Build logs retention</li><li>Additional team members</li><li>macOS machines</li></ul><p>Here is the pricing breakdown of some CICD tools:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EBhjVyVmWJpjS5UPZk9PCg.png" /></figure><h3>Release Automation Tools</h3><p>Release automation tools sit at the CD layer of your pipeline and help you automate other processes required before the app is released. They help you manage processes like app signing, distribution, and store submission, plug them into your CICD tool to fully automate your release workflow.</p><p>Here some release automation tools you can use:</p><h4>Fastlane</h4><p>Fastlane is an open-source automation tool that automates the process of building, signing, and releasing mobile apps to app distribution platforms.</p><h4>What it automates</h4><ul><li>App signing</li><li>Screenshot generation</li><li>Uploading to: App Store Connect, Google Play Store, Firebase App Distribution</li><li>TestFlight deployment</li><li>Version number updates</li></ul><h4>Firebase App Distribution</h4><p>Firebase App Distribution is a service that allows you to distribute pre-release versions of your mobile apps to testers.</p><h4>What it automates</h4><ul><li>Internal testing distribution</li><li>Uploading APKs, AABs, or IPAs</li><li>Tester invitations</li><li>Release notes distribution</li><li>Build notifications</li></ul><p>Most release automation tools use Appstore connect API and Google Play Developer API to carry out actions under the hood. However, you can still use this APIs in custom scripts on your CICD workflows to carry out release automation tasks.</p><h4>Shorebird</h4><p>Shorebird is a Flutter-specific post release automation tool that introduces Code Push to mobile apps. With it your users can get new updates over-the-air (OTA) without having to download from the appstore or playstore. Its only limitation is that you can’t push native code changes, just Flutter and dart code changes.</p><h4>What it automates</h4><ul><li>Code Push Updates</li><li>Patch Distribution</li><li>Update Delivery</li><li>Patch Rollbacks</li></ul><p>It’s especially useful for hotfix production crashes.</p><h3>Resources</h3><p>Selecting a tool for your team or product is an important decision to be made after careful consideration. Personally I am biased to Codemagic and Firebase app distribution as these are the tools I currently use and they get the job done.</p><p>Below are a short collection of links to articles to help you configure your CICD workflows.</p><ul><li><a href="https://blog.codemagic.io/publishing-flutter-apps-to-appstore/"><strong>Publish your Flutter app to App Store with Codemagic CI/CD</strong></a></li><li><a href="https://blog.codemagic.io/publishing-flutter-apps-to-playstore/"><strong>Publish your Flutter app to Google Play Store with Codemagic CI/CD</strong></a></li><li><a href="https://www.aubergine.co/insights/setting-up-ci-cd-for-flutter-android-apps#step-5-configure-firebase-distribution"><strong>Setting up CI/CD for Flutter Android apps With Github Actions, Firebase App Distribution &amp; Fastlane</strong></a></li><li><a href="https://firebase.google.com/docs/app-distribution/ios/distribute-fastlane#authenticate"><strong>Distribute iOS apps to testers on Firebase App Distribution using Fastlane</strong></a></li><li><a href="https://medium.com/simform-engineering/bitrise-getting-started-with-flutter-integration-part-1-1e4cbcffd369"><strong>Bitrise- Getting started with Flutter Integration</strong></a></li></ul><p>Most CICD platforms also provide docs and quick start guides, check those out as well.</p><h3>What makes a great workflow?</h3><p>The basic use of a CICD workflow is to automate your integration and deployment processes to save you hours of manual work. However there are certain steps you could add to your workflow to help you and your team become more effective, improve the quality of your releases and shorten your release cycles. Let’s look at a couple of steps you can add to your workflow to move it from basic to great.</p><h4>Selecting the right CICD option</h4><p>Selecting the right CICD option is obviously a very important step. Considering your team size, your organization structure and your product needs should drive the decision you end up making. Certain choices may seem good at first but end up causing you to rack up unnecessary expenses in the long run.</p><h4>Set up workflow triggers</h4><p>Setting up workflow triggers helps you cut down on the manual work of running the CICD workflow yourself. You can setup your workflow to listen for triggers to run then depending on your setup, simply make a PR or push to a certain branch and the workflow begins to run independently.</p><h4>Incorporate code quality checks</h4><p>When working with a team, it’s important to set up code quality standards using linters. This helps enforce the same standard on every code being pushed. Then by using the Flutter analyze command in your workflow ensure that only code that meets the standard set is being accepted.</p><h4>Integrate automated testing</h4><p>Incorporating automated testing in your workflow enhances quality assurance. This helps you ensure that you aren’t deploying code with failing tests. Integrate jobs to run unit, widget and integration tests in your workflow, reducing the chances of shipping bugs in your code. During CI once any tests fails, ensure you have notifications set to up to ping those responsible for fixing them through channels like slack and email.</p><h4>Set up release automation for both Android and iOS</h4><p>Depending on your product needs and the CICD option you choose, you might still need to integrate release automation tools like Firebase distribution, Fastlane or Shorebird with your CICD tool. While this is optional it can help speed up your releases and iterations.</p><h4>Set up flavored workflows</h4><p>When working on live projects, it highly recommended to create different working environments. This approach helps you save time in the long run. Using the same codebase you can test different configurations, have different release tracks, catch issues before they show up on production etc.</p><p>When you have set up flavored environments for your project then you can set up CICD workflows for those different flavors (environments).</p><p>Personally, I use Firebase distribution for staging releases. This approach helps me catch any existing bugs during testing while on the staging environment before the apps even get to the store.</p><p>If you don’t know about flavors? check these references to get started:<br><a href="https://medium.com/@animeshjain/build-flavors-in-flutter-android-and-ios-with-different-firebase-projects-per-flavor-27c5c5dac10b"><strong>Build flavors in Flutter (Android and iOS) with different Firebase projects per flavor</strong></a></p><p><a href="https://medium.com/@developerjamiu/mastering-flutter-flavors-tailoring-your-app-for-multiple-environments-92c65cd98638"><strong>Mastering Flutter Flavors: Tailoring Your App for Multiple Environments</strong></a></p><h4>Set up automated build versioning and release notes creation</h4><p>Manually updating your app versions for each release can be error prone and time consuming, however this task can be automated right in your workflow. In your workflow you can handle this with a script that checks the latest build released and increments build number by 1. This is possible by using the app store, google play and Firebase distribution APIs available.</p><p>You can also generate release notes from your commits by extracting the commit messages from your last set of commits or from the last git tag. While at this you can use AI to further simplify the release notes so that it’s easier for QA or any non technical member of the team to know what the newest release currently covers.</p><p>You can do this by calling an AI endpoint, passing the extracted commit messages, right there in your workflow using a script. After this you then save in a file, which you pass to your CICD tool to submit alongside the apps to the distribution platform.</p><h4>Set up build notifications</h4><p>To keep your team informed on the status of your releases, it is important to set up build notifications to alert your team on platforms like slack, teams or email.</p><p>With this in place, you can easily share the status of any release with the rest of your team. You don’t have to manually make announcements each time a build is deployed.</p><h4>Integrate error monitoring to your workflow</h4><p>Many times, when a crash happens in production and is picked by your error monitoring tool; the stacktrace is unreadable and because of this it makes it difficult to debug. However, you can fix this issue, by adding a step to your workflow that basically uploads debug symbols to your error monitoring tool after the app is built. With this when a crash happens in prod, the error monitoring tool is able to de-obfuscate the stack trace and now you can see exactly what broke. Sentry and crashlytics work well for this.</p><h4>OTA Automated rollbacks</h4><p>Sometimes software can act unpredictably and a release might suddenly start crashing in prod. Instead of scrambling to fix and submit a new build on the store. You can automate your rollbacks using Shorebird and an error monitoring tool like Sentry. Add a scheduled CI job that checks Sentry’s metrics and if the crash rates exceed a particular threshold, it then automatically triggers a shorebird rollback.</p><h3>Sample Codmagic Workflow Script</h3><p>This is a sample Flutter iOS workflow script that:</p><ul><li>Runs only when last commit contains ticket Id</li><li>Auto-increments build numbers</li><li>Generates AI-powered release notes</li><li>Sets up Flutter and iOS project environments</li><li>Builds the IPA</li><li>Uploads it to TestFlight</li></ul><pre>workflows:<br>  ios_staging:<br>    name: iOS Staging Build<br>    max_build_duration: 60<br>    instance_type: mac_mini_m2<br><br>    integrations:<br>      app_store_connect: YOUR-APPSTORE-CONNECT-API-KEY-NAME<br><br>    triggering:<br>      events:<br>        - push<br>      branch_patterns:<br>        - pattern: &quot;staging&quot;<br>          include: true<br>          source: true<br>      cancel_previous_builds: true<br><br>    environment:<br>      ios_signing:<br>        provisioning_profiles:<br>          - PROFILE-NAME-ON-CODEMAGIC<br>        certificates:<br>          - CERT-NAME-ON CODEMAGIC<br><br>      groups:<br>        - GROUP-NAME<br><br>      flutter: stable<br>      xcode: latest<br>      cocoapods: default<br><br>      vars:<br>        APP_ID: APPLE-APP-ID<br>        VERSION_NAME: &quot;1.0.1&quot;<br><br>    scripts:<br>      - name: Exit build if keyword not defined<br>        script: |<br>          set -e<br>          set -x<br>          COMMIT_MSG=$(git log -1 --pretty=%B)<br>          echo &quot;$COMMIT_MSG&quot;<br><br>          if [[ $COMMIT_MSG != *&quot;OA-&quot;* &amp;&amp; $COMMIT_MSG != *&quot;OH-&quot;* ]]; then<br>            echo &quot;Commit needs to include ticketID in its message.&quot;<br>            exit 1<br>          else<br>            echo &quot;Commit message includes ticketID, moving forward...&quot;<br>          fi<br><br>      - name: Fetch build number<br>        script: |<br>          BUILD_NUMBER=$(($(app-store-connect get-latest-testflight-build-number &quot;$APP_ID&quot;) + 1))<br>          echo &quot;BUILD_NUMBER=$BUILD_NUMBER&quot; &gt;&gt; $CM_ENV<br><br>      - name: Generate AI release notes with Claude Haiku 4.5<br>        script: |<br>          set -eo pipefail<br>          VERSION_NAME=${VERSION_NAME:-&quot;Unknown&quot;}<br>          BRANCH_NAME=${CM_BRANCH:-&quot;unknown&quot;}<br>          COMMITS=$(git log -10 --pretty=format:&quot;%s&quot; --no-merges || echo &quot;&quot;)<br><br>          write_release_notes() {<br>            local TEXT=&quot;$1&quot;<br>            jq -n --arg text &quot;$TEXT&quot; \<br>              &#39;[{&quot;language&quot;: &quot;en-US&quot;, &quot;text&quot;: $text}]&#39; &gt; release_notes.json<br>            cat release_notes.json<br>          }<br><br>          if [ -z &quot;$COMMITS&quot; ]; then<br>            echo &quot;No commits → fallback basic notes&quot;<br>            FALLBACK=&quot;APP\n\nVersion: $VERSION_NAME ($BUILD_NUMBER)\nBranch: $BRANCH_NAME\n\nNo significant changes detected in this build.&quot;<br>            write_release_notes &quot;$FALLBACK&quot;<br>            exit 0<br>          fi<br><br>          PAYLOAD=$(jq -n \<br>            --arg commits &quot;$COMMITS&quot; \<br>            &#39;{<br>              model: &quot;claude-haiku-4-5&quot;,<br>              max_tokens: 800,<br>              temperature: 0.2,<br>              messages: [{<br>                role: &quot;user&quot;,<br>                content: (&quot;Create concise plain text release notes from these commits:\n\n&quot; + $commits + &quot;\n\nInclude Features, Improvements, Bug Fixes sections. Do not use &lt; or &gt; symbols.&quot;)<br>              }]<br>            }&#39;)<br><br>          RESPONSE=$(curl --silent --show-error \<br>            -H &quot;Content-Type: application/json&quot; \<br>            -H &quot;x-api-key: $ANTHROPIC_API_KEY&quot; \<br>            -H &quot;anthropic-version: 2023-06-01&quot; \<br>            --data &quot;$PAYLOAD&quot; \<br>            https://api.anthropic.com/v1/messages) || true<br><br>          echo &quot;$RESPONSE&quot; &gt; claude_raw.json<br>          NOTES=$(jq -r &#39;.content[0].text // empty&#39; claude_raw.json 2&gt;/dev/null)<br><br>          if [ -z &quot;$NOTES&quot; ]; then<br>            echo &quot;Claude failed → fallback&quot;<br>            FALLBACK=$(printf &quot;APP\n\nVersion: %s (%s)\nBranch: %s\n\nRecent commits:\n%s&quot; \<br>              &quot;$VERSION_NAME&quot; &quot;$BUILD_NUMBER&quot; &quot;$BRANCH_NAME&quot; \<br>              &quot;$(git log -10 --pretty=format:&#39;- %s&#39; --no-merges)&quot;)<br>            write_release_notes &quot;$FALLBACK&quot;<br>          else<br>            write_release_notes &quot;$NOTES&quot;<br>          fi<br><br>      - name: Set up code signing settings on Xcode project<br>        script: |<br>          xcode-project use-profiles<br><br>      - name: Get Flutter packages<br>        script: |<br>          flutter pub get<br><br>      - name: Install CocoaPods<br>        script: |<br>          pod install --project-directory=ios<br><br>      - name: Build iOS IPA<br>        script: |<br>          flutter build ipa \<br>            --release \<br>            --build-name=$VERSION_NAME \<br>            --build-number=$BUILD_NUMBER \<br>            --export-options-plist=/Users/builder/export_options.plist<br><br>    artifacts:<br>      - build/ios/ipa/*.ipa<br><br>    publishing:<br>      app_store_connect:<br>        auth: integration<br>        submit_to_testflight: true</pre><h3>Best practices for CICD</h3><ul><li>Keep pipelines fast: long pipelines slow teams down and delay adoption. Cache dependencies, run jobs in parallel and avoid rebuilding unchanged components.</li><li>Automate everything that is repeatable: reducing manual steps lowers human error and improves reliability. Automate jobs like versioning, store deployment, lint checks etc</li><li>Use flavored environments: this is recommended Devops practice as it helps you manage the workflows for the different environments, improving testing and reducing errors.</li><li>Secure your pipeline: use encrypted secrets and least privileged access for your workflows. Store your secrets in CI secret managers.</li><li>Keep your workflows maintainable: Avoid massive monolithic scripts. Keep the workflow file readable.</li></ul><h3>Conclusion</h3><p>Setting up CICD for your Flutter apps will improve your quality of life as a Flutter developer. No more long hours spent in manually building and distributing your Flutter apps on different platforms. You can now build once, push your code and go for a coffee break, then come back to find the app waiting in the stores.<br> For any questions, you can find me on <a href="https://x.com/nikki_eke">X</a>, <a href="https://www.linkedin.com/in/nkechi-eke-software-developer/">LinkedIn</a> and <a href="https://github.com/nikkieke">Github</a>.</p><p><em>Originally published at </em><a href="https://dev.to/nikki_eke/flutter-cicd-guide-choose-the-right-workflow-and-automate-your-app-releases-5dkm"><em>https://dev.to</em></a><em> on March 4, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0af8f2a9b3b5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>