What we build with it
Ruby shows up in our work as build and release tooling rather than as product code. Fastlane is a Ruby tool, so its lanes, custom actions and plugins are Ruby, and so is the surrounding CI glue that drives signing, versioning and store uploads.
That is real code and it is worth treating as such — release automation that nobody can read is release automation nobody can fix on the day it breaks.
Where we have shipped it
The white-label cashback platform has the most of it. Producing 15+ branded apps from one Flutter codebase means each app needs its own signing identity, bundle identifier, assets and store listing, and the lanes that make adding a new brand a config change rather than a day of manual work are Ruby.
When we recommend it
For the mobile release pipeline, where Fastlane is the standard and Ruby comes with it. We would not introduce Ruby to a project for any other reason.
For product backends we use Go, Python or Rust — Rails is a capable framework, but it is not where our team's depth is, and we would rather hand you a backend written by people who work in that language every day.
