# Feature Flagging Published articles for Feature Flagging. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Feature Flag Security in your CI/CD Pipeline DevFeed: [Feature Flag Security in your CI/CD Pipeline]() Original publisher: [Read original article]() Author: Lena Sano Published: 2026-07-22T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [feature flags](), [Security](), [CI/CD](), [AI Agent]() Tags: [ai-agent](), [ci-cd](), [cleanup](), [feature](), [feature-flagging](), [feature-flags](), [governance](), [lifecycle](), [local](), [pii](), [privacy](), [remote](), [security]() ### AI overview This article explains security practices for Harness Feature Management and Experimentation. It covers local versus remote feature-flag evaluation, privacy considerations for sensitive user data, governance, automated cleanup, and an AI agent for feature-flag lifecycle management. ### Source excerpt Secure feature flags with Harness FME using local or remote evaluation, automated cleanup, governance, and AI-powered lifecycle management. | Blog ## How Senior Engineers Take a Feature from Start to Delivery DevFeed: [How Senior Engineers Take a Feature from Start to Delivery]() Original publisher: [Read original article]() Author: Tiger Abrodi Published: 2024-03-28T17:06:09Z Content type: tutorial Language: en Sources: [Saiyan Growth Letter]() Topics: [Development](), [Users](), [Requirements](), [data](), [iteration](), [pull-requests]() Tags: [data](), [delivery](), [developers](), [development](), [feature-flagging](), [how-to](), [iteration](), [pull-requests](), [requirements](), [simplicity](), [users]() ### AI overview This tutorial presents an approach for taking a software feature from initial justification through delivery. It recommends validating why the feature is needed, defining a minimum viable product, choosing a simple technical solution, breaking the work into small tasks, and using feature flagging and rollout practices. ### Source excerpt How Senior engineers take a feature from start to delivery ## Now you see me, now you don't: feature-flagging with LaunchDarkly at incident.io DevFeed: [Now you see me, now you don't: feature-flagging with LaunchDarkly at incident.io]() Original publisher: [Read original article]() Author: Sophie Koonin Published: 2021-11-09T00:00:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [feature flags](), [Pull Request](), [Code](), [App](), [systems]() Tags: [app](), [code](), [feature](), [feature-flagging](), [feature-flags](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [outage](), [post-mortem](), [production](), [pull-request](), [slack-incident](), [systems]() ### AI overview The article explains how incident.io uses feature flags to ship small, incremental changes rapidly while hiding unfinished features from customers. It discusses boolean flags, pull-request size and reviewability, long-lived branches, and the choice between building or buying a feature-flagging system. ### Source excerpt At incident.io, we ship FAST. Find out how feature flags allow us to keep changes small and incremental while also hiding unfinished features from customers. ## How to Toggle Features in C# with Feature Flags DevFeed: [How to Toggle Features in C# with Feature Flags]() Original publisher: [Read original article]() Author: umer Published: 2021-08-26T00:00:00Z Content type: tutorial Language: en Sources: [Code Ahoy - Articles]() Topics: [feature flags](), [.NET](), [Development](), [web applications]() Tags: [c-sharp](), [feature-flagging](), [feature-flags](), [net](), [tutorial](), [web]() ### AI overview This tutorial explains how to use feature flags to toggle functionality in .NET Core web applications. It covers controlling feature visibility independently of deployment, testing features in production, rolling back changes, and gradually releasing features to users. ### Source excerpt Note: Unlaunch, the feature flagging service referenced in this post, has been shut down. Links to it have been removed. This blog post was contributed by Tuan Nguyen, Software Developer at Getty Images. Using feature flags to release new features to customers is a powerful technique. I have been using feature flags for many years to release features or changes to production safely and with the peace of mind. The releases are done without any ceremony, and the features aren't visible to customers until we turn the feature flag on. Using feature flags to toggle functionality in .NET Core apps is easily achievable using a feature flag management platform. In this tutorial, I'll show you how to toggle features on demand in a simple web application using Unlaunch (Link Removed) to create and manage feature flags. We'll also see how to show or hide our features with a click of a button, without merging branches, rollbacks or deploys. Feature Flags Feature flags allow developers to control who sees new features irrespective of code deployment. For example, developers can deploy a new feature to production environment and keep it hidden from all users (except themselves.) This way, they can do testing on real systems, and when the management is ready to release the feature, they can turn on the feature flag to let the users in on it. To me, here are some of the benefits of using feature flags: Developers eliminate some of the risk knowing they can roll things back instantly if things go wrong. On a few occasions, I rolled back features because of negative impact to KPI we didn't consider before or one of the underlying system wasn't quite ready. Developers can launch the feature on production behind feature flag and show it to product or marketing team for their feedback. QA in production. This doesn't mean that we skipped testing on the 'Dev' environment, but rather launching the feature on production just for the development team give extra boost of confidence. It also a ## Improved version targeting in Remote Config DevFeed: [Improved version targeting in Remote Config]() Original publisher: [Read original article]() Author: Karen Zeng; Kevin Elko Published: 2020-10-05T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [App](), [Android](), [iOS](), [SDK]() Tags: [android](), [feature-flagging](), [firebase](), [ios](), [launch](), [new-feature](), [news](), [remote-config](), [updates]() ### AI overview Firebase Remote Config adds semantic version targeting with greater-than and less-than operators, and improves iOS version targeting by introducing conditions based on CFBundleShortVersionString while renaming the previous build-number conditions. ### Source excerpt News, tutorials, and updates from the Firebase team. ## A/B Tested, Feature Flagged, White-Label Apps with Webpack DevFeed: [A/B Tested, Feature Flagged, White-Label Apps with Webpack]() Original publisher: [Read original article]() Author: Andy Weiss Published: 2020-06-17T19:15:05Z Content type: tutorial Language: en Sources: [RBI Tech]() Topics: [Webpack](), [React](), [configuration](), [import](), [App]() Tags: [a-b-testing](), [configuration](), [feature-flagging](), [import](), [react](), [webpack]() ### AI overview This tutorial explains how to customize Webpack in a Create React App project to build and deploy multiple application variants from one codebase. It discusses use cases including A/B testing, feature flagging, platform targeting, and custom themes, with attention to file-extension resolution and import behavior. ### Source excerpt For most of us, the thought of tweaking our app's Webpack configuration inspires about the same level of excitement as a bi-annual trip to the dentist. We know it's important, necessary even -- certainly better than the alternative -- and yet, the goal is mostly to get in and out without anything going wrong. The popularity of Create React App and other tools is largely built upon their ability to abstract away these configuration details and allow developers to focus on shipping features quickly. But the better we know our tools, the more likely we are to recognize when they fit a particular problem we face in our work. For a certain class of project, it's worth considering Create React App's defaults as a starting point, rather than the end of the conversation. Thoughtfully applied, some small modifications can unlock a world of possibility. For example, we often know at the outset of a project that we will need to build and deploy different versions of our application. Whether it's for A/B testing, feature flagging, targeting specific platforms, or applying a custom theme, we want the ability to maintain multiple parallel universes around a single codebase without unnecessary duplication or complexity. Webpack's ability to select from a variety of file extensions at build time makes it an especially useful tool for this task. You'd probably be surprised to see how just easy it is to achieve a high level of flexibility with minimal configuration. More Intentional File Extensions Part of Webpack's magic comes from its ability to guess our intentions when we leave off the file extension at the end of an import. We do it so often we may barely notice, but how many times have we written code like this? https://medium.com/media/2f79921db578db57aa03929c826ccb82/href Maybe there's a Nav.js file in the components directory, or possibly the extension is .jsx or .tsx. Maybe Nav is actually a directory itself, and there's an index.js or index.jsx that's exporting the component ## Using Cloud Functions to update Remote Config in near real-time DevFeed: [Using Cloud Functions to update Remote Config in near real-time]() Original publisher: [Read original article]() Author: Mayank Jain Published: 2018-11-09T00:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Cloud Functions](), [Firebase](), [Caching](), [feature flags](), [API]() Tags: [api](), [caching](), [cloud-functions](), [feature](), [feature-flagging](), [feature-flags](), [firebase](), [news](), [remote-config](), [rest-api](), [tutorials](), [updates]() ### AI overview This Firebase team tutorial explains Remote Config caching and shows how Cloud Functions for Firebase triggers can run code when a team publishes Remote Config values through the Firebase Console or REST API, helping apps receive fresh values promptly. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Feature-oriented APIs DevFeed: [Feature-oriented APIs]() Original publisher: [Read original article]() Author: Nathan Petryk Published: 2017-11-01T15:31:01Z Content type: tutorial Language: en Sources: [RetailMeNot]() Topics: [Clojure](), [API](), [Code](), [version]() Tags: [api](), [apis](), [clojure](), [code](), [feature-flagging](), [mobile-app-development](), [versioning]() ### AI overview This article explains how RetailMeNot's Mobile API team evolved a Clojure versioned macro for feature-oriented API development. The approach adds feature rollout support and a feature-flagging system while addressing the limitations of linear, version-based code annotations. ### Source excerpt In my last post -- Minimally Invasive API Versioning -- I talked about how the Mobile API team at RetailMeNot handles versioning our Clojure APIs using a macro called versioned. This macro alone worked great for over a year, but we needed more. In this post I will cover how we evolved it to help ease our feature rollout process, and how we gained a super-easy feature flagging system basically for free. To recap, the versioned macro introduces a convenient syntax for annotating source code with version-specific information -- things like "this line was added in version 3" or "this line was removed in version 7." We call these annotations version-qualifiers. Initially we had several. some were "binary", like added, removed, only, which let the developer specify code that should or should not exist for a specific application version; and others, like changed, lets the developer specify alternative implementations based on the application version. https://medium.com/media/9c51608aa7d9e2240fdbdcc10742c8d5/href We call these qualifiers collectively linear version-qualifiers, because their functionality is based on the linearity of versions: something like "added in version 2"makes no sense without the assumption that V1 precedes V2, which precedes V3, etc. Like I said, this reasoning got us very far, but it has one major drawback: we typically ship multiple features per version, and when we do encountering this version-specific code would often leave developers wondering, "Why was this change made? Which feature was it a part of?". Furthermore, say a feature slipped and we needed to move it to a later version, we found it difficult to go back through the code base to identify and edit those places only related to that feature. The fundamental problem is that when we annotate code with linear version-qualifiers we imbue that code with version-specific information. Stated another way, these kinds of annotations only let a developer look at the code and answer the question, "Wh