Edge case 1:
What happens when a user is between two neighborhoods?
Imagine that a user is right on the border between the Mission and the Castro districts in San Francisco. What would the user see when searching 'Nearby?' Would the user see articles only related to the Mission, or would the user also see articles related to the Castro? Would the user receive any information that he or she was between two neighborhood or not?
When designing for these considerations, I realized that there wasn't necessarily one 'right' way to do it. It was important for me to identify tradeoffs and design with the user in mind.
I decided it was important for the user to receive articles from other neighborhoods that were in close proximity to the user's location because this is how users would (and people in general) understand their physical surroundings. People don't see neighborhoods as strict zones but instead as a continuous landscape connected (oftentimes) by ambiguous boundaries. I mocked up a quick wireframe and then high fidelity model of how I would design for this edge case.
Edge case 2:
What happens when a 'Nearby' article is not accurate to a user's location?
Imagine that a user has activated the new 'Nearby' feature on Medium's iOS app and realizes that the article that they are reading is not accurate to their location. "That's weird..." a user might think. How might the user do something about this so he/she and other users won't see this type of inaccurate article again?
I decided it would be best to allow the user to flag the article. Ideally, the employees at Medium would be notified, review the flag and make a decision to either keep or move the flagged article.
These are quick sketches of what flagging a post might look like: