Change Details

### Analytics questions in regards to search usage #### 01) Do we have any insights on where users are searching from in the app? There are three possible origins: 1. Explore search bar below Wikipedia 2. Explore search icon at top right 3. Article search icon at top right This is the only insight I have in regards to search usage so far: F31951319 It says that ~ 28% from all page views are coming from internal search, but not which one exactly. Dmitry pulled this data back in April 2019. **👉 This data will be used to revise the information architecture of the app → where do we show search?** #### 02) What percentage of search queries end up with zero results? #### 03) Do empty results stand in direct correlation with having set multiple languages in the app? **Hypothesis:** People are looking for something with the wrong language filter enabled. The more languages set, the more likely it it is to get no results. A simple split for this data would be great. E.g. 1 app language set → 2% no results, 2 app languages set → 3% no results, 3 app languages set → 3% no results. **👉 Data from 02) and 03) will be used to revise the design for empty state.** --- Adding @SNowick_WMF’s email reply here for the sake of completion > We have a Schema that tracks users search within the app: https://meta.wikimedia.org/wiki/Schema:MobileWikiAppSearch that I can get data from. That has a `source` field: "The source from which the Search interface was invoked: 0 - Main article toolbar, 1 - Widget, 2 - Share intent, 3 - Process-text intent, 4 - Floating search bar in the feed, 5 - Voice search query."

### [👉 Kickoff slide deck](https://drive.google.com/file/d/1g3RyCY4pwdlBZTyPYqQhJwu7FO6cJq-G/view) --- ## What are the problems we are trying to solve? 1. **Inconsistency:** The current search experience in the app is not inconsistent and misleading for users. - Search in `Explore` via search bar or magnifier glass leads users to the global search. Search in `Article` works the same way. - Search in `My lists` searches list names and articles in lists (T188333). - Search in `History` searches the users history. Even though the search scope and functionality is different, the iconography that is used remains the same. 2. **Reachability:** Search is the most used feature in the app, but it’s physically one of the hardest/furthest to reach on a touch device. The search bar on Explore is positioned in the top area of the device and the icon/button is positioned in the app bar. 3. **Intelligence:** The current search experience is limited in its capability to suggest relevant results for the user. It does not include results from `My lists`, `History`, `Open tabs` and `Other languages` that are set in the app. ## What are the goals? - Search becomes consistent, intelligent, and easier to reach. - Internal search usage increases [from 27% to 30%](https://phabricator.wikimedia.org/F31951319) ## Scope of the task This task is not about trying to alternate the existing server side search algorithm used in the app. It is about finding ways to improve the search experience on the client side. ## Optimization in three steps: 1. Clearly communicate the **scope of a search**. 2. Make search **easier to reach and use**. 3. Present **more relevant search results**. 👉 Check out the subtasks for details. ### Todos - [x] Create slide deck ([PDF](https://drive.google.com/file/d/1g3RyCY4pwdlBZTyPYqQhJwu7FO6cJq-G/view)) - [x] Gather feedback from Android and Design team - [x] Talk to Alex about process for Desktop Refresh Search - [x] Talk to Sudhanshu about search in emerging markets - [x] Create proposal for an improved search based on initial feedback from Android and Design (T259717) - [x] Create proposal for an improved article search experience based on initial feedback from Android and Design (T259795) (per @Pginer-WMF’s [feedback](https://drive.google.com/file/d/1g3RyCY4pwdlBZTyPYqQhJwu7FO6cJq-G/edit?disco=AAAAKC5X9ME)) - [x] Create task for analytics questions in regards to search (T259883) - [x] Send out draft for first proposals - [ ] Gather feedback on first proposals - [ ] What happens when results overlap e.g. `My lists` and `History` ? Is it only shown once? - [ ] Empty states designs - [ ] Consider multilingual search results when there are no results and multiple languages are set in the app - [ ] Consider increasing affordance when there are results in other languages (per @SGautam_WMF’s feedback). - [ ] Experiment with positioning and order of search results source icon: left, right, on the image (per @rho’s [feedback](https://drive.google.com/file/d/1g3RyCY4pwdlBZTyPYqQhJwu7FO6cJq-G/edit?disco=AAAAGwgTdWg)) - [ ] Consider a separate view for `History` (per @rho’s [feedback](https://drive.google.com/file/d/1g3RyCY4pwdlBZTyPYqQhJwu7FO6cJq-G/edit?disco=AAAAGwgTdS8)) - [ ] `Magic words` to trigger functionalities (per @alexhollender’s [feedback](https://phabricator.wikimedia.org/T256819#6362249)) - [ ] Consider search bar below app bar title for `My lists` (per @carolyn’s [feedback](https://drive.google.com/file/d/1g3RyCY4pwdlBZTyPYqQhJwu7FO6cJq-G/edit?disco=AAAAKDt2rWs))

