Live data from Hacker News

Show HN: Coscreen.co – a radically different remote collaboration tool

coscreen.co

31–40 of 188 posts

Re: Show HN: Coscreen.co – a radically different remote collaboration tool

#31

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?

it might be a technical reason sometimes. Does windows provide an API for you to capture a window, instead of a desktop on a specific screen?

True, just in this case we just went with Mac because we used it personally. Windows might actually have been easier because macOS gets increasingly restrictive (e.g. with Catalina). Nevertheless, glad we made it and we'll do our best to support all major OSes.

Re: Show HN: Coscreen.co – a radically different remote collaboration tool

#33

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?

it might be a technical reason sometimes. Does windows provide an API for you to capture a window, instead of a desktop on a specific screen?

I don't want to make this a game of one upmanship but I'd be surprised if there are GUI things you could do on a machinetosh that you cannot do on Windows.

Re: Show HN: Coscreen.co – a radically different remote collaboration tool

#34

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?

Thanks for the question. It was honestly a close call and we knew we couldn't do both at the same time (this is a side project).

The reasons where:

1. Our personal devices were Macs at the time we started.

2. We felt that the first use case for CoScreen would be agile developers who collaborate with UX designers. The latter seemed to mainly use Macs (https://austinknight.com/writing/designers-prefer-macs) while the former are mixed e.g. also depending on the region. In the SF Bay Area Macs quite popular among developers so we ran with it.

In any case, we hope to be able to support all 3 OSes soon. For that reason CoScreen was built 95% in a platform-agnostic way (nwjs) so we're optimistic.

Re: Show HN: Coscreen.co – a radically different remote collaboration tool

#35
This is a great idea, and your implementation of it looks awesome! I don't have a use for it at the moment, but I'm bookmarking it for later.

A bit of feedback on your website: the yellow you've chosen is nearly impossible to read on my monitor, especially with the thin font used in "Sign up".

Re: Show HN: Coscreen.co – a radically different remote collaboration tool

#36

Earlier quoted context omitted.

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.

Good point, we had thought about it but wondered if users would find it. But we'll look into it based on your feedback...

Re: Show HN: Coscreen.co – a radically different remote collaboration tool

#37
post #9

I am worried about screen sharing. Who knows what I could browse at work. I don’t want to mistakenly share my credit card number.

Even with CoScreen you only share screens/windows when you want to. You can go online/offline with a tap of a button and in any case it only shares windows on a display you choose.

Re: Show HN: Coscreen.co – a radically different remote collaboration tool

#38
This looks like a cool product if both people have a secondary screen.

A similar but much more low-key solution that I love using is tmate[1]. Tmate is a tmux session that can be shared over SSH. It's super easy to install and anyone who has a SSH client can join in two seconds. It's great for pairing sessions if both developers are into vim or emacs editors. Or just to show a quick thing.

[1]: https://tmate.io/

Re: Show HN: Coscreen.co – a radically different remote collaboration tool

#39
post #32
post #27

Earlier quoted context omitted.

"It also works great if you only have one screen"

Where do you see that? I can't find that on the page. Also, how?

Great question - here's how it works: If you only have one display (e.g. while you're on the run) it can still share the windows on this desktop but you can share/unshare all of them with a single click on the display icon next to your user. You can also auto-minimize all your windows when joining a room.

Re: Show HN: Coscreen.co – a radically different remote collaboration tool

#40
post #7

Earlier quoted context omitted.

The intro video on the homepage shows the actual software in action at around 53 seconds (mouse over the video to unveil the seek bar).

Exactly, here's the direct link: https://www.youtube.com/watch?v=gHI5-ne2F2I&feature=youtu.be...

I thought this was vapourware.

The best video you can show for this is your JIRA board where everyone can update it in realtime in a team meeting with remote teams.

Don't bother with the animations, they make your product look not real! Very impressive.

Post reply on HN