Powered by the Revyl platform and Grok's models, Studocu's Cursor Cloud Agents now build and verify mobile changes end to end. PRs that took two days now merge in hours, and designers and PMs are joining in.
Studocu is an AI-powered study platform that turns student-shared course materials into personalized summaries, quizzes and mock exams, helping 35 million students study every month across 192 countries. Rafael Pato, Director of Technology, wants everyone at the company working with agents. Not just engineers.
“I want to get to a place where non-technical people don’t have to prompt anything. They can just throw something at an agent, and the agent will figure it out.”
Rafael Pato, Director of Technology, Studocu Studocu started moving towards Cloud Agents with its mobile app, the youngest codebase and the platform where the team always tries new things first.
Cursor Cloud Agents could write mobile code, but they couldn’t verify it
A mobile change isn’t done when it compiles. It’s done when the screen works, and you only know that by building the app and looking at it on a device. Cursor Cloud Agents couldn’t do either. So mobile work kept going back to laptops, and agent PRs needed rounds of back-and-forth.
“Cloud agents were always able to do stuff, but they were never able to run the app and be like, okay, this is actually doing what I wanted it to do. … I wanted to one-shot, as close as possible, what I wanted done.”
Rafael Pato, Studocu One pipeline: Cursor writes it, Revyl proves it
A bug gets filed in Linear and assigned to Cursor. A Cursor cloud agent starts a Revyl session, creates a build and fixes the bug on a cloud iOS or Android device, checking its work with hot reload before it opens a PR.
“Linear Agent created an issue, assigned it to Cursor, and it immediately started the Revyl dev loop… It’s kind of crazy that you now have a machine testing swipe gestures on your app in the cloud.”
Rafael Pato, Studocu Once the PR is open, Revyl reads its description and the linked Linear issue, runs the change on a device and posts proof on the PR. That proof is now the feature of Revyl Studocu uses most.
Atlas is bringing designers and product people into the process
Every interaction Revyl captures, from the agent dev loop, PR checks and manual sessions, goes into Atlas. The result is an always up-to-date source of truth for what the app actually looks like, down to every screen and variant.
“Atlas is the feature where people understand better what Revyl is for. The non-technical people. Designers, particularly, are very excited about it.”
Rafael Pato, Studocu Atlas shows designers and engineering managers the product the way users see it, including screens nobody remembered building. They’ve started asking for access.
Rafael wants to go further. He’s pushing designers to prototype directly in Cursor with Revyl instead of Figma, so they work on the real app and not a mock that drifts away from it. It’s early, but that’s the direction. See the screen, point at what should change, hand it to Cursor Cloud Agents.
“Everyone is fighting to be the context layer of every company, and everyone is working with text. The future is working with navigation, images, and how things actually work. It’s what the end user sees, not what a product manager says that page is about.”
Rafael Pato, Studocu