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.
At the beginning of this year, Andrew Reeman from Control Point was kind enough to join our conversation about what we actually do differently at ConfigCat, or at least interesting enough so that it only makes sense for our clients to stick with us and for those who didn’t try our approach and products, to do so.
When growing any product or service, it’s to constantly gather feedback from your user base. And I mean constantly, else you risk losing focus from your real clients’ needs and priorities.
To drive this point home, I figured that the best course of action was to collect some valuable insight from a third-party. Joseph Harris, who works at Eucalyptus was kind enough to take the time and offer just that.
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.
Focusing on frontend applications, we introduced sensitive text comparators to make sure sensitive info (like email address, username) is kept hidden in targeting rules.
The main idea about our pricing is that our prices are fixed, deterministic and there are no hidden fees. Also we offer a forever free plan without requiring any commitment or credit card information. All features are available in all plans - even the free - helping the evaluation process of our customers.
There is a way to stream feature flag and configuration changes to the clients right when they happen. In some cases ConfigCat's pull based architecture does not completely satisfies the requirements when microservices need the latest values instantly, or mobile apps where polling sometimes is a battery consuming anti-pattern.
Your application subscribes to a PubNub channel to get updates about changes. And use ConfigCat Webhooks to notify PubNub when a feature flag value gets updated.
Sample application in Node.js.
Show us your most innovative idea in using feature flags with ConfigCat, and we’ll send you a pack of gifts including your choice of video or music streaming worth $100, or books worth $150 + a pack of ConfigCat and GitHub swag + a commercial ConfigCat subscription.
We'd like to make ConfigCat available for as many users as possible. Our SDKs are available in multiple languages. But still lots of our users missed Ruby support in ConfigCat:
Finally we decided to create a standalone Ruby SDK.
Ruby is an interpreted language. It's very similar to Python and we already have an SDK written in Python. Taking advantage of this, the first idea was that we simply convert our Python code to Ruby and everything will be just fine.
Students should have access to the highest-quality education available. So we partnered with @GitHubEducation and joined the GitHub Student Developer Pack.
