Let's play with a hypothetical scenario where you've built a Kotlin-based mobile application, and you'd like to customize the overall user experience based on specified criteria. You've got a perfect idea, but then this question pops up everywhere: Now what? Folks, allow me to introduce you to the concept of feature flags in Kotlin.
In this article, I’m going to be demonstrating how to integrate ConfigCat's Feature Flag service in React. I will build a simple, pretty easy-to-understand application that simulates a race between three cars. Let’s get started!
Thanks to the latest CI/CD tools and services, software companies can now deliver multiple releases in a week. Over the release process, it's expected that DevOps professionals keep their eyes on the monitoring dashboard and roll-back the deployment on the first suspicion. Since the use of feature flags gets more and more traction, it seems like a good idea to connect those releases and the monitoring tools.
If you're a software reseller you are allowed to buy a ConfigCat subscription for your client. You are allowed to resell one subscription to one client only. Of course, you are allowed to resell more subscriptions to the same client.
Here is how to do it.
If you run into any problem, just drop us an email at [email protected].
As feature flags are getting popular, an ever-growing number of developers are facing the challenges associated with them.
No matter if you implement your own feature flag library, or choose a hosted feature flag service like ConfigCat, chances are high you want to use your feature flags in your frontend and in your backend services as well.
If your feature flags can be toggled on a central feature flag dashboard, such as
Use Feature Flags, and you do not need to worry about the ambiguous Apple App Store review. Also, you can forget about the release trains or the good old days when PMs are running around in the office with flame-throwers.
