April 2025 Summaries

Feature flags are a powerful tool for developers, allowing them to activate or deactivate features in their software without redeploying code. This functionality is explored through a practical example using a Node.js Express application, where Flagsmith feature flags are utilized to control the visibility of footer icons. Node.js, an open-source, cross-platform runtime environment, enables server-side execution of JavaScript, making it ideal for scalable and real-time applications. The guide explains how feature flags, also known as toggles, enable gradual feature rollouts, testing with specific user groups, and quick feature disablement in case of issues. The tutorial details setting up a feature flag on Flagsmith and integrating it into a Node.js application, emphasizing the importance of caching with node-cache to reduce API calls. Additionally, it showcases deployment on Railway.app, highlighting the flexibility of environment variables for switching between development and production environments. The guide concludes by encouraging readers to explore Flagsmith for their Node.js projects and offers further resources for implementing feature flags in various programming languages.

The guide explores the integration of feature flags in Angular applications, using a practical example of controlling the rendering of a search UI in an insurance package selector component. It introduces Angular, a popular TypeScript-based web development framework by Google, known for dynamic web app creation through high-level solutions like data binding and state management. The document delves into feature flags, which allow developers to deploy and release features separately, enhancing workflows and reducing risk through mechanisms like phased rollouts and A/B testing. The guide details the process of setting up feature flags using Flagsmith, demonstrating how to create and manage a feature flag to toggle the visibility of a search input and button without code changes or redeployment. It further explains the creation of a feature flag service and directive in Angular, enabling feature flag utilization in components, and offers insights into testing and potential further applications of feature flags. The approach underscores the ability of feature flags to facilitate continuous deployment and efficient product releases, supported by Flagsmith's open-source and flexible deployment options.

Flagsmith has launched an integration with GitHub, offering a streamlined approach to feature flag management within the software development lifecycle. This integration allows developers to track the progress of feature flags directly through GitHub Issues and Pull Requests, providing enhanced visibility and automation in aligning code changes with feature releases. Users can link Flagsmith features with GitHub PRs or Issues, with automatic comments generated in GitHub whenever a flag is updated. Future updates aim to make the integration bidirectional, allowing GitHub events to automatically create tags in Flagsmith. The setup process involves installing the Flagsmith app from the GitHub Marketplace and configuring it to associate specific repositories with Flagsmith projects, thereby facilitating effortless monitoring and improved visibility of feature statuses across different environments.

Feature flags are an essential tool for managing application updates, enabling developers to release new features to a subset of users before a full rollout, allowing for monitoring and analysis of the update's impact. Key metrics to track during a new feature release include time spent in the application, application open frequency, goal completion rates, application load time, downtime and crashes, and support requests. These metrics help determine whether a new feature is effective or if it necessitates a rollback. Flagsmith offers native integrations with major analytics and data platforms such as Heap, Mixpanel, Datadog, and AppDynamics, allowing companies to analyze data within their existing infrastructure. By leveraging these integrations, companies can streamline their feature rollouts, monitor performance effectively, and ensure user satisfaction.

The article provides a detailed guide on implementing feature flags in a Xamarin application using Flagsmith, a .NET feature management platform, which can also be applied to other .NET frameworks like WPF, ASP.Net, Unity, or Godot. It begins with a brief overview of Flagsmith, explaining its capability to manage features and store environment variables, thereby saving development time by eliminating the need for separate admin panels. The guide walks readers through a step-by-step process of setting up Flagsmith by cloning a sample Todo application, signing up for a Flagsmith account, creating new features, and integrating these features into the project using Flagsmith's SDK. It emphasizes using flags to control application behavior, such as blocking new entries during maintenance or customizing UI elements like header colors. Additionally, the article explores the concept of local evaluation to enhance performance by reducing API calls, and concludes by highlighting the benefits of using Flagsmith for confident feature releases, offering both hosted and on-premises solutions.

