Comment by eschatology

You gotta add debouncing or disable the button(s) once clicked and are pending for results; got several email codes and random errors because I clicked again thinking the button(s) didn’t work

Adding a sample trip might help a lot to give an idea of how to use it.

Inputs feel tedious and not smart enough; so much that it feels to get in the way instead of helping.

Activity date input shouldn’t be free date input; I inputted the start and end date earlier, couldn’t that be used to help limit the input range? End date/time feels tedious as well, it could be a duration input instead (eg 3h at this location).

It also lacks some extra planning features, like pooling the list of locations to visit (no dates yet), for later to be scheduled if it ends up interesting.

Personally I would remain using Wanderlog..