Application: dwMap - Route Maps for Vivoactive and other watches

I have just published a route map app, dwApp, which I hope will fill a hole in the Connect IQ ecosystem.
Download from App Store

The primary goal was to offer a route map display and follow capability on the Vivoactive. The app however works on all Connect IQ devices and should be an very convenient way to send a route to the watch after creating it in MapMyRun, Ride with GPS, etc. It also offers an activity recording capability while you are using the routing feature.

I look forward to your requests, feedback, questions and bug reports, in this thread!

Features
- Uses a link code mechanism to link your watch to your account on http://dynamic.watch
- Your dynamic.watch account can be linked to Ride with GPS and Under Armour (MapMyRun/MapMyRide) to import routes automatically from those accounts, or you can import GPX and Garmin Connect routes
- Indicate which route is your current route, and you watch will automatically download it next time you start the app
- App displays a map view or a dashboard (data fields) view
- Map view has three zoom levels, and shows you current position and direction
- Dashboard view shows speed, distance, HR and other common activity stats
- App uses the normal built-in recording capability of the watch, and when you stop and save the activity it is sync'ed with Garmin Connect in the usual way
- App works without a data/phone connection, using the most recently downloaded route when offline

Former Member over 6 years ago

I'm sure this has been asked before but on my Fenix 5 watch, how do I discard a route without saving it. When I get to the screen that says Save and Exit I get yes or no, if I select no it returns to the paused route screen. Thanks

mappicus over 6 years ago

I'm sure this has been asked before but on my Fenix 5 watch, how do I discard a route without saving it. When I get to the screen that says Save and Exit I get yes or no, if I select no it returns to the paused route screen. Thanks

This is a deliberate choice in the user interface for dwMap. We wanted to eliminate the chance that a user can inadvertently exit an activity without saving, but, since we are extremely short of memory on the watch, we did not want to add extra code to add a confirmation step. We understand that users can find this inconvenient when they are first trying and testing the app, but quickly get used to it when they are using it normally. The unwanted activity can, of course, be deleted later in History and/or Garmin Connect.

Former Member over 6 years ago

This is a deliberate choice in the user interface for dwMap. We wanted to eliminate the chance that a user can inadvertently exit an activity without saving, but, since we are extremely short of memory on the watch, we did not want to add extra code to add a confirmation step. We understand that users can find this inconvenient when they are first trying and testing the app, but quickly get used to it when they are using it normally. The unwanted activity can, of course, be deleted later in History and/or Garmin Connect.

ah, that makes sense and many thanks for the clarification. Keep up the great work.

Thank you :)