Create a 'Pace' data type and allow on-device settings changes?

A common aspect of my apps seems to be setting a pace, and the problem being having to manually create that in settings from minutes and a seconds input box. It's not a great customer experience and would really benefit from being able to change it on your device, even mid activity.

If garmin created a 'pace' type that could be used in settings it would allow garmin to create a great CX that all the connect IQ developers using pace, could benefit from.

On top of that there's the opporutnity to get some really easy functions out of a pace type ie pace.getInMetresPerSecond() or similar utility functions.

It would also mean there's a possibility for garmin to create on-device settings changes to allow changes to pace setting for workout apps

jim_m_58 over 6 years ago

I could see a generic "time" type for app settings (as there is for date). As far as the pace type. you could make a barrel and publish that so others that are interested could use it. (and it's easy to use in your own apps)

peterdedecker over 6 years ago

This actually kinda exist natively in means of the virtual partner functionality. It'd be great if the speed setting of the VP was exposed to connect iq as I then could lose a few of my app settings as well. I think a few years ago I actually made this feature suggestion, so someday who knows :)

djhawley over 6 years ago in reply to jim_m_58

I think the greatest value here is the benefit to users in having a better settings UI (in Garmin connect mobile, and on device) so they can set the pace how they'd like (min/km, min/mile, kmh...) so I think those parts would need Garmin's input on it

Right now you have to have a fairly convoluted settings screen to allow users to do that

djhawley over 6 years ago in reply to peterdedecker

exactly! I use my app every day, but all I really do is change my target pace, and having to do that on a phone and sync it seems silly when garmin already have the UI in VP

flowstate over 6 years ago in reply to djhawley

Yeah, it would be really nice to have dedicated time and pace/speed controls in the app settings. There's a lot of things I would like to see changed in the settings, but right now they're pretty basic.

If you have the memory to spare for string parsing, I think one solution could be to have two settings:

Speed/Pace Format [list]: min/km. min/mile, km/h, miles/h
Speed/Pace [string]: e.g. "5:00" (pace) or "6.0" (speed)

In the absence of a dedicated pace or time control, it might be more user-friendly to enter 5:00 as "5:00" instead of "5", "0".

The only problem with the above suggestion is you could have a mismatch between the format and the value -- e.g. the user selects "min/km" but types "6.0" for the value. One way around this could be to:

- Have the format list as: km, miles
- Automatically determine whether the user meant pace or speed based on what they typed

The tough part is explaining all of that to the user, especially because nobody likes to read long text, and long text will be cut off on some platforms anyway (GCM Android, the new CIQ app). And placeholders / help links do not appear on all platforms either (not that you want to rely on those, either.)

One final alternative which might be more user-friendly:

Speed/Pace Units (list): km, miles
Use Pace/Speed (list): Pace, Speed
Pace (e.g. "5:00") [string]
Speed (e.g. "6.0") [numeric]

This way you have:

No possibility of ambiguity/mismatch between pace and speed
Short labels that will render on all platforms
Self-explanatory settings
Pace that's perhaps easier to type / understand than entering two numbers in separate minutes and seconds boxes
Built-in validation for speed

The only thing that's missing is built-in validation for the pace string. But then again, my last suggestion is probably not too different than what you already have.