| scblr | |
| Nov 25 2020, 8:46 AM |
| F34000584: Screenshot_20210114-124848.png | |
| Jan 14 2021, 11:58 AM |
| F33989621: device-2021-01-07-092333.png | |
| Jan 7 2021, 2:28 PM |
01) Make sure all items related to articles in the Explore feed use the same long press dialog actions as the ones within the article, namely:
(Dialog actions only consist of save and share at the moment)
02) Change “Add to reading list” in the article dialog menu to “Save” as well (when long pressing a link)
From the Explore feed, giving the option to "Open" and "Open in new tab" seems very confusing. Tapping "Open" will actually open it in a new tab anyway. But tapping "Open in new tab" puts it in a new tab, but doesn't actually open it? Are we sure about this?
From the Explore feed, giving the option to "Open" and "Open in new tab" seems very confusing. Tapping "Open" will actually open it in a new tab anyway. But tapping "Open in new tab" puts it in a new tab, but doesn't actually open it? Are we sure about this?
Yes, 100% sure. It’s consistent with the article experience and with Chrome’s default browser behavior. In both of these cases, “Open in new tab” opens items in a new background tab.
Yes, 100% sure. It’s consistent with the article experience and with Chrome’s default browser behavior. In both of these cases, “Open in new tab” opens items in a new background tab.
I don't feel too strongly about this, but I'm not sure the comparison with Chrome is accurate. A more apt analogy would be:
The user long-presses on something on the home screen of their device, and selects "open in new tab", and sees a message like "This item is now open in a background tab. To read it, you'll need to open Chrome, click on the Tabs list, and select the new tab from that list."
I disagree here. As opposed to seeing Explore as a “home screen of their device”, I look at Explore as another layer discovery layer in the app. Similar to open tabs that contain articles, Explore “coexists” as a possible origin to get to other destinations (tabs). The “additional tab number” animation will inform users about the tab that has been opened in the background. I think that is enough guidance for this and a common behavior.
Thanks @Dbrant. I don’t think an explicit snackbar is needed.
With the snackbar, the user’s attention is drawn to the bottom of the screen, but the actual area we want to show them is the top (where the tabs live). The amazing tab animation (did you tweak it? 👏) does an excellent job at drawing the user’s attention to the tabs at the top and where the actual action happens.
