This resonates with me, and is definitely why I loved Screenhero so much, it felt VERY fast, and visually looked crisp. Even the initial connection speed was fast, while Slack takes about 3–8 seconds to connect. And also why I was so disappointed with Slack's product, now it's back to the same level as Google Hangouts.
It's surprising that having the same lead, and access to the same source code, that the product was unable to achieve the same level of quality & performance. What would you say the culprit is? And if I may lead the question... Bureaucracy inside Slack? Managing a new team? Having to rewrite on presumably a new language & software stack? Rushing to meet deadlines?
Anyways, awesome to see your back at it again, and that you have such care about latency, people do notice & care!
Screen’s goal is to support remote work of any kind — including engineering & pair programming, for sure, but extending to many other uses cases, such as creative review, education, and beyond. And yes, I agree competition is good! :)
Curious: I assume you can't just sell your company and rebuild it in most cases. Was there an embargo on the amount of time before you could build this?
I would absolutely pay for any open source competitor to this type of product, preferably one that integrated with Jitsi (which itself is open source). Fool me once.
But to echo other comments, you really need to change the name.
Question for clarity sake, have I read this properly that you all still are with Slack, does this mean Screen.so is "A Slack Company" or just leveraging that relationship for tightly coupled/efficient integration as a wholly separate company?
Thanks!
Love that it is still blazing fast. Love that awesome features like multi cursor are still very much a thing.
Congrats on the re-launch!
Are you able to share further technical details on what you've had to do to get the speed gains you're describing?
I was the co-founder and CEO of Screenhero, and after its acquisition by Slack in 2015, I led the team that built Slack Calls (voice, video and screen sharing in Slack), and left Slack in 2018.
Today, we (myself and another engineer) are launching Screen, which is in many ways a successor to Screenhero. Our goal is to help you work with others like you’re in the same room.
Like Screenhero, it supports low-latency screen sharing with multi-mouse control. How low? It has the lowest screen sharing latency of any product we’ve tested: 30-50ms best-case end-to-end latency between screen capture and render, vs. 100ms-150ms in regular WebRTC. This means it’s great for remote pair programming, which was Screenhero’s biggest use case.
We have voice, video, multiplayer drawing and control, and ephemeral messaging, and we integrate with GCal and Slack.
We have native apps for Mac, Windows, and Linux (Screenhero’s top-requested feature was Linux support). We use custom native code to make multiplayer control work, and a heavily-modified custom fork of Electron to minimize latency. It's WebRTC-compliant, so you can share meeting links that anyone can join with a WebRTC-compliant desktop or mobile browser — no download required. Daily.co is our primary WebRTC-infrastructure provider (they’ve been amazing to work with!).
We're hoping Screen will be useful for engineers (pair programming, live debugging), designers (review with stakeholders - they can draw on your screen to give feedback), students and teachers, and anyone collaborating remotely.
You can view a 1-minute demo video by clicking the play button at https://screen.so, and there's a longer article at https://screen.so/about, if anyone's interested.
I’ll be around to answer questions and welcome any feedback. I hope you'll find Screen useful, especially during these times!