Even worse... 

When I have been creating or editing a route on my tablet and am reviewing it before saving it. I go to scroll the map to the left but place my finger too close to the edge of the screen. The subsequent finger swipe is then interpreted as 'Close App' (WITHOUT SAVING!) rather than as a scroll command. 

I keep doing that and it really annoying! 

I just spotted the cycle.travel/map/mobile option. The bigger map makes it much less likely that I would accidentally swipe the edge of the screen. Turning the tablet to landscape also helps.

Auto-save would still be nice though... 

I will just bump this up because it might have been missed af the time?

I am okay on my tablet now because I turned off gesture control but I like gestures on my phone and still occasionally swipe routes away without saving them.

Actually... I am still finding my part-finished routes being chucked away if I suspend the app for a while and then return. Instead of some roads near Exeter, I found myself back on a blank map of Todmorden!

I obviously could simply manually save before switching apps but it is annoying when I forget.

Remind me (sorry, I should have remembered) - is this iOS or Android?

Oh, er, Android.

But... The same thing happens with the web version on my Chrome browser in Windows!

I would like to be able to stop at any point and on whatever platform, and when I eventually come back everything is as I left it.

I have, myself, lost changes because I closed the wrong tab. (That’s on a desktop browser; I rarely plan routes on the app.)

However, I also like to experiment with route variants, maybe to see if I could stop somewhere along the way, or just to have options on the day. I do that by loading the route and dragging via points around. A naive auto-save would probably cause me more data loss by overwriting my base route.

As with most things, the tricky part here is probably designing the UI!

I think it would have to be a toggle (defaulting to off) set in the user preferences. I’ll add it to the list for the website, but really with any online service I would always encourage you to save early and save often.

The app being suspended is a different issue really (but Android will do what Android will do…!).

Thanks.

I wasn't thinking to save the changes over any pre-saved route - that could be annoying! More a temporary route file which was kept up to date.

I am developing an Android puzzle game. I had the same issue with that so I now do autosaves whenever the app is suspended or closed.