Being so busy in between releasing new features and achieving significant milestones, we tend to forget how much we've got done up until that point. As such, our active customers have enjoyed our product, but they also continue to find greater value in it as their subscriptions grow.
We're proudly announcing our 16th SDK release! ConfigCat's C++ SDK is now generally available. This SDK is a native C++ implementation of ConfigCat's feature flag management service. It is designed to be lightweight, easy to use, and easy to integrate into your C++ projects.
When you take your software products offline to add new features, users can become frustrated, especially if their livelihood depends on it. With a new feature, there is always the risk of introducing unanticipated bugs. By incorporating feature flagging into our software release workflow, we can prevent and even lessen these situations.
The ability to make good decisions is often the leading factor in the success of a business. Yet, it is becoming increasingly difficult for companies to decide on what ideas to develop and content to optimize for users with certainty that it will perform as predicted.
Feature flagging is a vital technique that enables businesses to perform controlled A/B test experiments to gauge and analyze the impact of their decisions. A/B testing can effectively improve a business's overall performance and boost conversion rates by comparing and contrasting multiple implementations based on their performance with real users.
React Native is a framework created by Facebook that simplifies development of cross-platform mobile applications. In a nutshell, React Native code is automatically translated to native code for both Android and iOS. It's no wonder that this framework is becoming increasingly popular among developers. In this article, we’re going to explore how to use feature flags in this environment so you have all the tools necessary for great mobile development.
Most software features are designed and tested in-house before making their way into the hands of users. While this is somewhat of a standard approach in feature deployments, it may cause user experience issues. This is because the majority of end users are not tech-savvy and aren't thinking the way engineers do.
Adopting an A/B testing approach prior to making a final feature deployment decision can prevent or lessen the risk of interfering and affecting user experience. Features can be tested and released to a subset of end users initially where the current metrics can be recorded and compared to a previous benchmark. As a result, developers may choose to improve or cancel the feature altogether without the risk of blindly affecting the entire user base.
Our customers are at the heart of everything we do at ConfigCat. We take pride in knowing customer satisfaction is our top priority because we know that many of our competitors do not place the same value on customer experience as we do.
You asked. We listened!
We're excited to announce that ConfigCat now has an official React SDK.🥳🎉 The React SDK has been a highly requested feature by our customers, and we're proud to knock it off our checklist. The React SDK provides customers with a more modern, first-class React integration support when integrating ConfigCat with their React applications. We hope our customers share our enthusiasm for it.
It has become very rare to develop software that does not require regular updates and patches. In fact, it's now the norm with the rise of agile software development. As a result, there are so many new updates to manage across our code making feature rollouts tedious and complex. Hence, turning towards a good feature flagging solution always saves the day.
Scenario: You’ve thought up a small change for your app. You write and test the code, and everything looks good. As you’re about to push it into production, you stop and ask yourself, “Will the users like this?”
You start having doubts, that maybe the idea isn’t as good as you previously thought. Still, you continue to have a strong feeling that it’ll make your app better.
One solution to this dilemma is to gradually introduce the change to a portion of users and track its impact on them. This is called A/B testing, and it’s a simple, low-risk way of letting your users pick which variant yields better results.
As the world continues to change rapidly, software applications must be constantly updated. This forces software developers to release new features quickly. It is, however, a challenge to keep bugs and other software issues to a minimum. I have always found that feature flagging saves the day in these situations.
