Earlier quoted context omitted.
Yes unfortunately and yet only for now. We just started with Mac (coin toss) and now we'll do our best to cover all of them soon.
That's sad -- from your demo video, I thought you were supporting Windows too (the minesweeper window). You might want to make that more explicit.
Show HN: Coscreen.co – a radically different remote collaboration tool
61–70 of 188 posts
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#62Look forward to using this in linux! Definitely a tool I would use.
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#63There are two job positions to join their team as well. I guess they could even use their own tool during a test interview.
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#64Looks like a pretty neat product. Congrats on the launch
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#65Does this require installing a software on your computer? Or is this purely browser based? Or is it Java?
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#66Earlier quoted context omitted.
Ok so it's an all or nothing type thing? I'm either sharing my whole screen or none of it? Still definitely useful! Just trying to learn the limitations. This is awesome by the way, I'll definitely be checking it out!
Exactly - all your windows on your screen to be specific, so e.g. not your desktop background or files on your desktop. We're considering adding the ability to pick individual windows but feedback welcome...
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#67Earlier quoted context omitted.
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
#68Earlier quoted context omitted.
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…
Does that mean you use the JS Screen capture api to capture each and every window separately? I would’ve thought that’s too much for typical (laptop) cpus but have to admit I never tried this
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#69I am worried about screen sharing. Who knows what I could browse at work. I don’t want to mistakenly share my credit card number.
This is mostly harmless in my solo environment, although one does have to be careful about things like .bash_history and websites that might actually be listening for keystrokes and sending them upstream. Having a team window seems like it would make this a greater risk.
On a different topic, I'm one of those people that can't stand pair programming and related--it destroys my ability to concentrate deeply on the problem in front of me.
Re: Show HN: Coscreen.co – a radically different remote collaboration tool
#70And I wouldn't pay too much attention to the Windows/Linux users in the very early days if it's too much of a development burden. There are tons of tech forward companies that are mac-only that are a large enough market to build momentum.
If the windows/linux people want it make them put their money where their mouth is and charge them in some way. It costs nothing for them to say "Build this for me!" but they already have enough info from the demos and mac app to make a purchasing decision. So if they're serious get some money from them. If you do a pre-order and say "if it's not released in 3 months you get your money back" that should be enough signal to know if they really want it or not.
Congrats! Not many people make something this good. Now don't screw it up :)
And if you're not part of YC already you should do a late application for the W20 batch.