Screenhero founding engineer here. I've been working with the CoScreen team for a few months now, and I am incredibly impressed with the product and the team. They've taken our idea and really pushed it forward—it's not collaborative screen sharing anymore, it's a shared desktop which anyone can drop a window onto. (I'm only a little embarrassed we didn't imagine this UX back in 2013). If you've never used something…
What is your opinion on https://screen.so ? They are made by your ex-colleagues.
CoScreen: Screen Sharing for Engineers
61–70 of 96 posts
Re: CoScreen: Screen Sharing for Engineers
#62Earlier quoted context omitted.
I hate to say it but this sounds fairly close-minded. Does this need to be a new product? Yes. There are no great collaboration tools for developers I've ever seen like this. I'm immediately willing to pay whatever it costs to get this for my team. No more awkward calls trying to communicate complex concepts that don't often have terminology unless you make it up. Quickly highlight and explain a conflict without back…
Does your product support iPad with drawing? Because difficulty of explaining is often relieved with visuals, as opposed to merely gesturing at something with the mouse. It’s something that’s keeping me on Zoom vs the competition.
The way we're doing this is that we use Miro (https://miro.com) on an iPad, open the same file on the desktop and share that window using CoScreen.
That way you can draw on the iPad, share the content via CoScreen with your peers and they can even draw at the same time - all while sharing & interacting with other windows in parallel. Does that address your needs?
Re: CoScreen: Screen Sharing for Engineers
#63Looks promising. I've used and enjoyed VSCode Live Share before https://code.visualstudio.com/learn/collaboration/live-share Two great features they have are: - The ability share a local service to your peer by simply forwarding a port. - Remote debugging. Participant 1 can start a debugging session and Participant 2 has access to the full debugging introspection without interfering with the host's session.
VS Code Live Share is one example of what I hope the future of remote collaboration will actually be: sharing of high-level semantic data rather than mere pixels and input events. The former is way more accessible with screen readers and other assistive tools, for one thing.
Re: CoScreen: Screen Sharing for Engineers
#64Looks promising. I've used and enjoyed VSCode Live Share before https://code.visualstudio.com/learn/collaboration/live-share Two great features they have are: - The ability share a local service to your peer by simply forwarding a port. - Remote debugging. Participant 1 can start a debugging session and Participant 2 has access to the full debugging introspection without interfering with the host's session.
We also use VSCode quite a bit at CoScreen and it works great in combination with it. The issue is that VSCode Live Share alone only enables you to collaborate on code and partially on CLI.
But if you need to debug e.g. in Chrome inspector, review logs in some other browser, explore a design in Figma, etc., you need a tool like CoScreen to go beyond code.
Re: CoScreen: Screen Sharing for Engineers
#65Earlier quoted context omitted.
CTO of CoScreen here: It has been a grueling labor of love to get where we are, and there still is a lot of work ahead of us. And we can only acknowledge the shoulders of the giants we obviously stand on, like Doug Engelbart. Linux is definitely on our roadmap. We want to know which distros are you most interested in for us to officially support first?
The eternal answer "on our roadmap", translates from PR-speak to actual-speak: "no significant userbase to justify any work". I guess we'll stick with gnu-screen and tmux for the time being.
Totally understand your frustration. We started with macOS, then delivered Windows in around 3 months (just launched) and will tackle Linux next but granted that it is a ton of work given our deep integration into operating systems and we want to get it right.
Re: CoScreen: Screen Sharing for Engineers
#66I'm not sure how to ask this question in a way that doesn't sound snarky, so having said that I'll try: At the end of the day, is this beneficial enough to justify a completely new product versus just sharing your screen/window over Zoom (etc.)? When I'm pairing, I prefer to have a single "driver" where the pair is there to work through the bigger ideas and course correct code level decisions. I've never really wishe…
There used to be an app called ScreenHero, which did. this, and it was really great. For some reason Slack bought it and killed it, but I think it validated the use case
The original founder went on to create https://screen.so which is what we use for our team. Free since Covid too
Re: CoScreen: Screen Sharing for Engineers
#67Earlier quoted context omitted.
Looks amazing. I love that you guys have Doug Engelbart subtly in your demo video on the main page. Finally we can do something Doug was able to achieve 53 years ago! No seriously, great work. This is what computers are meant for. As a Linux user I have to ask, when is the Linux release? As soon as that's out I'm throwing zoom away.
CTO of CoScreen here: It has been a grueling labor of love to get where we are, and there still is a lot of work ahead of us. And we can only acknowledge the shoulders of the giants we obviously stand on, like Doug Engelbart. Linux is definitely on our roadmap. We want to know which distros are you most interested in for us to officially support first?
Flatpak
Re: CoScreen: Screen Sharing for Engineers
#68For the CoScreen team, I'm curious how the existing competition ( https://tuple.app/ , https://screen.so/ ) factors in to your decision to build/position this - do you believe you have a different vision than they do? Features they can't match? A better team that will out-execute? Out-market? Startup founders are often told not to launch a product that has direct competitors already, so I'm curious to hear your take!
Screenhero engineer here, and currently working with CoScreen. TBH, Tuple adn Screen both seek to re-create Screenhero (and do an amazing job of that!) CoScreen, while using similar technology, has completely rethought the UI from the ground up, and is a huge step forward that the others are going to have a hard time catching up with. Instead of one person sharing their screen, with CoScreen, each participant can sha…
Tech question: do you plug in to the native compositing UI system or do you have your own cross-platform UI compositing code?
Re: CoScreen: Screen Sharing for Engineers
#69Earlier quoted context omitted.
CTO of CoScreen here: It has been a grueling labor of love to get where we are, and there still is a lot of work ahead of us. And we can only acknowledge the shoulders of the giants we obviously stand on, like Doug Engelbart. Linux is definitely on our roadmap. We want to know which distros are you most interested in for us to officially support first?
The eternal answer "on our roadmap", translates from PR-speak to actual-speak: "no significant userbase to justify any work". I guess we'll stick with gnu-screen and tmux for the time being.
I realize your skepticism to my original answer, but I am 100% earnest about our intentions regarding Linux. It isn't a secondary concern for us, and we know how important it is for engineers.
Most of the developers on our team are avid Linux users.
My previous job was writing eBPF security drivers and device drivers, and I have used Linux for years.
Linux is very near and dear to our hearts, and when I say it's on our roadmap, I mean it.
Re: CoScreen: Screen Sharing for Engineers
#70Please forgive me if it's been answered, but how does CoScreen.Co compare to Screen.So?