Writing

What Chrome will and won't let an app hide

CCalyndraeEngineering notes, Perch

Two screen-sharing restrictions shaped Perch, and both were found by trying it the other way first.

The sharing bar stays

When a tab is captured, Chrome shows its own indicator, and no flag, policy or DevTools method removes it. That's correct, too, because an indicator the capturing app could hide would be worthless. Perch doesn't try, and instead the mirror is a separate window, which means the window you work in isn't the one wearing the banner.

A captured tab won't go fullscreen

That's deliberate as well, since a page that could fill the screen the moment capture starts would be a phishing tool. The mirror handles fullscreen on its own window instead, which isn't under that restriction.

The pattern

Every screen-capture restriction found so far protects the person whose screen it is, and designing with them, rather than around them, produced the better product. The mirror is separate because it has to be, and being separate is exactly what lets you keep working.

This is a shorter version of a post on the Pioneering blog, so if you want the full story, read the original on pioneering.app.

Next postThe “just trying to make friends” dropshipping scam