3 ms·
I tried messing with these flags a month or so ago to see how close one could get to creating a standalone web app without needing to use Electron or similar. I
by russellbeattie 4y ago
I tried messing with these flags a month or so ago to see how close one could get to creating a standalone web app without needing to use Electron or similar. I assume the binary executable that a PWA installs is essentially just setting these flags on startup, so I decided to try to figure out which ones.
As someone else stated, most of the app oriented flags are ChromeOS specific, so I didn't have much success. I tried a lot of different combos and scrolled through Chromium's .h headers to see what I could find. It was a good way to waste an afternoon and learn a bit more about the browser. Kiosk modes, dummy profiles, full screen, single window, security flags, etc. Lots of interesting features you don't run across regularly.
- terinjokes 4y agoIf you create a PWA on Linux all it does is drop a new ".desktop" file in `$XDG_DATA_HOME/applications`, which you can then inspect to see what flags it sets. I imagine it's mostly the same flags as used on other platforms.
- russellbeattie 4y agoOh, wow. Thanks! I will totally look at that!! I was even trying to look for strings within the Mac binary, and browsing around the repo for the PWA creation code (which I didn't find). I'm super curious what's in the .desktop file. I'm definitely going to check that out this evening.
- russellbeattie 4y agoTurns out it just calls Chromium and passes an app id: [Desktop Action Edit] Name=Edit Exec=/usr/lib/chromium-browser/chrome --profile-directory=Default --app-id=idjenohckefppahppaeclfgpbfkfppaf --app-launch-url-for-shortcuts-menu-item=https://www.hypertext.plus/editor/