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.
We're capturing them natively and are working on another major performance improvement which should make it at least as efficient as other major solutions.
Are there other solutions that capture multiple windows at once? I’m only familiar with typical screensharing where the use case is either full screen or a single window.
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
We do capture overlapping windows separately but we turn them into one video feed with overlaps to save bandwidth and overhead. We might stream windows individually but feel free to reach out directly if you have specific requirements & ideas.
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.