@Andrew Heard : if you start "edit on map" from list of tracks, then why start point is better then some in the middle or in the end? So I see nothing logical on pre-selecting just the first point. Try to start this "edit" directly from the map to see difference.
About via-points - if you add new point during planning, it is not considered as "via point", just a "helping track point". If you wants to create a permanent via-point, try to tap on green dot once again. This creates real via-point that will be kept in track, visible in list of points and also used during navigation for notification or re-calculation.
I am editing track from the map, not a list. I am pointing out the left/ right buttons start differently to existing pro behaviour. Existing behaviour is for tapped point to be selected, and therefore, generally, both buttons are enabled. Beta behaviour is for tapped point to be ignored.
As discussed before there needs to be better distinction between a green icon helping point and its converted blue? Via point. Currently almost impossible to tell the difference - shape, better colour, size?
If I edit this new track on the map I can long-tap to edit/ move the point (not always?), but from waypoint list there is an error message that point can't be edited?
How about long-tap on point to display same menu as tapping Tool button? Would be faster in lots of situations.
Maybe instead of further menu level Edit/insert > select point yet again, the Tool menu has separate items for Move/ Insert/ Delete?
Seems named via point is lost if edited and moved?
Moving, deleting points, a simple operation, just takes far too many taps. Surely long-tap point > menu > Delete? And if undo facility provided then no need for confirming each and every operation.
Each recompute is taking a very long time too. Just with simple test track.
Just a few long-winded thoughts to speed up editing and make more intuitive? Could there be a workflow "conflict" between users with short tracks wanting very precise control over placement of all points, and users with long tracks that rely mostly on compute source, and just want to steer in right direction is iniial route needs broad adjustment?