Simulator

sdk.remeet.video/simulator.html runs your app without a call: no account, no install, no second device.

What it shows

• Two copies of your app side by side — You and Anna. app.broadcast() from one arrives in the other, exactly like between two people in a meeting.
• Participants — the people in the simulated meeting.
• Meeting events — buttons that make things happen: Omar joins, Omar leaves, Anna speaks, Omar writes in the chat, Omar says something (captions).
• Permissions granted — tick or untick permissions to see how your app behaves when the person did not allow something.
• Bridge log — every message between your app and the «meeting», both ways.
• Toasts from app.notify() and badges from app.badges.set().

Open your app

Paste the address into the field and press Run the app, or pass it in the link:

https://sdk.remeet.video/simulator.html?url=https://your-site.example/panel.html
https://sdk.remeet.video/simulator.html?url=https://your-site.example/stage.html&surface=stage

surface is panel (default) or stage — what ReMeet.surface returns inside your app.

Develop on your computer

Browsers don't let a public site like sdk.remeet.video show pages from localhost in a frame. Two ways around it:

Run the simulator next to your app. The simulator is one file. Save simulator.html into your project folder, start any local server there (npx serve, Vite, Python's http.server) and open both from it:

http://localhost:5173/simulator.html?url=http://localhost:5173/panel.html

Or use an https tunnel (for example ngrok or cloudflared) and give the tunnel address to the online simulator.

What the simulator does not do

• There is no real video, audio or chat; events come from the buttons.
• You is the host, Anna is a member, Omar is a guest — try stage.open({ everyone: true }) from both copies to see the host check.
• app.stage.open() shows a toast instead of a stage. To work on your stage page, run it with &surface=stage.
• app.storage is kept in this browser's local storage, separately for You and Anna.
• The context token is a placeholder (simulator-token-…) and is not signed by ReMeet: test token checks on your server in a real meeting.