Talk:Beta Features/Nearby Pages/Design

While discussing the design please mention the screenshot number and comment number for ease of reference.

Previous page history was archived for backup purposes at Talk:Beta Features/Nearby Pages/Design/LQT Archive 1 on 2015-06-25.

Questions - What happens when I click on a list element? Target URL is the same window or new window?

Behavioral feedback -

• List view is a good start point and provides a rational view. People will use this feature to scan a list of nearby articles and pick one, open it a new tab and read it.
• I can also see nearby as an rich and contained browsing experience. Adding the ability to switch to a richer view such as an image flow - (maybe even use hovercards) so as a user I can browse through a bunch of nearby articles in a more stable persistent right pane (instead on an overlay) would be interesting.

Larger Conceptual feedback for the future - Something about this current concept feels forced. On Desktop, I see Location as a lens on a Wikipedia Article. A different and more specific narrative of the same information. What if this panel carried -

• 'Locations relevant to this article',
• 'Locations mentioned in this article'

Instead of nearby? The interface you have can be used as a filter or a lens in addition to Nearby.

1. I think its right to deemphasis search and current location if the article has a location. We might want to have a call to action for "improve location" or "update location"
2. When an article doesn't have have a location we should go straight to to the submit location flow, using the article name as an initial search query (silently in the background, and not show it) might be a useful start.
3. I'm not sure of the value of collapsing the map inside the flyout, a collapsible region inside of a collapsible region seems like an awkward experience for users.
4. The text blurbs are big, we might want to consider less text, at a larger size, and larger leading, to make it less dense.
5. lets treat full screen mode as a stretch goal, I don't think it needs to be part of the initial re-release.
6. we need a way for a user to say "this article isn't a place/doesn't need a location" and maybe deemphasize or remove the geo marker in the future for that article.
7. I'd love to see at least one variation where we use the push style edge menu, and take up the full vertical height of the browser.

Needed: actual users flows, these can be simple wireframes, but start points, end points, error states, etc.

1. That makes sense. Do you think there will ever be a use case for Search/Current location?
2. Right, if there are no coordinates we will go straight to that flow. I'll ask Jdlrobson if the search thing would be possible.
3. True, this needs polish. But we do need this as some users might want to opt-out of the map completely (due to slower connections etc.) and this is a preference that we'll store. (see Jdlrobson's first comment in his feedback)
4. Will do this in the next iteration
5. Will do this in the next iteration
6. There is one already (see [C](a) in the table)! Do you want me to update it incorporating the new feedback?

1. not sure what you're asking exactly, I think search should always be available, but emphasised more or less depending on if the article already has location or not.
3. This seems like a weird case to me "I want to interact with location based things, but don't want to see a map" I think we can safely assume this is not a use case unless users ask for it.
6. sort of, I don't expect it to cover page content but rather push it over, I'd expect that I could open it and leave it open as I moved from page to page (perhaps)

feedback on variation E Mapped article

1. Nice touch with the masked pokey like the hovercards
2. I think we can kill the blue text, esp. since the entire row is a target, no need to call out the titles that much
3. search seems to have gone missing from the default view, even if it isn't a huge focus it should probably still be present, maybe a subtle simple search bar, or…
4. turn the results row into a search, UI, prepopulated with the current region, "Near New York"
5. the current article isn't represented on the map as the centerpoint, or if it is, its not

clear

Unmapped article

1. That is a LOT of text, we need to trim that down to at least half that, how about…

Contribute a location for this article Search, zoom, or pan to the location on the map then drop a pin

1. we can kill the license/TOS text, its not needed for geoloc contribs
2. we can de emphasize the "this page is not about a place" and make it more subtle, grey, non-underlined text (also shorter!)
3. again, maybe a simple always there search box integrated between the map and text box could work here as well, with prompt text "Search for a location"
4. I think we can kill the grey box across the bottom
5. maybe we don't even need a confirm button at the bottom? auto-save and provide and undo/cancel once a pin has been placed or moved?

Drawer

1. No soft shadows! :)
2. We could do a hard transparent shadow, but I think it would make sense to inverse, e.g. the article cast a shadow on the drawer, not vice versa
3. Most sites use an icon for "use current location" we might want to use the same pattern here.
4. big maps is cool

Great start, Prateek! Some quick ideas:

1. Maybe add an excerpt or category (on the list) for each item on the list
2. On hover, you can show the marker on the list as well
3. Copy, interaction and placing the marker should be thought out a bit more
4. Think more about the "Search Map" inside the map (might be confused with zoom because of the icon). Maybe put it somewhere else?
5. "Use current location" should probably go on the map
6. I don't like the edge menu layout :(

I've incorporated your feedback in the new design iteration D. I will look into the edge menu later. Let me know what you think!

Some more feedback:

1. Hide/Show map link could be a little subtle.
2. Add ellipses to text extracts.
3. Move the marker on hover somewhere other than the photo. Maybe besides the name.
4. Maybe the full map thing could take only half the screen? That is probably more than enough.
5. Make the page title color blue in the list, to indicate that its a link.
6. Idea: Maybe users could rank POIs?

Do a few quick wireframe sketches for the workflow of the following use cases:

1. Someone goes to New York article and want to find places nearby
2. Someone goes to a page like "Car" that does NOT have location and should be able to say that there is no location needed on this article.
3. Someone goes to "Chicago" but can't find it on the map and then adds it to the map.
4. Someone wants a big map and explore Wikipedia through geodata

Some ideas:

• Make it possible to collapse / expand the map and remember that setting - if a user has collapsed it don't run the code to generate the map on future loads .
• A full screen mode would be great (especially when trying to add a location)
• You can add location by appending wikitext in a save.
• In the cases of pages without a location show the world map - showing anything more accurate is probably too difficult.
• The edge menu would be interesting if it appeared within the article content - maybe in a right gutter which pushes the article content to the left - this would also help with the Typography Refresh !.

I've incorporated your feedback in the new design iteration D. I will look into the edge menu later. Let me know what you think!