1071730 - Clean up Search suggestions and Search history UI

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: Awesomescreen, defect)

Description

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

Attachment: XXHDPI - Mobile - Typing 2.png

I'd like us to consider improving our search UI by cleaning up the suggestions tiles. In keeping with the UX of the current model, I think we could still improve the UI of it.

Splitting this off from bug 909536.

Ni-ing Mark and Karen to get their eyes on this.

Comment 1

[Mark Finkle (:mfinkle) (use needinfo?)]

Please also consider tablets, which have more space.

This is a lower priority than other work we have on the Roadmap, but we should make sure this is in the Project Funnel for prioritization.

Comment 2

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

(In reply to Mark Finkle (:mfinkle) from comment #1)
> Please also consider tablets, which have more space.

Definitely, just wanted to quickly mock something up to keep the ball moving.

> This is a lower priority than other work we have on the Roadmap, but we
> should make sure this is in the Project Funnel for prioritization.

I imagine some of the telemetry data we've been collecting around which suggestions are typed, search activity, etc could help shed some light on this too.

Comment 3

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

Just leaving a note here: we'll revisit this once a search deal is in place. 

This (as Margaret mentioned) could also be looped into "Awesome screen improvements".

Comment 4

[Karen Rudnitski [:kar]]

Adding Deb to the bug. This can be added to the list of things to explore for search first thing in the new year!

Comment 5

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

Attachment: prev_suggestionsUI.png

Attaching an updated mock of the proposed suggestions UI update (now matches all the other work we've been doing on panels,etc) on mobile as well as tablet.

Note: Need to experiment with the quick search controls on Mobile as there's significantly less space. One option would be to hide it in the long-press function but that might require some visual affordance for discoverability. 

NI-ing Kar as well

Comment 6

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Suggestion: use the search suggestions to search any of the providers.

Comment 7

[Deb Richardson [:dria] (plz NEEDINFO)]

So for the mockup the tablet version has the other-provider icons at the bottom, above the keyboard. Is that something we're going to do for phones as well, or just tablet?

If also for phones, I'd love to see a mock up for that as well.

Comment 8

[Karen Rudnitski [:kar]]

I think I'd like to test this out - it doesn't totally feel like an intuitive experience to me (at least yet). From the mock, I assume we would provide a suggestion from our default in the first line (and attribute it as such). But are those supposed to be 'generic' suggestions that I then follow through by tapping on a provider? Or are you thinking of providing a list of suggestions from each provider in that list (which I think would be hard since we have limited space and do we limit 1 suggestion per provider, does this cannibalize our use of the default provider, etc).

If we were to provide one or two lines of suggestions from the default and attribute as such (with their favicon to the list), and provided generic suggestions (where would this come from) and a user could tap on their preferred provider, that's one possibility - but I want to get to the same understanding of what's actually happening :)

Comment 9

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

Adding Nalexander to stay in sync with this work going on from the iOS side. 

Though, from discussing with Darrin and Robin, we want to explore this bug more thoroughly together. So we can hold off on this for now.

Comment 10

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

NI self: look into pre-landing strings so we can try to get this into 39.

Comment 11

[Allison Naaktgeboren :ally]

So it looks like the last discussion on this bug was about 8 months ago, long before the recent rework of search suggestions & inclusion of local search history.

Where do we stand on this now? Should we close this?

Comment 12

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

Thanks for the reminder Ally!

I think the latest work we did in bug 1199335 addresses some of my earlier concerns that I had in this bug. Since there, there's also been more change and the goals don't really apply any more.

I'm going to close this for now.