Page MenuHomePhabricator

Add geolocation functionality to MobileFrontend to support Articles near me
Closed, ResolvedPublic

Description

Author: hcatlin

Description:
Implement geolocation beta.


Version: unspecified
Severity: enhancement

Details

Reference
bz19920

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:43 PM
bzimport set Reference to bz19920.
bzimport added a subscriber: Unknown Object (MLST).

Why do we want this? We aren't serving any geo located banners.... Seems something most don't want?

bugs wrote:

It was probably fundraising-related. We used to have a donation notice that encouraged people to text WIKI to some number to make a $10 donation. Maybe it showed to everyone who used en.m.wikipedia.org even though only people in the US could donate with that service?

It probably doesn't matter anymore and can be closed since we don't server banners at the moment through the Mobile interface.

While that was one use of geo related data why don't we instead focus this on "Articles near me" functionality. This is one feature that our iOS app has that our website does not. You should not have to have iOS in order to see articles near you.

hcatlin wrote:

This was about geolocation for "Articles near me"...

the donation banner was via an IP lookup for country.

I did want to get this going on the web app, but at the time
it was iOS only. I think now most phones have a location API
for JS.

philinje wrote:

Also a filter may be useful - articles near me without photos. Latest discussion about this is regarding API enhancements to make these sorts of geolocation requests easier. But here we need to look at what is possible on devices via the browser.

This seems very unclear and mixes various things. I'm taking this to mean "port nearby functionality from mobile site to app" and have written a story to capture this
https://mingle.corp.wikimedia.org/projects/mobile/cards/125

Closing as "WONTFIX" (developers do not plan to fix this) to get rid of the deprecated "LATER" resolution and to provide a realistic outlook - unfortunately developer manpower and time is limited, sorry. In case you feel that this really must get fixed your contributed patch is highly welcome.

As the matter, the developers are actively working on infrastructure that would make it happen:)