Pretty much every other ride tracking app provides users with a means to delete or discard a ride. I've given you a potential UX design (above) and proposed a data loss prevention solution (move the ride into a Deleted Rides container for 30 days). Trouble is, if you hold it down for a little bit too long, the unit will reboot which is another undesirable consequence of this.Īll I want to do is discard a ride. You still have to go into the Rides app and manually delete it from there (swipe and confirm).Īlso, quitting the Rides app by holding down button D seems a bit extreme as well. In any case, pressing the bottom left button (instead of Upload on the final step) still saves the ride to Hammerhead so it doesn't solve the problem entirely. I should not have to explore various button presses in order to figure this out for myself. My issue with the current workflow is that it forces the user down the path of saving the activity, regardless of whether or not they actually want to save the activity. I would also expect to see this "Deleted Rides" container made accessible from the Dashboard so that users can restore deleted rides from there as well. If a ride is deleted, then it should not be uploaded to any of the connected services until it is moved out of that container. I see a few people saying that they have had to delete "desk" rides from Strava because they have accidentally uploaded them. My thinking with this is that deleted rides would not be uploaded to connected services until they are moved out of the deleted rides container.
Have you considered implementing a "Deleted Rides" container that gets purged every 30 days or so? That way, even if rides are accidentally (or deliberately) deleted, they can still be recovered within a given period of time. I understand there is some concern about data loss and new users accidentally deleting rides. This request seems to be gaining a lot more traction lately and it would be good to see some movement from Hammerhead in an upcoming release.
0 kommentar(er)
