Alternatives
Products that do what TabConnect does
Share one browser tab. Your viewer installs nothing.
- 11F
I wanted to show you something I was hacking on for the last few weeks. I tired of sharing screen via Google Meet with 1-hour limitation, with Zoom and 40-minute limitation, etc. With paid Slack subscription. And often times I just needed to screenshare with no audio. So I ended up with my own solution - no registration, low memory, low CPU, low tek 1 fps encrypted screen sharing. Currently sharing only the main screen (good for laptop users). It's very raw in terms of infrastructure, since I'm not counting bytes (yikes!), everything works on my own dedicated server. But the service itself…
2024 · 1fps.video
- 2

- 3XT
2024 · github.com
- 4FU
2012 · screenleap.com
- 5

- 6

- 7

- 8SS
Seeing all the hype around Bolt.new, I decided to give it a try, and within just 30 minutes, I built a fully functional web app for screen sharing. How It Works: - One user opens a room and receives a unique code. - Participants join by simply entering the code to view the shared screen. After that initial build, I moved the project to Cursor to continue iterating and enhancing its features. Github: https://github.com/tonghohin/screen-sharing Demo: https://share-your-screen.vercel.app
2024 · github.com
- 9

- 10

- 11

- 12IS
Two browser windows (acting as socket clients) communicate their: - Screen dimensions - (screen.width, screen.height) - Window dimensions - (window.innerWidth, window.innerHeight) - Window X/Y position - (window.screenX, window.screenY) ...or whichever calculation works best for you. The original work by Bjorn Staal https://twitter.com/_nonfigurativ_/status/172732259457002734 used localStorage, but I found sockets more fun, because if tweaked a bit, this can be shared with friends. Here's a demo of how it works and the codebase:…
2023 · github.com
- 13

- 14

- 15

- 16

- 17TS
Hi HN, I've developed a Chrome extension that provides tab-sharing functionality without the use of screencasting. The product works by keeping the DOM on a mirrored page in sync with the driver's display. This is achieved by listening for DOM events on the driver's page and relaying them to the mirror as display instructions (e.g. add/remove a node, change attribute, scroll page, etc.). While the mirrored page gets the DOM structure directly from their peer via a WebRTC connection, the bulk of the resources and visible content (e.g. images, fonts, stylesheets, etc.) are downloaded…
2019
- 18TS
2014 · nutty.io
- 19

- 20

- 21

- 22

- 23

- 24

Ranked by how close each launch is in meaning, then by votes. Refine with a description →