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.
I would’ve thought that’s too much for typical (laptop) cpus but have to admit I never tried this
The way I understand you, coscreen captures each window shown individually.
Doesn’t that also mean that overlapping windows are captured in full? I can’t try it out atm so perhaps if you could leave a comment on cpu usage for encoding as well as bandwidth (upload) compared to a typical Screen Sharing solution with a single screen that would be great.
I’ve been toying with the idea of getting a MacBook with cores > 4 for precisely that idea: capturing every single window, streaming them out to a separate machine for analysis of what’s happening in them and possibly making them accessible for collaboration as well, all without losing too much performance
I believe somewhere in this area is a lot of productivity waiting to be unlocked with better tools, not just for typical remote use cases but for any kind of office work
"Windows is used way more than [Macintosh] on developer machines." - Citation needed. Macs are extremely popular among web developers, and are required for iOS developers, both pretty major categories of "developer".
Edit: + Stats from the Stack Overflow Developer Survey 2019
Windows: 47.5% MacOS: 26.8% Linux-based: 25.6%
Source: https://insights.stackoverflow.com/survey/2019#technology-_-...