How Ramus works

Ramus brings every pull request to life by building the real Android app and making it instantly available for review. Here's what happens between opening a PR and using the app, step by step.

1. Open a pull request

Install the Ramus GitHub App on a repository and enable previews for it. From then on, Ramus listens for pull request events — opening a PR or pushing a new commit kicks off the pipeline automatically. No CI configuration, no workflow files.

2. Ramus builds your app

Ramus clones the PR's commit into a clean, isolated build environment and builds an installable APK. Kotlin/Java with Gradle, Jetpack Compose, Expo, and Flutter projects are detected and built automatically — see Builds for details.

3. A comment stays honest

One self-updating comment on the pull request tracks the whole story: queued, building, ready — or the failure and its log. There is exactly one comment per PR, and it is rebuilt from the current state every time something changes, so it never drifts.

4. Review on a live device

When the build is ready, the comment links to a live preview: the app, installed in a fresh private Android emulator, streamed to your browser. Tap, scroll, type, take screenshots, restart — no local setup, no emulator install, no APK sideloading. See Preview sessions.

5. Merge and cleanup

When the pull request is merged or closed, Ramus tears the preview down and cleans up build artifacts automatically. Preview links expire on their own; nothing lingers.

That's it. Every supported pull request becomes a real, testable app in minutes. No more "works on my machine."

What Ramus is not

Ramus does not replace your review. Discussion, approval, and the merge decision stay on GitHub — Ramus adds the running app to them. Today it is Android only, builds same-repository pull requests (fork PRs are not built yet), and runs previews only in repositories where you enable it.