Flagsmith's journey to becoming a remote-first company highlights the challenges and rewards of building a global, distributed team. Initially not a remote-first company, Flagsmith evolved due to circumstances like the COVID-19 pandemic and strategic decisions, leading to a diverse team spread across multiple countries. The company has navigated various remote work challenges, such as logistical hurdles and cultural differences, while embracing the benefits of global hiring, increased client support, and tools for asynchronous workflows. A particularly cherished aspect of remote work for the founder is providing employees with opportunities for travel and cultural experiences, exemplified by a memorable team gathering where an employee from South Korea attended a Manchester United game, showcasing the personal connections and unique opportunities that can arise in a remote-first environment.

The integration of Flagsmith with Jira offers a significant enhancement to software development and project management by allowing teams to manage feature flags directly within Jira, streamlining the development and testing process. Feature flags, a crucial tool in software development, enable teams to toggle functionalities on or off post-deployment, facilitating continuous delivery, minimizing deployment risks, and supporting A/B testing. This integration simplifies the workflow by providing direct access to feature flag values and update timestamps within Jira tickets, eliminating the need to switch between platforms. This setup not only benefits developers, QA teams, and product managers but also fosters a collaborative and efficient development environment by enabling multiple issues to link to a single Jira ticket, thus improving organizational flexibility and transparency.

Transitioning from legacy continuous integration (CI) systems to modern platforms is crucial for organizations seeking to enhance efficiency, scalability, and developer satisfaction. Legacy CI systems, while once reliable, often struggle with high maintenance costs, scalability limitations, complex configurations, and security vulnerabilities, ultimately hindering productivity and growth. Modern CI platforms, such as Semaphore CI/CD, address these challenges by offering automated scalability, cost savings, improved security features, and enhanced developer experiences with user-friendly interfaces and comprehensive support. These platforms support hybrid operations, enabling organizations to leverage both cloud and on-premise solutions for optimal flexibility. Transitioning to modern CI requires careful planning and execution, including assessment, proof of concept, setup, migration, training, and continuous improvement to ensure the new platform aligns with organizational needs and boosts development efficiency.

Flagsmith, an open-source feature flagging company, has chosen to bootstrap its growth rather than pursue external capital, as discussed by founder Ben Rometsch on the Developer-Led Podcast with Jonathan Reimer. By running an agency alongside Flagsmith initially, the company alleviated financial pressures and allowed for gradual refinement of its Ideal Customer Profile (ICP), eventually reaching $1 million in annual recurring revenue. The company believes in the advantages of small teams and a simple monolithic product, emphasizing the freedom to make independent business decisions without the constraints of venture capital. Flagsmith focuses on providing feature flags that customers can run in their own infrastructure, with a particular emphasis on preventing code lock-in by collaborating with OpenFeature. The company has benefited from a steady stream of inbound leads from enterprises seeking enterprise licenses and on-premises feature flags, guiding its strategy and growth without relying on external funding.

The text explores the evolution and best practices of modern software deployment, emphasizing the importance of automating builds, testing, and deployments to achieve seamless and frequent production releases. It contrasts the cumbersome and manual processes of the late 1990s with today's advancements in continuous integration and continuous deployment (CI/CD) pipelines, highlighting tools like Docker and CI platforms such as CircleCI and GitHub Actions that facilitate automation and predictability. The narrative underscores the necessity of standardizing development practices, automating build pipelines, and running comprehensive automated tests to ensure reliability and efficiency. It also emphasizes the value of containerization and stateless application design for simplifying deployment processes and achieving zero downtime, encouraging teams to gradually implement these practices for long-term benefits.

Filippo Sarzana, Tech Lead at Serenis, explains how the mental health platform effectively utilizes feature flags for continuous delivery and A/B testing, focusing on seamless product development rather than in-house feature flag management. Since adopting Flagsmith in October 2021, Serenis has leveraged it for various use cases, including testing new features with specific user segments before wider rollout and conducting comprehensive A/B tests on features, menu sections, booking systems, and algorithms. The platform employs Flagsmith for efficient integration with their internal tools and data warehouse, utilizing webhooks and analytics to produce business intelligence insights. The decision to use a third-party tool like Flagsmith rather than building an in-house solution stems from the need to focus resources on product development, coupled with the efficiency and cost-effectiveness offered by established feature flag systems. Serenis uses the Flagsmith Cloud hosted version with Aurora AWS database and integrates it with platforms like Slack and Mixpanel to enhance operational efficiency and data analysis, employing React, React Native, and Node.js SDKs for seamless integration with their existing tools.

