Share a running app
A share link opens your Android app in anyone's browser, on a phone or a laptop, with no install and no account. Each person can get their own device with your app, or everyone can join the device you are on. From any link they can send you a note with a screenshot, and you can reply. Sharing is on every plan; shared devices run on your minutes.
Two kinds of link
| Their own device | Join this device | |
|---|---|---|
| What they open | A fresh device with your app, for them alone | The device you are on, live, with everyone else on it |
| How many at once | One device per person, up to your plan's devices | You + 3 people |
| What they can do | Use, or Use + install | Watch, Use, or Use + install |
| Good for | A client, tester or reviewer trying your app in their own time | Showing something live, or watching your coding agent work |
Their own device is the default for an app you uploaded. It needs one of your uploaded apps, so a blank device offers only Join this device. On an app's page you make Their own device links; to have people join a device, share it from the running device.
Create a link
On a running device or on your app's page, choose Share. Then:
- Choose Their own device or Join this device.
- Under For, add a label if you like, such as "Acme review" or "QA, Dana". The person sees it.
- Choose what they can do, which build the link opens and how long it lasts.
- Choose Create link, then copy the link and send it however you like.
Your agent can create links too: ramus session share --own in the CLI, or android_share_session with own_device over MCP. Without them, the link joins the agent's device; --permission watch, or permission over MCP, makes it view-only. The link every ramus session start makes is Watch, and it does not show your name; open your own device page to control that device. A new link leaves your other links working.
Their own device
Each browser that opens the link gets its own fresh device with your app, which starts as soon as the page opens. No one else on the link sees it. If the person comes back in the same browser while their device is running, they return to it; after it has ended, the link starts a fresh one.
- It runs on your account. Their device uses your minutes and, while it is open, one of your plan's devices: 1 on Free, 1 on Hobby and 2 on Pro. See Plans and minutes.
- When all your devices are busy, the next person's page waits and opens as soon as one is free.
- You can see it. The Share panel lists who opened the link and whether they are on their device now. Choose Open to open their device yourself.
- A person's turn is 30 minutes. Their device ends then, in use or not. They can start another while the link lasts.
- Your own device comes first. If you start a session while every device is in use and someone holds one through a link, the one that has run longest ends, and that person's page waits for a free device. Sharing never blocks you.
- It ends like any device: after 10 minutes without input, when its 30 minutes are up, or when you revoke the link.
Join this device
Everyone who opens the link joins the one device it was made on, live and together. You + 3 people can be on it at once, and each person appears by name with their own cursor. One of the four places is always yours and your agent's: a link's fourth person is refused, and you still get in. When the link's places are taken, the next person sees a message and can try again once someone leaves; no one is disconnected. Two tabs in one browser take two spots.
or coding agent
Same device state.
Can watch and control.
| Permission | They can |
|---|---|
| Watch | See the screen. They cannot tap or type. |
| Use | Tap, type, swipe and scroll, like you. |
| Use + install | Use the app and install a new APK on the device. This is the default. |
When the device ends, a link that has not expired can start a fresh one with the same build, subject to capacity and relaunch limits. A fresh device does not restore what anyone did on the previous one.
Which build it opens
- Latest build opens the newest build of the app. When you upload a fix, the link you already sent opens it, so there is nothing to resend. Someone who is on their own device when a new build arrives is offered it; their device is not replaced without asking. On a Join this device link there are two exceptions: a Watch link joins the device that is already running, and when your plan has no free device the link opens the running build instead.
- This build (Their own device) always opens the build the link was made on.
- This device (Join this device) opens this one running device and its current state. When the device ends, the link offers a fresh device with the same build.
Feedback
Anyone with a link can send you a note, whatever the link lets them do.
To send one, the person chooses Send feedback, which carries your name, beside the device. The screen is captured as a screenshot; they tap it to drop a pin on what they mean, write what you should know and choose Send note. A note carries:
- the screenshot and the pin;
- the app and the build it was sent from;
- the last 200 lines of the device log;
- their recent taps, swipes and keys. Typing on a keyboard is recorded only as a number of characters, never the text. Taps are not recorded while the phone’s on-screen keyboard is open, so a password tapped on it can't be read back, and this list can be empty.
They can untick Include the device log and my recent taps to send only the note and the screenshot. The notes they sent stay on their link, with your reply or a mark that you resolved it.
Notes appear in the Feedback section of your app's page, newest first, and the Share panel shows each link's open notes and each person's notes. For each note you can see the screenshot with its pin, the build, the log and their steps, then:
- Reply: they see your reply on their link.
- Resolve, or Reopen a resolved note.
- Copy for your agent: the note, their steps and the log as text to paste.
- Delete: the note, its screenshot and its log are removed, and it disappears for the person who sent it too.
Notes stay after the device ends and after the link expires or is revoked, for 30 days. Then they and their screenshots are deleted.
Your coding agent can work through notes itself. Over MCP, android_list_feedback lists them, android_get_feedback returns one with its screenshot and log, and android_resolve_feedback resolves it and can leave a reply. From a shell, use ramus feedback. A typical loop: your agent reads the note and tells you what it found, you say to go ahead, it fixes the bug, uploads the new build and resolves the note with a reply. It asks before it changes code because of a note. A latest-build link the person already has then opens the fix.
How long a link lasts
Choose from 1 hour to 7 days; a link lasts 3 days unless you choose. The expiry is when the link stops working, not a promise that a device keeps running until then: a device still ends after its idle timeout, and the link can start a fresh one.
Copy or revoke a link
Every link you create stays in the Share panel with its label, its kind, who opened it and its notes. Copy a link again from there at any time, or revoke it: the link stops opening at once, and anyone already on the device through it is disconnected within about 15 seconds. Revoking a Their own device link also ends the devices it started. Ending a device does not revoke its links.
Share links work like keys: anyone who has one can use what it opens, so send each link only to the person it is for. A link to a pull request preview also stops working when its creator can no longer read the repository. See Security.