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 the context of SaaS applications, having a tool that allows you to control different features and flag certain users is critical, given the uniqueness of their needs and the instability of new releases.
This is where the ConfigCat Elixir SDK's tale begins. This is the simplified narrative of a great open-source SDK, driven by highly-professional folks from three different companies, as told by one of its creators.
We'd like to make ConfigCat avaliable for as many users as possible. Our SDKs are avalible in multiple languages. But still lots of our users missed Ruby support in ConfigCat:
"Does configcat have Ruby sdk??"
"So I am sad you don’t have a ruby client I can see."
"Are you plannig to support ruby?"
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.