[RFC] ATHS component #180
Description
What problem does this feature solve?
As a follow up to discussion I had with @pi0 and @atinux I would like to propose a small DX enhancement for PWA module in a form of PWA components.
An example of such component would be ATHS component which I would like to start with.
Currently the ATHS banner that is shown by Chrome has a lot of limitations (especially when it comes to design) and can't be spawned again after dissmision which is a undesirable behavior for (probably) anyone that builds a PWA. Another problem is lack of common ATHS flow across browsers.
Proposed solution is a soft opt-in component responsible for ATHS behavior. It will handle catching the native beforeinstallprompt event, preventing default banner from being shown and passing the native prompt() event into a scoped slot so developers have more control over ATHS flow and the way it looks.
Having it handled in a 3rd party component will also help with promoting good practices and being up to date with web standards.
Please let me know what do you think about this idea @pi0 ;)
What does the proposed changes look like?
Example usage could look more or less like this:
Add to Home Screen