Review the pull request in a running app.
Ramus builds your Android pull request and posts a preview link. Open the app in your browser and try the change before merging.
Sign in with GitHub, select repositories, then enable automatic PR previews.
The sample runs a demo app. No account needed.
Ramus · Preview ready
The APK has built. Open the preview to try the change.
Ready for review
Review the app alongside the diff.
Put the running app beside the code.
Give engineers, QA, and design reviewers a way to check the change themselves. The PR comment tracks the build and links to the preview when it is ready.
Choose your repositories
Sign in with GitHub and install the Ramus App for selected repositories. Enable Automatic PR previews in each repository you want to build.
Open a supported PR
Ramus detects the project and builds an APK. A new commit triggers a new build, with progress and failures shown on the PR.
Try it before merging
Open a ready preview to start the app in your browser. Reviewers can test the flow without building the branch locally.
Built for your Android project.
Kotlin, Java, Jetpack Compose, Expo, React Native, and Flutter. Ramus detects supported layouts and builds the Android APK. For monorepos, set the app directory in ramus.toml.
Automatic previews support same-repository PRs. Fork PRs are not built. Private PR access requires GitHub sign-in and repository authorization.
Before you start.
Does installing the App enable every repository?
No. You choose which repositories the GitHub App can access, then enable Automatic PR previews in Ramus for each repository you want to build.
Which projects are supported?
Ramus detects Expo, React Native, Flutter, and Gradle-based Kotlin, Java, or Compose apps. The project must produce an installable APK. Monorepos can select an app directory in ramus.toml.
Who can open a private PR preview?
Standard PR previews require GitHub sign-in and repository authorization. A deliberately created watch link is separate: anyone holding that link can control its shared device.
Are fork pull requests supported?
Not currently. Automatic builds support same-repository pull requests in repositories where previews are enabled.
What happens on new commits or PR closure?
A new commit triggers a new build. Closing or merging the PR cancels unfinished builds, expires its ready previews, and ends their sessions. Stored artifact deletion follows a separate retention policy.
What if my build needs custom setup?
Check the build guide for detection, supported defaults, and ramus.toml. Private dependencies, signing, product flavors, or toolchain requirements may need project changes. A successful local build does not guarantee a hosted build will succeed.
Make the next review hands-on.
Sign in with GitHub, select repositories, then enable automatic PR previews.