what might be a meaningfull usecase? what might be a other solution to get waypoints on the watch, to utilize their coordinates for different calculations?
Again, they can be used in native activities/ Look at something like "run" and the options for course and navigation.
I first looked at getting the location of native waypoints about a decade ago, and in my CIQ apps. I save my own waypoints so I can do things like show them on a map, calculate distance, etc.
On newer devices if there's a textual input then it offers to use the keyboard in the Garmin Connect phone app. I'm not sure if there's a way to activate this remote keyboard from CIQ apps, but it might be possible
yep - but in this case, what might be a comfortable way to enter waypoint names and coordinates?
It would probably be more user-friendly for people to select locations in a website or app, then sync them with your watch with some kind of name that uniquely identifies them.
Ofc you serve both the content (e.g. FIT file) and metadata from your server and tie them together using the unique name.
As others have pointed out, it's kind of a problem that the PersistedContent id can change and that the name() function only returns the first 32 characters. Other devs have apparently worked around this by setting the first part of the name to a unique ID (which probably looks weird in the watch UI).
Then again if you don't need to use those locations with native activities, then you don't need to use persistedcontent at all.
