Yeah, but Android Apps on Chrome on the O/S is a hell of a lot of overhead for a basic HTML5 single-page that you would just rather package and have in an independent window rather than forcing the user to always have to keep a tab open.
I have a Chrome app music player (a client for subsonic), an html5 app that I also serve on the web and deploy on Amazon's Fire OS platform. For a time it was on Firefox as well as an app but they eliminated their "app" capability a year ago.
The problem is that I want this music player to be independent, as most music players are. I don't want to force the user to keep it in a tab, stuck in size to the window of the rest of the browser. I *like* having them be able to open it independently, size it to what they want, etc, just as they would the player if it was native.
Now, with Chrome throwing this away, I am going to have to look at new deployment tech like electron, which adds a huge amount of overhead (though less than running in an Android interpreter) for the same feature set that Chrome was giving me effectively for free.