Due to an other upcoming discussion I add some new points here instead of creating a new thread:
Handling Garmin specific extensions in GPX import to differ ViaPoints from ShapingPoints might be a benefit also for users who do not use any Garmin device, because a lot of GPX you can download in the web use that format.
Furthermore other applications use those Garmin extensions to differ ViaPoints from ShapingPoints (eg. Motoroute, MyRouteApp ).
On the other hand some applications use a type tag (eg. Kurviger app 
), or waypoint symbols to differ Via- from ShapingPoints.
Probably it is not useful to implement several import strategies depending on GPX creator, but from my point of view following priorities (1 = highest, 3 = lowest) could be an generic approach:
- Start and destination are ViaPoints (of course)
- if Garmin extensions are in GPX, use them
- if type definitions are in waypoints (like in Kurviger App export), use them
- if symbols are defined for waypoints, use them
I’am not sure, if it is necessary to implement such a detection in both Versions (web + app), at least if a user has both subscriptions it would be possible to do the import in web - but on a mobile phone it might be much more comfortable to use the app directly.