Devolic is a small, senior consultancy built around one idea: business logic and interface should be written once and run everywhere. We do not take over codebases. We guide the architecture decisions, plan the migration off parallel Android, iOS, and Flutter codebases, and help teams modernise how they work, including where Claude and Codex genuinely belong in review and refactoring. When the ecosystem did not reach a platform we needed, we extended it ourselves and open-sourced the result.
3
18+
6
70%+
Transparency
We believe in a culture of transparency and communication, showing you where the cost goes in your project and explaining the logic behind each item.
Our Mission
Devolic exists to make one Kotlin codebase enough, and to leave your team able to run it without us. Teams should design a feature once and see it land on every screen their users own, without paying for the same work four times or handing their product to an agency to do it.
Devolic is owner-operated and partner-led. Surit runs the company; Bilal and Sajid are partners who each lead an engineering practice. You work directly with them, not with an account manager who forwards your questions on.
Founder & Managing Partner
Surit founded Devolic and runs the business end to end: client relationships, scoping, and keeping the engineering team pointed at work that moves the product. A decade in the lab and the technical sale got him here, from polymer QC at Sasol through analytical instruments and industrial materials.
LinkedIn →
Partner, Full-Stack, Cloud & DevOps
Bilal leads the backend and web side of every engagement: the Node and Express APIs, the Next.js web apps and dashboards, and the cloud infrastructure our multiplatform apps talk to. He sizes the deployment to the team that has to run it, from Dokploy or Docker Swarm up to Kubernetes with Argo CD. On AWS or Hetzner, with GitHub Actions behind it, a release is a pipeline run rather than a release-day scramble.
LinkedIn →
Partner, Technical Lead for Kotlin & Compose Multiplatform
Sajid has spent ten years on cross-platform TV and mobile apps, and is the engineer who brought Compose Multiplatform to Apple TV before JetBrains supported it. He leads our KMP architecture and maintains our open-source EPG, player, and compose-tvos libraries. The guide batches and lazy-loads 10,000+ channels, and the player stack runs live HLS and DASH with DVR and adaptive bitrate.
LinkedIn →Sajid and Bilal each lead a practice. When JetBrains shipped no tvOS target, Sajid built one rather than talk us out of the platform, and that is the standard both practices work to. They back the advisory work rather than replace yours: building the spikes that prove a recommendation before you commit to it, reviewing pull requests while the new conventions are setting, and pairing on the hard parts. Your engineers still write the production code, which is the whole point.
Led by Sajid Ali
The Kotlin and Compose Multiplatform practice. They are the engineers who prove a recommendation before you act on it: building the spike that shows whether a module really can be shared, reviewing your pull requests while the new conventions are setting, and pairing on the screens nobody wants to take first.
Led by Bilal Hadid
The practice that covers everything a multiplatform app talks to. A shared client codebase usually surfaces questions on the server side and in the release pipeline, and this is the team that answers them: proving the API and infrastructure side of a migration, and getting one build onto every store without a release-day scramble.