Many banks are transitioning to modern software development practices to become more agile and meet customer demands effectively, despite challenges like regulatory compliance and legacy infrastructure. Romano Roth, Chief of DevOps at Zühlke, highlights the debate between cloud-based versus on-premises development and emphasizes the importance of continuous integration to enhance adaptability and efficiency. The push for modernization is driven by the need for faster time to market, cost efficiency, and improved customer satisfaction, often hindered by outdated processes and infrastructure. A hybrid approach, combining cloud development with on-premises deployment, helps address security concerns associated with cloud adoption. By embracing practices such as continuous deployment, feature flags, and test-driven development, banks can improve the developer experience and accelerate the release of new features. This modernization is not solely about reducing expenses or speeding up processes but about fostering an innovative and responsive banking environment that aligns with evolving market demands.

Feature Flags have become essential in modern software delivery, but current solutions often rely on proprietary SDKs that create challenges, such as the need for re-architecture when switching platforms, inconsistency when multiple platforms are used, and complex integration with other software delivery tools. OpenFeature aims to resolve these issues by offering a vendor-neutral, open standard for feature flag management, enabling developers to use a unified API through SDKs implemented in various languages. This standard allows feature-flagging platforms to integrate seamlessly, providing a consistent API for flag evaluation across different tech stacks, thus simplifying the ecosystem and reducing vendor lock-in. Contributing members to this initiative include major industry players like Google, GitLab, and LaunchDarkly, reflecting a significant advancement in the standardization of feature flag management.

Flagsmith has partnered with Heap to enhance A/B testing capabilities by integrating feature flag performance data with customer behavioral insights. This integration enables teams to rapidly iterate and optimize digital experiences by viewing feature flag states for identified users within Heap, without needing engineering intervention. By decoupling deployment from release, development teams can push code to production multiple times a day, allowing product managers to test and refine features based on user interactions. Flagsmith facilitates quick feature deployment to selected user segments, and Heap's tools provide analysis of customer behavior, enabling targeted rollouts and real-time tracking of outcomes. This synergy between Flagsmith and Heap allows for efficient execution and analysis of A/B tests, helping over 6,000 businesses improve their product development process and user experiences.

Flagsmith employees discuss the benefits and drawbacks of working in a bootstrapped company, emphasizing the autonomy and alignment that come from setting internal goals rather than adhering to investor-driven directives typical in VC-backed firms. The sense of partnership and collaboration is heightened in a bootstrapped environment, as strategic decisions are made internally, with a focus on sustainable growth rather than rapid expansion, which often leads to cultural drift and instability in VC-backed companies. Employees enjoy a sense of ownership and personal responsibility, which empowers them to contribute significantly to the company's vision, although it can also lead to pressure and high workload. Financially, bootstrapping offers a more stable path with modest gains through profits and dividends, contrasting with the high-risk, high-reward potential of VC-backed ventures. Different departments, such as sales, marketing, and engineering, benefit from the creative freedom and flexibility that bootstrapping allows, enabling them to tailor processes and strategies that align with the company's long-term goals.

The financial sector is at a pivotal moment in its relationship with open source, transitioning from merely consuming open-source technologies to contributing to them, although challenges remain. Rob Moffat of FINOS, part of the Linux Foundation, notes that while more banks are joining FINOS and exploring open-source projects, significant cultural and regulatory barriers persist, including risk aversion and compliance concerns. Despite these challenges, the potential benefits of open source, such as risk mitigation, strategic advantage, and more efficient staffing, are driving slow but steady progress. FINOS plays a crucial role in this transition by offering support, training, and resources to help financial institutions integrate open source into their operations. Banks are exploring pathways to open source through trial projects and tackling policy restrictions, aiming for a future where open source is embedded in the financial sector's regulatory framework.

