Feature flags are essential for effective feature release and management. Using them, we can control what features end users can see and which should remain hidden. Feature flagging allows developers to plan, launch and test new features remotely without editing code. While these benefits are fantastic, what about code testing? Having some methods in place for testing the integration of feature flags in our code can increase the likelihood of smooth feature integrations.
Choosing the right SaaS (Software as a Service) provider is a crucial decision for any organization. When evaluating potential vendors, it's essential to have a clear understanding of their security measures, service level agreements, and other factors that may impact your business.
Here are some key questions to help guide your evaluation process.
According to an article published by CNET, the growth of the gaming industry is expected to increase. Due to this, new game titles are on the rise as greater demands are placed on gaming companies to remain competitive by keeping their users engaged with new features and updates. With the proper feature flagging mechanism, new features and updates can be effectively managed and released to users.
In today's fast-paced world, the web development landscape is constantly evolving, with user expectations for fast and responsive applications driving innovation. The need for more modular, scalable, and maintainable architectures is more crucial than ever, as web applications are now required to be highly adaptable and feature-rich.
This has led to the rise of Microfrontends, an architectural approach that addresses the challenges faced by large frontend development teams working on monolithic frontend applications. Microfrontends have emerged as a solution to this challenge by breaking down these frontend monoliths into smaller, manageable components owned by cross-functional teams to facilitate the independent delivery of updates and new features.
Software development and delivery is a dynamic process that requires constant adaptation and frequent testing. Therefore, how can you ensure that your code is reliable and secure? Can you test new features without disrupting or compromising service performance? How can you enable your teams to innovate quickly and efficiently?
The answer is feature flags.
Releasing your digital product on the market is both an exciting and terrifying process. Whether you’ve created a mobile app or another type of software product, seeing it in the hands of real users is the ultimate achievement. But, simply building a wonderful product is not enough to ensure its long-term success. Over time, you’ll inevitably want to make changes and updates to your app.
But how can you be sure you’re making the right changes? It’s impossible to read your clients’ minds, but A/B testing might just be the next best thing. In this article, I’ll guide you through conducting an A/B test on an Android (Kotlin) application using ConfigCat’s feature flag management system and Amplitude.
Ever since the dawn of feature releases, feature flags have become the de facto standard for managing and controlling features in software applications. Many software development methodologies these days such as agile, are heavily focused on releasing continuous updates and features. In addition, a few companies have based their entire business around serving clients a cloud-based feature flagging solution. But in limited bandwidth situations or when you need to optimize the performance of your client-facing applications making API requests may not be ideal. This can be handled by implementing a process called caching with the help of a popular tool called Redis.
It can be time-consuming to create and manage the infrastructure that drives your software applications as they grow and become larger. Also, what about ongoing updates and releases of new features? Luckily, there is a solution to this problem in the form of a tool designed by Hashicorp called Terraform. This allows us to define our infrastructure in a central configuration file without having to create it on every provider platform we use.
While there may not be a one-size-fits-all solution for optimizing workflow and maximizing productivity, you can often put things in place to really up your productivity game. At ConfigCat, we understand this and strive to provide our customers with the essential integration tools to help automate their feature flagging workflow.
For this reason, we are thrilled to announce that ConfigCat now has an official integration with Zapier, a powerful automation tool. With this Zapier integration, you can now connect ConfigCat with over 5,000+ apps, unlocking a new level of automation for your feature flagging workflow. This allows you to make things happen on autopilot without ever having to touch them after the initial integration. And you know what's most interesting about this integration? No code is required! It's like having superpowers.
Can naming feature flags be hard?
Yes. Just like variables in programming, naming feature flags can get tricky if you don't follow a naming standard. When feature flags don't have good names, it can be difficult for people using them to remember what they do. In this article, we'll see a few naming conventions we can use for feature flags.