### Analytics questions in regards to search usage[👉 Kickoff slide deck](https://drive.google.com/file/d/1g3RyCY4pwdlBZTyPYqQhJwu7FO6cJq-G/view) #### 01) Do we have any insights on where users are searching from in the app? There are three possible origins:--- ## What are the problems we are trying to solve? 1. Explore search bar below Wikipedia 2**Inconsistency:** The current search experience in the app is not inconsistent and misleading for users. - Search in `Explore` via search bar or magnifier glass leads users to the global search. Explore search icon at top rightSearch in `Article` works the same way. 3.- Search in `My lists` searches list names and articles in lists (T188333). - Search in `History` searches the users history. Even though the search scope and functionality is different, Article search icon at top rightthe iconography that is used remains the same. This is the only insight I have in regards to search usage so far: F319513192. **Reachability:** Search is the most used feature in the app, but it’s physically one of the hardest/furthest to reach on a touch device. The search bar on Explore is positioned in the top area of the device and the icon/button is positioned in the app bar. It says that ~ 28% from all page views are coming from internal search3. **Intelligence:** The current search experience is limited in its capability to suggest relevant results for the user. It does not include results from `My lists`, but not which one exactly.`History`, Dmitry pulled this data back in April 2019`Open tabs` and `Other languages` that are set in the app. **👉 This data will be used to revise the information architecture of the app → where do we show search?**## What are the goals? #### 02) What percentage of search queries end up with zero results? #### 03) Do empty results stand in direct correlation with having set multiple languages in the app? **Hypothesis:** People are looking for something with the wrong language filter enabled. The more languages set, the more likely it it is to get no results.- Search becomes consistent, intelligent, and easier to reach. - Internal search usage increases [from 27% to 30%](https://phabricator.wikimedia.org/F31951319) A simple split for this data would be great. E.g. 1 app language set → 2% no results, 2 app languages set → 3% no results, 3 app languages set → 3% no results.## Scope of the task **👉 Data from 02) and 03) will be used to revise the design for empty state.**This task is not about trying to alternate the existing server side search algorithm used in the app. It is about finding ways to improve the search experience on the client side. --- Adding @SNowick_WMF’s email reply here for the sake of completion## Optimization in three steps: 1. Clearly communicate the **scope of a search**. 2. Make search **easier to reach and use**. 3. Present **more relevant search results**. 👉 Check out the subtasks for details. ### Todos > We have a Schema that tracks users search within the app: https://meta.wikimedia.org/wiki/Schema:MobileWikiAppSearch that I can get data from- [x] Create slide deck ([PDF](https://drive.google.com/file/d/1g3RyCY4pwdlBZTyPYqQhJwu7FO6cJq-G/view)) - [x] Gather feedback from Android and Design team - [x] Talk to Alex about process for Desktop Refresh Search - [x] Talk to Sudhanshu about search in emerging markets - [x] Create proposal for an improved search based on initial feedback from Android and Design (T259717) - [x] Create proposal for an improved article search experience based on initial feedback from Android and Design (T259795) (per @Pginer-WMF’s [feedback](https://drive.google.com/file/d/1g3RyCY4pwdlBZTyPYqQhJwu7FO6cJq-G/edit?disco=AAAAKC5X9ME)) - [x] Create task for analytics questions in regards to search (T259883) - [x] Send out draft for first proposals - [ ] Gather feedback on first proposals - [ ] What happens when results overlap e.g. That has a `source` field: "The source from which the Search interface was invoked: 0 - Main article toolbar,`My lists` and `History` ? 1 - WidgeIs it only shown once? - [ ] Empty states designs - [ ] Consider multilingual search results when there are no results and multiple languages are set in the app - [ ] Consider increasing affordance when there are results in other languages (per @SGautam_WMF’s feedback). - [ ] Experiment with positioning and order of search results source icon: left, 2 - Share intentright, 3 - Process-text intent, 4 - Floating search bar in the feed, 5 - Voice search query."on the image (per @rho’s [feedback](https://drive.google.com/file/d/1g3RyCY4pwdlBZTyPYqQhJwu7FO6cJq-G/edit?disco=AAAAGwgTdWg)) - [ ] Consider a separate view for `History` (per @rho’s [feedback](https://drive.google.com/file/d/1g3RyCY4pwdlBZTyPYqQhJwu7FO6cJq-G/edit?disco=AAAAGwgTdS8)) - [ ] `Magic words` to trigger functionalities (per @alexhollender’s [feedback](https://phabricator.wikimedia.org/T256819#6362249)) - [ ] Consider search bar below app bar title for `My lists` (per @carolyn’s [feedback](https://drive.google.com/file/d/1g3RyCY4pwdlBZTyPYqQhJwu7FO6cJq-G/edit?disco=AAAAKDt2rWs))