UI Experience Suggestions

Here are a suggestions, many should be easy to implement...

1. If you are interacting with the UI, a segment can pop up and disrupt whatever you are doing. This should not happen! Wait until the interaction is complete, or use an alternate notification that doesn't simply jump to the segment screen.
2. In some circumstances, you can dismiss a segment only to have it up pop again, and in some cases multiple times. If a segment is dismissed, there should be some kind of cool-down before it can be triggered again.
3. The "phone battery is low" warning shows up way too much. Does it need to pop up every 1%? The garmin low battery only shows up once! If you dismiss the alert, don't show it for another 5% or something. Then below 5% show it every 1%.
4. Weather alerts need some rethinking. Some alerts, like tornado, storms, etc are short-lived and helpful. However, others are "long lived" (such as flooding) and may be active for days or weeks and can pop up over and over on a ride.
5. Someone had the neat idea to give sensors a red icon if their battery is low. Take it one step further - remind me when I power the unit down. Also put a notification on my phone via the connect app about low batteries in my garmin, power meter, di2 or whatever so I'll remember to address it.
6. Why can't we put something more on the single-tap screen? It's a big, blank semi-transparent overlay; seems like a waste of space.
7. Backlight warning. One tenet of alarm management is that an alarm should NEVER be triggered directly by a user action - he meant to do that, don't set off an alarm. I feel the same way here. I don't need a nanny reminder that this will reduce battery life. However, I do need a reminder to turn it back off - when powering up the unit, ask me if I want to disable the backlight. (also please implement the automatic night-time always on backlight!!!!)
8. When a distance field is full-width, include two decimal places for values over 100. I'd honestly like to see all fields with decimals show two when full width. I'm always curious if average speed is rounded up or truncated to one decimal place.
9. One-screen alert timeouts seem too long before they disappear -- especially the full-screen alerts, they take FOREVER.
10. No alert should ever obscure an in-progress segment screen. Defer until it's over please.
11. Allow removal of the graphic from the segment and to add more data fields.
12. Create additional segment-related fields, such as:
    1. current segment average speed
    2. average speed for segment goal (for comparing with your current average). Knowing "how fast I need to go" is much more helpful than "how much time I have to do it", especially on shorter segments. Our brains are pretty terrible at estimating time.
    3. speed required for remainder of segment to beat current goal, for pacing. Example, a 1 mile segment with a KOM @ 25, I have gone 0.5 miles at 24, so I need to average over 26 for the remaining 0.5 miles. A nice joke would be to put a frowny face in the field if the required speed is over some large value... Or just empty, for safety reasons!
    4. multiple target-specific time ahead/behind for XOM, PR, carrot, whatever (all the possible targets)
    5. Segment elapsed time, and "time left to beat goal" (e.g., goal - elapsed = time left)
    6. Alternatively, improve connectIQ so it has access to things like the active segment and corresponding data and these could be custom fields created by users.