1130495 - (iostabspanel) IOS-64 - Home Panels - Synced tabs

Status: RESOLVED INVALID

(Firefox for iOS :: Home screen, defect, P4)

Comment 2

[Richard Newman [:rnewman]]

(Removing that dependency 'cos it's transitive on Bug 1141847.)

Comment 3

[Nick Alexander :nalexander [he/him]]

For the record, there are no mocks for the Synced Tabs panel.  I'm rolling my own, informed by the other panels (tabs look like history tabs, for example) and Android's panel (clients will have a grey background, for example).

Comment 4

[Nick Alexander :nalexander [he/him]]

tecgirl: it might not be v1, but I'd love to get some UX input on how we could switch from a "client-centric" view to a "latest-tab-centric" view.  Right now, we're going:

client
  tab
  tab
client
  tab
  tab

with clients ordered with the most recently synced first and each client's tab ordered in the position it appears on that client.  I think it's more helpful to do something like:

most recent tab
tab
tab
tab

possibly without indication of the originating client, even.  But the two views are used in different situations, so we might want a toggle.  Can you opine?

Comment 5

[Nick Alexander :nalexander [he/him]]

Attachment: Link to Github pull-request: https://github.com/mozilla/firefox-ios/pull/232

Still several TODOs but best to land something.  This will need a fresh Home Panel icon, too.  I will file follow-ups as needed.

The underlying Remote Tabs data store commit has r=rnewman, just waiting for feedback on this to land.

Comment 6

[Nick Alexander :nalexander [he/him]]

https://github.com/mozilla/firefox-ios/commit/d71b02325fc822be7f757468133c9380c861151d

Comment 7

[Robin Andersen [:tecgirl]]

:nalexander  - Based on some of our recent task continuity research we found some users to associate content based on which device it was on, but there could be an opportunity to improve upon that pattern by offering a different view choice—one that allows simple date sorting, regardless of device. Most users will typically have 2-3 devices so showing a list that is purely time-based could work, rather than sorting by device—but I would still vote for showing the device next to the entry. I'm willing to give that a shot for v2.