Wistia, a video marketing platform, leverages Flagsmith to enhance its release management and continuous deployment processes, enabling them to deploy 20-30 times a day with targeted rollouts. Nick Quaranto, Director of Platform Engineering at Wistia, discusses how the transition from a homegrown feature flag system to Flagsmith has improved flexibility and reduced the workload for their teams. Initially, Wistia faced challenges with their custom system, which lacked the flexibility needed for specific targeting and segmenting ideas from the product team. By adopting Flagsmith, an open-source feature flagging software, Wistia has streamlined their deployment process, increased reliability, and allowed their product team to focus on creative rollouts without manual tinkering. The move to Flagsmith has been smooth, with high adoption rates across teams, and has provided a safer and more efficient deployment environment. The success is evident in the qualitative and quantitative improvements in their deployment frequency and overall organizational health, as feature flagging has become integral to their continuous delivery strategy.

Banks are increasingly recognizing the necessity to modernize their systems to keep up with customer expectations and market demands, moving away from monolithic architectures and lengthy release cycles. Many banks, hindered by legacy systems and regulatory complexities, are turning to feature flags as a means to improve software delivery and foster innovation. Feature flags allow for more agile development by decoupling deployment from release, enabling incremental rollouts, and offering the flexibility to toggle features on or off without redeployment. Institutions like Citibank, Komerční Banka, and Alt Bank have successfully leveraged feature management platforms like Flagsmith to streamline their release strategies, migrate to microservices, and enhance development velocity while maintaining security and compliance. By adopting feature flags, banks can experiment with features more dynamically, gain strategic advantage, and mitigate risks associated with flawed releases, thus staying competitive in an evolving digital landscape.

Modern software engineering teams in data-sensitive organizations are increasingly opting for self-hosted feature flagging services to gain speed, security, and control benefits, particularly in regulated industries like banking and healthcare. While SaaS offers ease of setup and management, self-hosting allows organizations to maintain strict data security and compliance with governmental or industry-specific regulations, offering complete control over data storage and interaction with other services. Flagsmith, an open-source feature flagging platform, provides flexibility and performance advantages, enabling teams to run software within their own network infrastructure for faster and more secure communication. The enterprise version of Flagsmith offers additional features such as Role Based Access Controls (RBAC) and integration with various authentication providers, enhancing its utility for large organizations. By allowing teams to host in preferred geographical locations and integrate seamlessly with existing tech stacks, Flagsmith supports modern deployment practices without sacrificing security or performance.

Palo Alto Software, led by development manager Jedidiah Hurt, employs feature flags to enhance their software development process, particularly for their products like LivePlan and Outpost. Their development process involves using a tech stack comprising React, Java Dropwizard, Postgres, Elasticsearch, and Redis, alongside an agile scrum methodology with two-week sprints and weekly releases. Feature flags have notably increased their deployment cadence by allowing new features to enter production swiftly for feedback without extensive QA processes, although they face challenges such as managing unused flag paths post-rollout. The integration of Flagsmith has facilitated smoother workflows, enabling experiments in production without extensive rollbacks, though Jedidiah highlights the need for built-in caching support in the Java SDK to optimize backend performance.

Flagsmith has introduced a new integration that allows users to view feature flags directly within Jira issues, providing visibility into which flags are active or inactive across different environments and whether segment overrides are applied. Currently in its Beta stage, the integration invites users to set it up, offer feedback, and stay informed through newsletters and updates. To get started, Flagsmith account holders can access the integration via the Atlassian marketplace by adding their API key and connecting their chosen organization, after which they can associate projects and add Flagsmith flags to Jira tickets. The development team encourages users to share questions or feedback to improve the integration's value for various workflows.

alt.bank, a Brazilian fintech firm, initially built its financial products with basic feature toggles but found these insufficient as they scaled their offerings, including debit and credit cards, underwriting, and credit scores. Faced with limited feature management functionality that couldn't keep up with their growing customer needs, the team, led by Engineering Manager Caio Gandra, opted to implement Flagsmith for robust feature flagging. This transition allowed alt.bank to manage features more effectively, supporting their shift from a monolithic architecture to microservices, and enabling seamless and continuous deployment of changes in their mobile application without lengthy approval processes. The new system provided the necessary scalability and support, allowing them to integrate flag management across both backend systems and mobile applications, ensuring flexibility crucial for their rapidly evolving startup environment.

