hasgeek/hasjob

Location prompt is occasionally wrong, offers no recourse

jace opened this issue · 4 comments

jace commented

BSNL 3G in Bangalore is currently showing this on the homepage:

screen shot 2016-11-16 at 10 59 24 am

This is incorrect and grates on the user, but there is no way for the user to do anything about it, whether reporting the error or dismissing it. These options should be included:

  1. An additional button with a different colour: "Not in "
  2. An additional form that drops down with an explanation: "Our apologies, IP-based location isn't always accurate. Button: Detect location" (using geolocation API)
  3. A submission to a reporting backend that submits IP-detected location and browser-detected location. Since the client can't reliably guess its public IP, the backend needs to note that (with the caveat that the IP may have changed by this time)
  4. Offline process for us to report errors to MaxMind's IP database
jace commented

"Locate me" button (for geolocation) should be top-level, not hidden under a prompt.

jace commented

Once the user grants geolocation access, use that automatically next time to find the correct location. Remember the grant via a browser cookie or browser detection.

jace commented

Also, location buttons should indicate how many jobs are available in that location.

jace commented

We need a lat/lon to geoname id lookup service, similar to Maxmind's IP lookup.