Max here from CoScreen.
I'm with you, sharing a portion of the screen or window would be very useful for this scenario. I can also imagine running CoScreen from the VM itself, but that would only work for Mac and Windows VMs at this point (Audio and video could still go through your physical machine —— i.e. you would connect with two users). We also have a headless Linux client in the pipeline that could serve to connect the VM directly.
Connecting with 2 users would work. I would still need to resize the window I'm sharing (the reason I have that big ass monitor is to use VS maximized and have everything open), but it's easier than resizing all windows.
Max from CoScreen here.
Yeah, we hear you. We have a web client coming out soon and a headless client that works on Linux in the pipeline. Hope to bring some early users onboard for the latter in Q2.
Max from CoScreen here.
Yes, we've heard this from many users as well. Generally speaking our approach to this is:
1. Deal with capturing and rendering of this in the native layer to achieve high performance and throughput.
2. Use something we call "DPI-match" to open shared windows at the right size on the receiving end to avoid unnecessary text blurring from pixel count mismatch.
3. Give the screen sharing stream high priority.
Max here from the CoScreen. I think the best way to put this is that there will still be a gracious free tier to help small teams get their work done and this will likely be metered on the number of users joining a session at the same time. Once a paid upgrade is available, we want you to feel it's worth it though :-).
I couldn’t have said it better myself @bmcahren! Perfectly summarizes the pain points we’ve experienced that led us to build this. (CPO of CoScreen here)
