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?
Show HN: Coscreen.co – a radically different remote collaboration tool
31–40 of 188 posts
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#32Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#33I'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?
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#34I'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?
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
#35A 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
#36Earlier 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.
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#37I am worried about screen sharing. Who knows what I could browse at work. I don’t want to mistakenly share my credit card number.
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#38A 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
#39Earlier 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?
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#40Earlier 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...
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.