Have you ever wanted to add a new feature to your iOS app with the option to roll it back quickly if things go wrong? Feature flags can help! With feature flags, you can deliver new features remotely with the click of a button without having to republish your app.
Using Feature Flags in a Preact Application
Sending your code out into the world can be a nerve-wracking experience. Regardless of how much testing you do beforehand, you’re never quite sure if everything will work according to plan. Even if it’s the case, during an applications life-time, you’ll need to redeploy your code many times. Code redeployment means time, money and a lot of hassle.
Fortunately, feature flags are useful tools that can help reduce the need for code redeployment as well as enable you to test your changes in production without affecting the end-user. In this article, I’ll show you how to make use of feature toggles in a React-like framework. So…
How to A/B test your Python application
Will showing the number of book copies sold on my website encourage more people to buy it? To answer this question confidently, I can rely upon A/B testing for guidance. This method of testing allows us to evaluate two versions of a website or app by releasing them to different user segments to see which one performs better.
Using Feature Flags to gradually roll out new features
Software development is a really challenging endeavor. A lot of time and energy has to go into making sure that customers like what you're building for them.
Many people make the mistake of thinking that product development mainly consists of coding. Developing a product (ideally) needs specialists, managers, tactics, and various tools. A good idea can indeed go a long way, but if you want to give your product the highest possible chance to penetrate the market, then you need to allocate all possible resources that you have available to throw at it.
This implies that you should work smarter, not harder. Slow traditional deployments often cost more and take up a ridiculous amount of time. Thankfully, integrating Feature Flags into your deployment strategy can speed up this process.
How to Implement and use Feature Flags in a Svelte Application?
When deploying code, one of the best ways to ensure it's high quality, meets user or business requirements, and works as it should is by feature flagging it. Feature flags are a great way to control the release of new code or features in your software, as feature flags make it possible to test new code on specific users or a group of users before releasing them to everyone.
Feature flagging allows you and your team to easily experiment with new features or make changes to existing ones without deploying a new software version. Furthermore, feature flags make it possible for you and your team to seamlessly execute trunk-based development by facilitating continuous deployments and ensuring code integration reliability.
This guide will cover how we can use feature flags to introduce new features in a Svelte application.
An In-depth Look into User Targeting
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's feature flag services. For context, ConfigCat is a developer-centric feature flag service with unlimited team size, awesome support, and a reasonable price tag.
Using Amplitude in a VueJS A/B testing scenario
When it comes to releasing new features or changes in software, we can rely on A/B testing for making informed decisions. In this type of testing, we can measure the impact of the new change or feature on users before deciding to deploy it. By doing so, we can carefully roll out updates without negatively impacting user experience.
Automating Feature Flags using ConfigCat’s Public API + Cron + cURL
Feature flags are a great way to control the release of new features in your software. They allow you to easily turn new features on or off without redeploying your code.
However, when implementing a feature flag in an application, we may want to customize its management after the initial release, i.e., schedule an incremental release/delivery strategy that is carried out automatically or schedule future changes to a flag's targeting rule that can take effect at specific time intervals.
- Activate a flag’s config by date and time. For instance, release a feature at noon on a Sunday afternoon.
- Gradually increase the discount value of an ongoing promotion at specific times of weekdays.
- Enable a feature only on weekends or on weekdays.
- Three days from today, turn on a feature for internal testing and enable it for public use a week later.
How to implement A/B testing in Ionic
The world population continues to grow, and so does the number of house pets. While we all hope most of them have a good quality of life, some don't have a home. To combat this, we can make an animal care app. In this blog post, the app's objective is to increase the pet adoption rate. We will change the color of our call-to-action button and measure the click-through rate of each button version using A/B testing.
How to build a remote light switch with Raspberry Pi and Feature Flags
Got some free time on your hands? Got you covered!
I'm going to show you a more peculiar way of using feature flags. Feature flags enable non-developers to switch on and off application features or change software configuration.
Following this step-by-step tutorial, you'll build a remote light switch using a Raspberry Pi and ConfigCat’s feature flag tools in no time. Let’s get started!