Developers have asked us for a long time how they can pitch and optimise PWA installability; @b1tr0t and the team have done great research into what can (and does) work:https://twitter.com/b1tr0t/status/1136293261725786112 …
-
-
Replying to @slightlylate @b1tr0t
The 30 second engagement heuristic is a bit of deal breaker from a UX perspective. If someone looks at a menu in the first 30 seconds and sees either a greyed out "install" link or no link, then they're not going to look back later.
1 reply 0 retweets 0 likes -
There's no 30 second heuristic. PWA install UI only shows when we can verify that the SW installed successfully, and that's async.
3 replies 0 retweets 2 likes -
Replying to @slightlylate @Stafree
Wonder if there are UX tweaks that could be made. Thinking out loud, show the install button, allow a shortcut to be installed that can async be upgraded to a webapk if the user interacts with it?
1 reply 0 retweets 0 likes -
We can do better (on average) from a UI latency perspective by propagating a bloom-filter of installable sites so that we can start showing UI immediately on SW registration.
1 reply 0 retweets 0 likes -
This would necessarily prioritize sites that get lots of installs, but that feels right-ish. Doesn't need any new data and we can derive the list from the WebAPKs backend.
1 reply 0 retweets 0 likes -
As for shortcut-upgrade, we should be doing that anyway for sites where the backends timeout and we do the fallback flow.
2 replies 0 retweets 1 like -
We can also be more aggressive about showing install UI when we get omnibox install for mobile *cough cough*
1 reply 0 retweets 1 like -
That is, we do have an engagement bar today, but it's super low. We can do away with it entirely in an omnibox install world.
1 reply 0 retweets 0 likes
In summary, omnibox install for mobile...pic.twitter.com/OO0cyG8dXL
-
-
How would omnibox install play with say the AGSA UI? Assuming no on-page CTA for install, would it be AGSA -> Open in Chrome -> omnibox install prompt?
1 reply 0 retweets 0 likes -
AGSA uses CCT today, which support the install banner. Omnibox-install equivalent for CCT still TBD, and perhaps easier to get done.
0 replies 0 retweets 0 likes
End of conversation
New conversation -
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.