its funny, I was told that oneplus' OS is pretty close to stock android so I was hoping to avoid this sort of unknown unknown (if it is a oneplus issue - i havent verified that my issue doesnt happen on Pixel) I still dont know if this is the Browser or the OS' responsibility
-
-
Replying to @swyx @mhartington
This is very confusing! It *looks* like you didn't get a WebAPK installed (instead, you got a homescreen shortcut, hence the little chrome icon).
1 reply 0 retweets 0 likes -
What URL were you installing? I'm not aware that GitHub is a PWA.
2 replies 0 retweets 0 likes -
1 reply 0 retweets 0 likes
-
Replying to @slightlylate @swyx and
If you go to something that's a known PWA, e.g. http://airhorner.com or http://coronavirus.app and install them, do they install from Chrome w/o that little Chrome icon in the lower left?
2 replies 0 retweets 1 like -
Replying to @slightlylate @mhartington and
yes, they install w/o Chrome icon. OK I think I get it now - "Add to Home Screen" is overloaded for both PWAs and Chrome shortcuts, I have no way to know until after I install, and when I uninstall the shortcuts don't know that they are shortcuts and so uninstall Chrome itself?
1 reply 0 retweets 2 likes -
Replying to @swyx @slightlylate and
Yeah that's it. But note that shortcuts *can* be PWAs, too. Chrome (and also Samsung Internet) wraps PWAs in a native app shell when you install, so Android believes they are native – they get a normal icon, are visible in launcher, settings, etc., you can uninstall. ↓
1 reply 0 retweets 0 likes -
Replying to @JonasKuske @swyx and
But if you use another browser (e.g. Edge or FF), adding a PWA to your homescreen will only generate a normal shortcut, even though it'll work offline etc. Also possible with Chrome, just yesterday it skipped generating the app shell and only added a shortcut for some reason :/
1 reply 0 retweets 1 like -
Replying to @JonasKuske @swyx and
I don't know why this is so complicated – why is "Add to homescreen" overloaded, on desktop the message for PWAs is a clear "Install app?". Why does Android require slow workarounds like WebAPK? But no matter what, it definitely hurts PWA discoverability & feasibility. :(
2 replies 0 retweets 0 likes -
Replying to @JonasKuske @swyx and
(there was a wildly speculative blog post about it some time ago, guessing that maybe this UX is the result of the Chrome team and Android/Play Store team fighting internally, but
https://medium.com/@firt/is-there-a-cold-war-between-android-and-chrome-because-of-pwas-e50a7471056c …)1 reply 0 retweets 0 likes
Speculation is only that. Anyhow, we are trying to separate out the installation affordances. They're in the omnibox on desktop, and I think a pervasive, discoverable UI like that makes sense on mobile too. A long road to get there, but we're on it.
-
-
Replying to @slightlylate @JonasKuske and
thank you! i understand it is a work in progress. Figured I'd throw myself in the deep end and live it for a while to get a good feel for the state of things. i expect pain.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Replying to @slightlylate @swyx and
Yep, wasn't sure whether to add the link or not – but the pain points mentioned are valid, so I thought there's still value in sharing as long as I mention the "wildly speculative" part right in the tweet :) Also: I appreciate the constant progress & the experiences it enables!
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.