cyclestreets / cyclehackney-ios Goto Github PK

If the journey tracking is started then immediately stopped, a valid submission is still possible.

Upon completion of the submission wizard, a map centred south of Royston is shown, showing no GPS trace (obviously, as there isn't anything to show) which is presumably a related bug.

If a trip is auto-completed on the iOS version, it is also auto-saved and put in the trip list to upload later. The data that is then submitted seems then to be fixed as notes="Auto completed Trip", purpose="other", and user details as per the saved profile (though not sure what happens if no profile has been saved).

The user therefore never has the opportunity to give details. I think this is wrong as the purpose of the auto-completion is to deal with the scenario of the user forgetting, rather than per sé to upload things automatically.

Android app by comparison handles this better. If the trip has been autocompleted, upon unlocking the auto-locked phone and opening the app, the questionnaire is immediately visible, requiring the user to enter the details. This seems to me to be the ideal UI and as a user I've found it works well in practice, and is logical as then auto-completed and manually-completed trips are handled consistently.

I don't think there's any good reason for this not to be on by default.

Currently the map view showing the plotted route is zoomed in to a part of the journey.

Instead, it should show the full route, so that the user can have assurance that the full journey was properly captured.

I've noticed that opening the app but not starting a route and then backgrounding it results in the GPS location left active. This could unduly affect battery life.

Basically the GPS pulsing should presumably only be on when the app is either:

1. In the foreground; or
2. Backgrounded planning a route.

I definitely see this as a bug rather than feature request.

We've had a bug report that a user (who deliberately didn't accept the geolocation permission request as they were abroad) got a location in Bavaria when opening the app.

Could this be set to Hackney as the centre-point for the Hackney build.

A suitable location is 13/51.5450/-0.0553.

If a user has refused the OS Geolocation permission, it is possible still to start a journey.

Seems the app has iOS8 compatibility issue(s) that need to be resolved urgently:

We've had this report:

"Unable to end our journeys - you can click on the finish button but nothing happens."

Currently, only the user's current location is shown while tracing routes.

However it would be nice, particularly to reassure the user that tracking is definitely working, if the route that has been achieved so far were drawn out as a line.