In banking and financial institutions, developers face challenges with legacy systems that limit their ability to deploy frequently, resulting in large, error-prone releases. Transitioning to modern feature management, including the use of feature flags, can help decouple deployment from release, reduce bottlenecks, and increase release velocity, allowing for more agile and confident feature deployment. Feature flags also provide a safety net for iterative code releases, enabling phased rollouts and quick feature deactivation, which is crucial in a highly regulated environment like banking. Modern feature management tools, such as Flagsmith, not only cater to data security needs but also support continuous deployment processes, improving developer confidence and reducing the pressure of traditional release cycles. By adopting these tools and practices, banks can enhance their software development processes, better meet compliance standards, and deliver improved products to customers more efficiently.

Venture capital is no longer a necessity for tech startups, with many bootstrapped companies successfully competing against heavily funded rivals by focusing on niche markets and sustainable growth. Bootstrapping allows companies to concentrate on customer satisfaction and maintain profitability without the pressures of meeting external revenue targets or rapid expansion mandates. The evolution of technology has reduced the financial barriers to entry, enabling startups to launch with minimal costs and leverage open-source tools. Bootstrapped firms, like Flagsmith, emphasize sustainability and flexibility, allowing them to grow at their own pace and avoid the pitfalls of traditional venture-backed models, such as the pressure of fundraising cycles and the risk of unsustainable growth. This approach aligns with an ethos that values creativity, customer focus, and the freedom to chart their own course without the constraints imposed by external investors.

Flagsmith, originally open-sourced in June 2018, has undergone significant evolution from its early private development stages to its current status as a critical tool for many companies. Initially, the project was built in private, but the team later adopted an open development approach, recognizing its substantial benefits. As the platform's user base expanded, the pressure to maintain high-quality releases increased, especially given the crucial role of feature flagging in delivering consistent product experiences. To address API latency issues, particularly for customers in remote regions like Sydney, Flagsmith developed an Edge API, allowing for sub-200ms latency globally. This involved replicating data across a new domain, necessitating a comprehensive rewrite of their SDKs in multiple languages to shift flag processing from the API to the SDKs themselves, enhancing flexibility and reducing latency for server-side applications. The release of the new Edge API and version 2.0 SDKs, though a daunting undertaking, was designed to be seamless, ensuring no downtime for customers. This pivotal update, provided for free across all plans, aims to enable faster releases and continuous product improvement for Flagsmith's diverse user base.

Flagsmith has launched a referral program designed to offer content creators, agencies, and developer advocates the opportunity to earn passive income by promoting its feature flag software. Participants can earn a 25% commission on every referral that converts into a paying Flagsmith customer, with no initial investment or contract required. The program aims to reward individuals who are already part of the Flagsmith community and actively sharing the product with others. Interested parties can quickly join by contacting Flagsmith to receive a unique referral link, which can be used in various marketing materials to promote the product. The initiative provides ongoing support through a designated Flagsmith contact to assist with marketing strategies and address any queries. This program targets individuals such as content creators, developer advocates, developer agencies, and consultants who can leverage their existing networks to generate sales and earn recurring commissions.

Flagsmith founder Ben Rometsch discusses the challenges and strategies involved in building an open-source feature flag tool on the Open Source Startup Podcast with Amanda Robson and Timothy Chen. The conversation explores the rationale behind choosing open-source development, emphasizing the importance of community growth and the deliberate pace at which they've expanded. Rometsch explains that Flagsmith began as a side project due to the lack of suitable feature flag solutions on GitHub and underscores that the decision to remain open-source influences all aspects of their development, including integrating with specialized analytics tools rather than building their own. The discussion also touches on the importance of understanding customer needs and maintaining a flexible, self-hosted platform that is not tied to any particular cloud provider. With a focus on gradually building their tool and community, Flagsmith aims to improve the developer experience by continually refining aspects such as deployment, load testing, and security, while also sharing valuable content for developers without heavy financial backing.

