You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd prefer the manifest-per-application (PWA-pa) approach.
We've done this in v1 with code that assembles the manifest on the fly.
Roughly:
// Append manifest to head.useEffect(()=>{// construct manifestElement from manifest// ...constmanifestElement=document.createElement("link")document.head.appendChild(manifestElement)},[manifest])
An alternative is to make the entire coder dashboard a PWA, but we've gone that route before and it's not as great of an experience as solely having the applications as native-like installs.
@vapurrmaid that seems to be an even better enhancement.
Since the original proposal is a one line change, I think the PWA behavior should be in a separate issue. There's also the matter of how apps behave when the user refuses PWAs.
For one, it's consistent. For two, @mtm20176 thinks it will demo better. We can easily reverse this change too.
The text was updated successfully, but these errors were encountered: