UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1. Install a PWA app on desktop macOS
2. Press cmd-tab to switch to the app, and notice it brings Chrome to the front of the recent app list as well
3. Press cmd-backtick and notice that the app switches away to other Chrome windows.

What is the expected behavior?
I expect the app to act as if it is entirely its own app, not coupled with Chrome.

When we're not running Chrome, and we launch a PWA, it should open that app, and we should not also see the Chrome icon. It should be as if Chrome is not running.

Then if we click on the Chrome icon that should "open" Chrome as if it is a separate app.

What went wrong?
Instead, it is coupled, meaning doing things like pressing cmd-backtick alternate between Chrome windows AND the PWA app window. This makes the experience less favorable.

After quitting Chrome, then launching a PWA app, the Chrome session will be destroyed. The only hope of getting anything back is to repeatedly press cmd-shift-t to open previously closed windows/tabs, and if lucky get them all back.

Did this work before? N/A 

Chrome version: 68.0.3440.106  Channel: stable
OS Version: OS X 10.13.4
Flash Version: 

It'd be great for the decoupling, so we have a better workflow and experience.