GitOps, when integrated with feature flags, allows teams to manage feature rollouts and changes within the familiar workflows of code development, ensuring transparency, consistency, and ease of rollback. By using tools like Terrateam alongside Terraform and Flagsmith, feature flags are treated as part of the infrastructure, with changes tracked, reviewed, and deployed through pull requests and CI/CD pipelines. This approach makes feature flag updates visible and predictable, aligning developers, QA, and product managers. Terrateam automates Terraform workflows, streamlining the process of applying and rolling back changes across different environments, thus minimizing deployment risks and maintaining workflow efficiency. By incorporating flag changes into the version-controlled codebase, teams can maintain an audit trail, manage environment-specific configurations, and facilitate canary deployments and feature deprecation, all while reducing operational overhead.

The text introduces the react-native-performance-monitor, an open-source tool designed to enhance the performance monitoring of React Native applications, and highlights its potential benefits for developers. This tool, available on npm, addresses the challenges of optimizing large React Native apps by providing real-time performance metrics, facilitating an objective assessment of code changes through immediate, A/B comparison-based feedback. It serves as a complement to the React Profiler, which, while useful, has limitations such as a slow feedback loop and overwhelming data output in complex applications. The performance monitor enables developers to establish baselines, test both component mounts and updates, and iteratively refine their code while observing the effects on performance. The tool's implementation involves a React Native component sending profile data to a WebSocket server, which then renders it in a graph through a web application, offering a visual representation of performance metrics. The author, having extensive experience with React Native since 2015, shares insights gained from using the tool, emphasizing the importance of measuring and documenting performance improvements to avoid regression and ensure that changes lead to meaningful enhancements.

The guide details the implementation of feature flags in Android applications using Kotlin, emphasizing the flexibility, risk reduction, and improved user experience they offer. Feature flags allow developers to enable or disable app features remotely without needing to release a new app version, facilitating adaptive changes based on user behavior and business needs. The tutorial uses Flagsmith, a feature flagging tool, to demonstrate the process of setting up a travel app with toggles for features like flight booking. It stresses the importance of caching to mitigate network latency, ensuring a responsive user experience by storing previously fetched flag values locally. The guide also provides step-by-step instructions for setting up the Flagsmith SDK, creating a Flagsmith key, and configuring Android Studio, and underscores the benefits of using a local cache to reduce network requests and improve app responsiveness.

Feature flags can enhance analytics by integrating A/B testing and experimentation into existing tools and workflows, offering more robust metrics and decision-making capabilities. While all-in-one feature flagging and testing solutions exist, using specialised tools like Flagsmith allows for more tailored and cost-effective analysis by integrating with existing analytics platforms. This approach avoids the pitfalls of introducing additional decision points and costs associated with full-suite solutions and enables teams to leverage their current infrastructure. Flagsmith exemplifies this strategy by providing a specialised feature flag tool that partners with analytics providers, allowing seamless data integration for A/B and multivariate testing. A practical example involves a fintech team using Flagsmith to adjust app modals for improved user feedback, demonstrating the effectiveness of combining feature flagging with a comprehensive analytics stack.

Flagsmith, a fully remote team with members worldwide, recently held their first off-site meeting in Amsterdam to foster better connections among colleagues and to understand each other beyond virtual interactions. The gathering proved highly beneficial, enhancing team alignment, accountability, and idea generation, with activities like 10-minute personal presentations allowing team members to share more about their lives. However, the team faced challenges, particularly in logistics such as acquiring visas, managing travel costs, and coordinating schedules across different time zones, which highlighted the complexities of organizing such an event. Despite these hurdles, the experience was deemed a success, with plans to improve future off-sites by conducting more thorough location research, potentially engaging a travel agent, setting clearer agendas, and addressing visa issues earlier. The team looks forward to future gatherings, eager to apply the lessons learned to enhance productivity and personal connections further.

Rabbit Care, a leading financial and insurance company in Thailand, transitioned from using GitFlow to trunk-based development with Flagsmith for feature flag management, enabling them to deploy multiple times daily. This shift, spearheaded by Senior Software Engineer Piyush Chauhan, significantly streamlined their workflow, reducing the need for overnight releases and extensive conflict resolution. The company previously faced challenges with large pull requests averaging 2,000 lines of code, which delayed delivery and required much effort to manage and merge. By adopting trunk-based development and feature flags, Rabbit Care improved their deployment process, allowing for continuous integration and more frequent releases with less downtime. The use of feature flags also provides flexibility in managing mobile app updates and mitigating serious issues swiftly, enhancing the overall efficiency and collaboration within teams.

