DataFields : 367 RunFields

Update 2015-09-15

Have started to upload V2 of the 367Bike and RunFields to the App store.
367BikeFields is Live.
367RunFields is Live

The new version adds TimerTime, also adds the seconds on the timer once you reach > 1hr. (I'm told that seeing seconds is especially important for runners)

Note for all : Please refer to the app store for the latest in the NEW direction the app/datafield is going.
Go PRO! GO UnLimited!!

TOD (Time Of Day)
Timer Time
Pace 10s / Current Speed (in KM or Miles)
Cad
HR
Dist (either Miles or KM)
Avg Pace / Avg Speed

Nikeow over 10 years ago

The "simpledatafield" is pretty simple actually. Very easy actually.
The Datafield is more complicated where you really need to write everything.

For reference source codes, you can find some on GitHUb. (search using keyword --> extension:mc using)

The one I've released, supports Vivoactive - but since I do not have an actual HW, I'm not sure how small it looks. The screen real-estate is limited. (unless you remove the Labelling then you can have a slightly bigger font size for the data. Based on what someone here has tested, you can get up to 6 fields on the vivoactive right now. (even tho I've designed it such that you can get 9 fields in total on the vivoactive - there is a 2 field limitation for ConnectIQ Datafields - so you get a max of 6)

Refer to screenshot on the app page as well as on this forum thread.

Each project usually takes me a week+. (slow coder I know..)

chloe2 over 10 years ago

Went running with this app - great job! You picked the perfect set of data to display.

I was thinking it would have been cool if Garmin or someone would have released an iPhone/Android App that would allow someone to choose 7 fields to display and let one organize those on the iPhone.Android device and then send it to the watch (in my case the Fenix 3).

Since the above is not available what you have done is exactly what I was looking for and it is working great. Only time I notice some running pace anomaly is when I turned around after 2.5 miles (pace was a little odd - same with regular watch so I know it is nothing to do with the 10s pace ....) otherwise I liked it better than the normal watch pace.

Great job!!!!

Nikeow over 10 years ago

I'm inclined to remove support for the VA. People are leaving bad reviews and not posting here.
Additionally , is it me or somehow based on what I've read in the forums - majority of the low rate reviews are coming from VA users.

Former Member over 10 years ago

Please don't remove support for the VA. I went running yesterday for the first time with your datafield in the second row, so that I got the values I'm interested in. And it worked flawlessly!

very happy with it now.
Thanks,
Manuel

Nikeow over 10 years ago

What FW are you on?
I have DigiDad and u who are successful users. DigiDad is on 2.7

The poor review one (tho it's the BikeField 1 but essentially the code is the same) is on 2.8. There is a person on 2.7 and he/she seems to have a positive experience too.

Thanks!

Former Member over 10 years ago

2.80 as well

Former Member over 10 years ago

2.80 as well

Yes, please go on giving support for va. It works well.

DigiDAD over 10 years ago

What FW are you on?
I have DigiDad and u who are successful users. DigiDad is on 2.7

The poor review one (tho it's the BikeField 1 but essentially the code is the same) is on 2.8. There is a person on 2.7 and he/she seems to have a positive experience too.

Thanks!

I am on 2.80 now and running fine.

Nikeow over 10 years ago

Thanks all.. Then how come some users (the 3 specifically that left reviews on the BikeField datafield app page) seems to have issues.

This is inherently weird.

ftw037 over 10 years ago

I'm loving this 6 fields-on-one-page option for Cycling. Shows everything I want, all on one page. Thanks!

My only suggestion is to have 12 hour time of day, rather than 24 hour. But that's an extremely minor quibble. Loving it!