For me personally, memory usage has been a big concern with the growing number of Electron apps. CPU usage on well-behaved Electron apps in idle seems mostly negligible or at least not significantly worse than on native apps.

But memory is a different story. I don't always get to work with machines with "enough" memory, so I don't keep any apps with a larger memory footprint (let's say anything above 50MB) running longer than necessary. More often than not I will try to just use the web app, which will at least not load "yet another copy of Chrome". Where feasible I will also simply switch to an alternative.

Not to backseat engineer too much, but maybe you could look into a smaller native component that can run in the background to listen for incoming "calls" and only loads up Electron (or maybe a native webview) when the user wants to actively use the app.

All of that said, it looks like you have a solid product and I wish you success with it.

EDIT: It appears that a year ago when your product was still named screen, I also provided some feedback which you acted upon swiftly, so I'm optimistic you'll figure this out as well :-)