New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 853646 link

Starred by 3 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Installed PWAS should get a boost to be on the NTP

Project Member Reported by benwells@chromium.org, Jun 18 2018

Issue description

It should be much easier for an installed PWA to appear on the NTP than a non-installed site (i.e. they should require less usage).
 
I think this is a great idea, but I think it might have some unintended consequences. Would the PWAs open in their own window or as a separate window? PWAs are trying to train a new user model / expectation and if users start getting to them in browser tabs from NTP, it might work against us. I could easily see us making a new section for PWAs in NTP though. 
Components: UI>Browser>NewTabPage
There's also the complication of what source the NTP is using:

 * the feed / content suggestions
 * suggestions based on Sync
 * Most Likely (local-only)

I made some changes a little while ago in Most Likely to add site engagement sorting aside the standard history-based scoring. Switching the NTP to use site engagement sorting exclusively would give installed PWAs an inherent bump automatically, but we could also look to adda hardcoded boost independent of whether engagement sorting is on.

We should probably chat to the Most Likely team regarding this.
I figure it should be less likely for an installed PWA to appear on the NTP because they would already have a shortcut installed in the OS.
Labels: zine-triaged
Cc: ramyan@chromium.org

Sign in to add a comment