Closed
Bug 1314732
Opened 8 years ago
Closed 7 years ago
[User Story] As an Android user, I want to change the name of a top sites item so i can more easily recover it later (mental queues)
Categories
(Firefox for Android Graveyard :: Activity Stream, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jchaulk, Unassigned)
References
Details
(Whiteboard: [MobileAS])
No description provided.
Comment 1•8 years ago
|
||
- We need a way to persist a user-defined name for a top site item: Bug 1320803
- We need UX to rename top site items, likely via an action menu: Bug 1320804
- We need telemtry tracking of this action: Bug 1319245.
Comment 2•8 years ago
|
||
Thinking more about how we might actually store this data, I'm not sure this is necessarily part of an MVP.
I think one of the assumptions behind this feature is that combination of the display name we derive from page's metadata and page's favicon is not enough for a user to remember what a given Top Site might be, and quickly find it later. It seems that if the page made it to Top Sites, user is well familiar with it. So we're left with renaming as a way for a user to "improve" how Top Sites look, or perhaps tidy things up a bit. For example, they might prefer to set "gdocs" instead of "docs". But to me that doesn't seem like a core feature we should focus on for the MVP.
We have ongoing work to improve top site names which we display which should help with recall; see Bug 1311434.
This also ties into our multi-device story - as things stand, there wouldn't be an easy way to sync this data across devices, so any custom naming that user performs will not carry over, and will be lost if they switch devices. We've talked about augmenting sync with A-S data, but that seems to be ways away, unlikely to be ready before mobile MVPs.
If we want to validate our assumption that this is indeed a valuable feature, we could add a basic UX for this, but without the supporting functionality. UX could be entirely fake, or it could inform the user that is is "work in progress". (A-S is marked as an "experimental" feature in the advanced settings as things stand, so this isn't too far fetched). From telemetry we'll be able to tell if our early population is trying to use this feature, and implement it if we see the demand. This will demand on early population to be representative and large enough.
We could do a hackier implementation of the backend for this using something like SharedPrefs, or work out how to best fit this with other metadata we have for pages (yet another table?). But generally I don't want to do this work if it's not needed.
Flags: needinfo?(bbermes)
Comment 3•8 years ago
|
||
Thanks for the great summary, based on your breakdown of what work needs to happen to make this work, I agree with you that this is not part of the MVP and we should remove it.
I'm fine with pausing this feature.
Jenn, I can't find the equivalent bug for iOS, I removed it from the AS Android Trello board but would like to do the same for iOS. Would you happen to know the bug number? Thanks.
Flags: needinfo?(bbermes) → needinfo?(jchaulk)
Reporter | ||
Comment 4•8 years ago
|
||
I don't think there was an equivalent US for iOS. All of the user stories (open and closed) for iOS are here: https://mzl.la/2jrtXak and I don't see one about renaming your top sites.
Flags: needinfo?(jchaulk)
Updated•8 years ago
|
Blocks: as-android-notyet
All open Activity Stream bugs are moving from the whiteboard tag, "[mobileAS]", to the Firefox for Android component, "Activity Stream", so that I can keep better track of these bugs as the new triage owner; I will send out an email shortly with additional details, caveats, etc.
Component: General → Activity Stream
We only have one bug (bug 1320804) so this meta feels unnecessary.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
(In reply to Michael Comella (:mcomella) from comment #6)
> We only have one bug (bug 1320804) so this meta feels unnecessary.
That is bug 1320803.
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•