Changing app search site requires app restart to take affect
Closed, ResolvedPublic

Description

Repro steps

  1. Launch the app
  2. Note current search site (Settings > "Search ___ Wikipedia"
  3. Note nearby or search result languages
  4. Change search site

Expect results

  • Nearby immediately updates to pull results from the new site
  • Conducting a new search targets that site
  • Recent searches...?
    • Query the site they were originally targeted at?
    • Query the new site?

Actual results

  • Nearby doesn't refresh
  • Tapping "More nearby your location" yields no results
  • New searches still target the old site
  • Recent searches target the new site
BGerstle-WMF updated the task description. (Show Details)
BGerstle-WMF raised the priority of this task from to Needs Triage.
BGerstle-WMF added a subscriber: BGerstle-WMF.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 25 2015, 2:31 PM

@Fjalapeno @JMinor please triage, I think this should be fixed sooner rather than later, along with the search language UI/UX changes.

Yes, it makes sense to define/implement the impact of language switch when we actually implement the language switch.

To me UX of swtiching AND its effects are both blockers on the story "I want to switch my search language"

Here's my initial thought on behaviors:

  • Nearby immediately updates to pull results from the new site [agree]
  • Conducting a new search targets that site [agree, also if their is a language hint visible it should refer to new language]
  • Recent searches...?
    • Query the site they were originally targeted at?
    • Query the new site?

[Think these should target the new language if they are re-run. Here's my take on the user's mindset:
I run a search for "Someguy Popstar" in my usual language. I get no results. I then switch to searching en, because I know it has more coverage, I then select the query from my recent searches. If I get results in my local language that would defeat the point of re-running the search.

An alternative is for each language to have its own history. But that is more complex and also doesn't meet the need described above, as I'd have to re-type the search for my new language.]

Yeah, sounds like we'd have to do user testing to really suss out which recent search behavior works best. I think currently only save the query string, not the site (i.e. second behavior), so might as well go w/ that to stave off extra work.

Also, to be clear, after switching any actual cached results/suggestions should not be shown, only the actual search strings.

@JMinor to make sure I understand, are you saying that when I change the language I'm searching in, we should:

  • Clear current search results
  • Display all recent searches (query string only)
  • Preserve any query the user had typed in the search field

@BGerstle-WMF yes, I think you got it. If you think any of that violates
user expectations/intuitions, let me know. I think this workflow is covered
by our user testing plan already, but will make sure its on our list.

MBinder_WMF closed this task as Resolved.Oct 7 2015, 9:17 PM