Closed bradfloodx closed 11 months ago
Geolocation service installed ready for basic user flow testing at http://therevivalfellowship.com/dev/public/
List all
is probably the path of least resistance.
Here's some more options to be considered:
Search
by typing in a postcode, city, or state. We'd need to know the geolocation of what they've entered (not easy). We could then show the closest 3 results within a range?I think a lot of people would have their location blocked so it would be valuable having a good "workaround" here..
Here is a mock of the failed message. I don't mind if it's either a 4 second box which disappears to reveal the original buttons or if it appears above the buttons and disappears after 8 seconds. What are the permiations that we can define for a failed message? Might be easier to just be vague for all: "Your location wasn't provided, please browse our list of fellowships"?
Just realised I didn't add a mobile version... I'll have a look at that tomorrow as the blue box wouldn't work in the same way for mobile... :/
Good ideas @supertravio .
Re design @danielmee I'll just improvise something for now, and yes just one error message is easiest. Let's see how we go after launch.
Once a user clicks
Use current location
the Geolocation service will initiate the location request to the user's browser and they will be promptedYes
/No
IF their browser is configured to prompt.Browsers can be configured to auto
yes
or autono
.If
yes
obviously we locate the closest fellowship and display that to them, no problem.If
no
what should happen? I feel like some sort of message should be displayed informing them of our inability to retrieve their location, due to their rejection of our request slash their security settings. They could then be presented with a button toList all
.Thoughts?