Rohan SoniAuthor of the Inspired Entertainment case studyGoogle
Integration team. Java Spring Boot adapters for betting-operator wallet APIs. Gemini CLI, succeeded by Antigravity CLI.
Google Developer forums (Google case study), published Read the case study (opens Google Developer forums (Google case study) in a new tab)
Observation
Inspired Entertainment shrank each payment-adapter build to a week with Gemini CLI, and now points developers to Antigravity CLI.
- Takeaway
- Start the agent on one repetitive, documented integration with written guidelines, and count developer days per unit of work, as this team did.
- What happened
- Each new betting operator, such as DraftKings or Entain, needed a custom Java Spring Boot adapter that took a five-person scrum team 6 to 8 weeks. Developers now give the CLI the operator's API documentation and the company's markdown guidelines, and it writes the adapter. Google's case study reports builds down to one week, manual work from 40 dev days to 5, and two people per integration, down from five. The team recommends Antigravity CLI for new work.
- Vendor case study
- Customer-reported figures
- Written by Google with Inspired's CTO
Deployment details
Integration team. Java Spring Boot adapters for betting-operator wallet APIs. Gemini CLI, succeeded by Antigravity CLI.
- Vendor case study
- Customer-reported figures
- Written by Google with Inspired's CTO
- Team
- Inspired Entertainment integration team, now 1 developer and 1 QA per integration
- Workload
- Wallet adapters for betting operators, plus a Java 8 to Java 25 upgrade
- Product version
- Gemini CLI, now Antigravity CLI
- Measurement
- Dev days per integration, 40 to 5; build time, 6 to 8 weeks to 1 week