If there's one thing I can't stand in a screen sharing app (I'm looking at you, Slack and Zoom), it's annoying overlays. I want to be able to open up my IDE, go full screen with it, and have zero overlays visible. The only tool I've been able to find that lets me do this is Tuple (tuple.app), which is the closest thing I've found to Screenhero (which was my favorite screen sharing and pair programming app back in the…
Agreed! Soon CoScreen's UI controls will get hidden automatically so you won't see anything but shared windows.
OP here, we believe that the time has come to let remote workers and highly agile teams get stuff done together in a very different and much more natural way. CoScreen is a remote collaboration tool that enables exactly that. Problem: Pretty much anyone who has ever worked remotely knows it - today’s remote collaboration solutions provide much better screensharing quality and reliability (thanks, Zoom) compared to a…
Seems like a great idea. One question is visual data only shared among peers or does it pass through your servers?
Thanks! It goes through a central server so it can make it through corporate firewalls. This adds latency unfortunately but makes it more reliable for folks behind strange proxies and scales better for >2 users. But in any case, we'll enable P2P connections shortly so it won't go through the server if it doesn't have to, stay tuned. Sign up on our website and we'll let you know once it's out.
If there's one thing I can't stand in a screen sharing app (I'm looking at you, Slack and Zoom), it's annoying overlays. I want to be able to open up my IDE, go full screen with it, and have zero overlays visible. The only tool I've been able to find that lets me do this is Tuple (tuple.app), which is the closest thing I've found to Screenhero (which was my favorite screen sharing and pair programming app back in the…
Agreed! Soon CoScreen's UI controls will get hidden automatically so you won't see anything but shared windows.
That's awesome, and I'm glad to hear it!
If I could make a tiny suggestion: Why not hide the coscreen functionality under a little system tray icon with a pop-out menu? That way, it's invisible, but still easy to get to.
OP here, we believe that the time has come to let remote workers and highly agile teams get stuff done together in a very different and much more natural way. CoScreen is a remote collaboration tool that enables exactly that. Problem: Pretty much anyone who has ever worked remotely knows it - today’s remote collaboration solutions provide much better screensharing quality and reliability (thanks, Zoom) compared to a…
Congrats on the launch. This looks like one of those great ideas that works so much better than the old way that it feels obvious in hindsight. I’m curious how you handle different monitor resolutions?
Thanks a lot for the kind words!
Great question, CoScreen shows shared windows based on their relative positions and sizes. So they appear in the same way for all participants. If there are huge difference between resolutions, the users will see either very small/large fonts but we still concluded after many prototypes that this is the best tradeoff. Feedback welcome nevertheless...
OP here, we believe that the time has come to let remote workers and highly agile teams get stuff done together in a very different and much more natural way. CoScreen is a remote collaboration tool that enables exactly that. Problem: Pretty much anyone who has ever worked remotely knows it - today’s remote collaboration solutions provide much better screensharing quality and reliability (thanks, Zoom) compared to a…
How are you different from Vectera.com which does the same thing, but with persistent rooms too?
Thanks for your question! Afaik Vectera runs in your browser and focuses on sharing what's in it. CoScreen lives on OS-level so you can share and interact with any native window, browser or not. They also don't seem to support multiple users sharing windows at the same time side-by-side but please let us know if we're missing anything.
I'm curious why somebody would start with a machinetosh? Windows is used way more than machinetosh on developer machines. Is it because: 1) Authors don't know the demographics? or 2) They think that Windows users wouldn't pay? (Not true I think) or some other reason?
looking forward to using this once it rolls to linux