Your feedback really helps make the app better!

You can use the Send feedback link in the Settings menu if you just want to leave feedback or a suggestion – I can’t answer questions sent that way but it’s great if you just want to make a comment. 

If you need an answer or you’d like to ask for suggestions from other cycle.travel users, use our forum.

Bugs or crashes?

If the app crashes or freezes, this is a bad thing (that goes without saying, really). I’d love to hear about this so I can fix it.

If possible, please let me know exactly what you were doing when the app crashed. For example, “planning a route from Oakham to Melton Mowbray by long-pressing each location on the map in turn”. If I can follow these instructions and reproduce the crash, it’s much more likely that I can fix it.

Please also say what model of phone you were using and, if you know, the version of the operating system. Whenever Apple or Google release a new version of the operating system, lots of things change under the hood and it’s not uncommon that this causes apps to break.

Ideas?

If you’ve got an idea for something that would make the app better or easier to use, let me know – the forum is a great place to post these.

Here are a few of the things I’m planning to work on soon:

• Better support for circular/loop routes
• User-editable notes for via points
• Turn-by-turn improvements on complex urban cycleways
• Undo button for route edits
• Offline contours and hill-shading (for supporters)
• Improvements to sketch mode (for supporters)

I’m sometimes asked for extra routing options (e.g. ‘avoid hills’ or ‘tolerate busy roads’). cycle.travel’s route-planning engine works in a way that means these aren’t really possible, I’m afraid, at least without vast expense on new servers. It’s the trade-off for fast calculation times and draggable routes.