Swarm City app is an interface that allows people to get goods and services in the real world. That is why sometimes it's relevant for a user to share their location range.
How it could work:
When creating a new request, the default location range is set to "worldwide". If the user specifies a smaller range, the client checks if the browser's location services are enabled.
If not, a screen appears asking the user to allow sharing of the device's location with the client, so the front-end can add the chosen geohash to the request.
On view /new-request (A), when the user moves the slider without the location services enabled, the view changes to /location (B).
The /location (B) contains:
copy: "Can we ask for your location?"
copy: "By accepting, your browser will enable location services."
black x-mark (cancel-button)
big white button with blue V-mark (confirm-button)
When the user taps the black X-mark (cancel-button), the process is aborted and the view changes back to /new-request, with the inputs still filled in.
When the user confirms by tapping the blue V-mark (confirm-button), the view changes back to /new-request, with the slider now fully movable. When the location remains unknown, the only option is worlwide, not specifying the location at all.
The slider determines the geo-location.
Moving towards the globe-icon will increase the size of the area.
Moving towards the location-icon will decrease size of the area.
When the slider has a new value of (distance), the copy above the slider changes instantly (while still sliding). The user sees the distance in a more human expression:
Abstract:
Swarm City app is an interface that allows people to get goods and services in the real world. That is why sometimes it's relevant for a user to share their location range.
How it could work:
When creating a new request, the default location range is set to "worldwide". If the user specifies a smaller range, the client checks if the browser's location services are enabled.
If not, a screen appears asking the user to allow sharing of the device's location with the client, so the front-end can add the chosen geohash to the request.
What it looks like:
Userflow: https://invis.io/ABGM89SX3V5#/293522260_FRANK_-new-Request_SLIDER_I ( > in Invision, hold shift to see clickable areas)
routes: /new-request and /location
On view /new-request (A), when the user moves the slider without the location services enabled, the view changes to /location (B).
The /location (B) contains:
When the user taps the black X-mark (cancel-button), the process is aborted and the view changes back to /new-request, with the inputs still filled in.
When the user confirms by tapping the blue V-mark (confirm-button), the view changes back to /new-request, with the slider now fully movable. When the location remains unknown, the only option is worlwide, not specifying the location at all.
The slider determines the geo-location.
When the slider has a new value of (distance), the copy above the slider changes instantly (while still sliding). The user sees the distance in a more human expression:
Desktop view:
Invisionlinks with login (for inspect mode!): mobile: https://projects.invisionapp.com/d/main#/console/13838256/293522260/inspect desktop: https://projects.invisionapp.com/d/main#/console/14147648/294446452/inspect
With ♡ from Swarm City