Hi. The more I read and think I agree with Robin, not to implement this edit: at once. I had also to think why this 5-digit to share feels like a workaround and it would not solve the usecase I have in my mind.
The initial question was how to consume the link as easy as possible. If Chrome has opened the link as the Samsung browser we would have had no question and no discussion at all. And we have discussed a lot of possibilities to consume the link, perhaps not in the way we used it in K2. So it is not completely broken, perhaps a little bit weird by writing in in my own messager, so I get a clickable link. Two times a year. At least for me no showstopper and absolute no emotions.
Then the first posts, we talked about Tourcodes and “kurv.gr” links.
The kurv.gr is in the end just a service, that shortens a long URL, like any other service in the internet that shortens URL´s. Input is long URL, output is short URL, but still an URL. So I fully understand Robin, when he says - please use it as an URL and share the URL.
As it has currently(!) 5 digits, some used it for communication on paper. But it is not the usecase of a link to share only a part of it. You do not even have control over this link, you cannot change or delete it. What if the links are deleted after x months? Never promised to keep it a lifetime.
The other thing, why it feels to me like a workaround, is that with every change of the route, the just shared link is old, and I would have to say to everybody “Sorry, I changed the route, please enter this new 5-digit-code”. Not comfortable.
Rough idea - hopefully not totally bad.
I would extend the usecase to “I want to share MY route with many other ONCE. I want to share it also anonymous users. I want to share the the route already X days/months before the tour starts. When I make changes on MY route, and the partner loads the route again, he should get the most current route. When a route is changed on the tour (tour must be changed because you invited me and I am too slow), all users that have currently the route loaded should get an update message (e.g. when the navigation is started or other event; or I call loud they should please reload the route). The code should be easy to enter as the normal Tourcodes. I can create, change and even delete MY route so that it is not available anymore.”
In my mind this is just the behaviour of a Tourcode plus additional functionalities with the cloud. Perhaps vice versa a link with a tourcode can be build. Share the tourcode now for the tour next summer by email and you are done.
Example:
Route “BlackForest032023” links to tourcode toffel/SUMMER2023 and every change of the route is linked.
And all who rely on the 5-digit of the link can (mis-?)use it as in the past.