Two screens, one abacus
Share a live abacus
Start a session, send the code, and whoever joins sees your beads move as you move them. Hand them control when you want them to try it themselves, and take it back with one tap.
Start a session
You will get a code to share. You stay in charge of who joins and who can move the beads.
or
Join a session
Got a code from a teacher or a parent? Enter it here.
The person who invited you can see every bead you move.
How it works
Three steps, no accounts
- 1
Start a session
Pick how many rods you want and start. You get a five-character code and a link to send — nothing to install and nobody to sign up.
- 2
Let them in
When someone enters your code you get asked before they see anything. Until you say yes, they cannot see the frame at all.
- 3
Show, then hand over
They watch your beads move in real time. Tap Allow control when you want them to try it, and take it back the moment you want the frame to yourself again.
Why watching beads move matters
Bead technique is a motor skill before it is an arithmetic one, and it is almost impossible to correct from a photograph. A learner who lowers the five bead with the wrong finger, or who clears a rod in two motions where one would do, looks exactly right in a still image and wrong the moment you watch them work. A live frame shows the motion, which is the part that actually needs fixing.
Who this is for
A tutor working with a student who is not in the room. A parent who learned on a physical soroban and wants to show a child what a proper finger movement looks like. A teacher taking two students back to back on the same link. The session needs no account on either side, so it works with whoever you are talking to right now.
Who can move the beads
You start with control and the other side starts watching. Hand control over when you want them to try something themselves, and take it back when you want to demonstrate again. Control is enforced on our server, not just hidden in the page, so a viewer cannot move your beads by fiddling with the browser.
What is stored
Nothing. A session lives in memory for as long as it runs and disappears when it ends — there is no recording, no transcript and no account to attach one to. The code stops working when the session finishes, and there are no names anywhere in it.