Feature flags have made it easier than ever to continuously test and integrate new features in our applications with confidence, even while in a production environment without having to worry about deployment risks like downtimes or bugs that could greatly impact the experience of the entire user base.
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.
Building a modern application often involves building it as a microservice, which provides developers with more flexibility and agility in terms of deployment options. However, deployment can either be a joy or a nightmare, depending on the strategy used, whether it's deploying microservices, testing new features, updating a business logic, or releasing a new version entirely? With every code change pushed, comes the risk of potential failures, which could be as a result of bad code quality or unexpected bugs, and this can potentially disrupt the user's experience.
Hence, picking an efficient deployment strategy is key to mitigating these deployment risks and not having to constantly disrupt your user’s experience by going into downtimes or completely having to go offline whenever there is something to be deployed.
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!
Bugfender is a remote log aggregator that allows front-end and mobile developers to view their entire crash and issue records from any location. It works on iOS, Android and web applications and provides crucial information at all three development stages (development, testing and production).
By harnessing Bugfender, ConfigCat users can provide even more targeted support by identifying bugs in their individual features as well as overarching trends.
Good code is one of the most valuable commodities in technology. Code quality can affect everything from code execution time and application load times, to how easy it is to maintain, read, and debug.
It can also play a significant role in your company's competitiveness. If your competitors are spending more time fixing bugs than adding features, then they're losing ground to you.
Two Technical terms that can save your project!
Code Hygiene goes hand in hand with avoiding Tech Debt and these two should be THE backbone of your company’s philosophy!
Separating your customers into distinct segments will help your product in all sorts of ways. It can help you track the usage of your app in a more meaningful and granular way. It can also reveal how specifically different segments behave differently, which will help you prioritize future feature development as well as focus your marketing efforts.
Let's say you've just built a new feature, but it's not ready for a full release just yet. So, you decide to test it with a small group of people.
You can go about it in two ways - deterministic or random. The first way lets you specify people by name, email, company or any other attribute you know about them. The latter uses fancy math and probability to randomly assign users into groups. Let's see how you'd accomplish both using ConfigCat.