Smartex, a company providing advanced tools for modern textile factories, utilizes Flagsmith for customer segmentation and staged rollouts to efficiently manage feature deployment with reduced risk. Jared Baribeau, Head of Software Architecture, explains how feature flags have enabled Smartex to streamline their release processes by allowing product teams to manage feature rollouts independently, without relying on engineering teams. This approach supports phased rollouts to early-adopter clients, facilitating continuous improvement and testing of complex hardware and software in various products like Smartex Core, a fabric inspection tool. As Smartex expands globally, they are focusing on maintaining efficient workflows and reducing release cycle times through improved testing processes and feature flag management, utilizing Flagsmith's intuitive interface and SDKs across their embedded devices and web applications.

Flagsmith, an open-source tool managed as a SaaS for enterprises, faced a challenge with vulnerabilities in their Docker image during an on-premise deployment for a client with stringent security standards. Initial analysis with the Clair tool revealed numerous vulnerabilities from outdated binary packages in the base layer, prompting a need for a more secure foundation. While considering alternatives, including Alpine Linux and changing the build toolchain, Flagsmith found a solution in Chainguard's Wolfi, which uses the familiar glibc C backend and offers necessary binary dependencies. Opting to pin the base layer version to the latest to ensure up-to-date binaries, they successfully tested and deployed the new Docker image, integrating Trivy security scanning and Docker Scout reporting for ongoing security monitoring. Future adjustments to their Docker build process will depend on evolving customer demands and potentially include moving to alternative build systems like Chainguard if required by enterprise security practices.

Gagan Trivedi, an engineer at Flagsmith, shares his experience of developing a Terraform provider for their open-source feature flagging tool, aiming to assist teams in automating CI/CD processes and managing feature flags within Terraform workflows. Trivedi highlights the growing adoption of Infrastructure as Code (IaC) practices, particularly with Terraform, which motivated Flagsmith to build this integration. Through customer discovery calls, they shaped the provider's initial design, allowing them to develop a minimum viable product (MVP) and a roadmap for future improvements. The process involved using the Terraform provider scaffolding framework and building a Golang library to interact with Flagsmith's API, focusing on GET and PUT methods for feature states. Trivedi explains that creating and deleting feature states is unnecessary, as they are automatically managed with the environment in Flagsmith. The article also encourages readers to use the provider available on the Terraform registry and stay updated on further developments aimed at enhancing infrastructure management through code.

This tutorial provides a comprehensive guide on using Elixir Feature Flags with Flagsmith, a tool that allows development teams to manage feature flags through a web dashboard or API without redeploying applications. The tutorial walks through a practical example of toggling email notifications on or off in an application, starting with setting up the Elixir environment, creating a mix project, and configuring Flagsmith with API keys. It includes instructions for installing dependencies, setting up a mailer using the Bamboo library, and scheduling notifications with the Quantum library. The guide explains how to control notifications via feature flags, test configurations, and deploy the application to a production environment using Gigalixir, while emphasizing secure management of API keys and other sensitive information through environment variables.

eFuse, a platform for connecting gamers with professional opportunities and esports scholarships, utilizes A/B and multivariate testing with Flagsmith to enhance user experience. Experiments are meticulously documented in Confluence, with design documents outlining the test's framework and potential influencing variables. User experience is controlled through feature flags in Flagsmith, segmenting users into test and control groups, primarily using React and React Native for mobile applications. Analytics are crucial, with data from experiments analyzed through Mixpanel, facilitated by an internal component that manages feature flags. A notable test in 2021 involved onboarding processes, initially showing no significant difference in user engagement between a guided onboarding and a control group. A subsequent multivariate test, which introduced a third group tasked with making a post, revealed that this action significantly increased user retention. Looking ahead, eFuse aims to integrate A/B testing into its core feature flagging process to ensure all features are evaluated upon launch, fostering an engineering culture centered around continuous experimentation and improvement.