Perch 0.18: one file, per-user, no admin
The Windows installer never asks for administrator rights, and that isn't a shortcut, because an elevated Perch simply wouldn't work.
Why elevation breaks it
Perch launches its own Chrome and mirrors a window out of it. The trouble is that an elevated parent starts an elevated child, and Windows then puts User Interface Privilege Isolation between that Chrome and the ordinary desktop, which is where the share picker lives, so the two halves would no longer see each other.
Nothing to grant
Windows has no screen-recording permission, so the right number of prompts is zero. macOS does have one, though, so Perch asks the first time you start a mirror.
What the installer does
Everything goes into %LOCALAPPDATA%, with the shortcut and uninstall entry under HKCU. The uninstaller lives inside the main executable, because a second binary would carry another copy of the .NET runtime, and the one step a process can't do, deleting its own folder, is handed off to PowerShell.
What it leaves alone
Your Chrome profile, with its sessions and cookies, is never removed silently, and the uninstaller tells you where it is instead. Everything else goes to the Recycle Bin rather than being hard-deleted, since an uninstaller is the wrong place to be irreversible.
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 postWhy loading an extension needs the DevTools pipe
