If anyone is interested... here is the 16 slide User Guide to a pretty cool data field I wrote for managing performance for cycling. For executing an ultra-distance non-drafting race, this is a game-changer for me. The keys to maximizing distance, in my experience, from several 24-hour RAAM Qualifier races... are pacing, nutrition, and (minimizing) stop time. Obvious stuff. But keeping on top of those things isn't easy deep into a hard effort. Tracking hydration. Awareness of Total Stop Time. Watching the projected finish line results. Warnings if your HR getting too high, or your cadence slowing too much late in the night. Periodic reminders to drink. Understanding the weather and wind influence. Knowing when the sun is coming back up. When your battery will die if you don't plug it in... All are wonderful data points to watch.
I use a barrel to auto-scale the fonts (some custom) and layouts based on the Device. Peak memory is 114kb, so it only works on newer large memory EDGE devices. Which is fine... most serious cyclists have upgraded by now to at least a 520+. But it works best on an 830 or 1030 class device due to the amount of information.
Slide 15 lists some future possible refinements. Just sharing here in case this gives others some ideas. I don't use any background tasks. However, Slide #15 "Device Temp Override": a possible future feature, would require a BG task.
