Built a standalone Ballistic Solver for Garmin: Did I miss anything, or what else should I add to the main screen?

What data would you prioritize on this main screen?

Hi everyone!

As a long-range instructor and developer, I’ve spent the last few months trying to push my Garmin watch to its limits. I was tired of relying on phone apps in the field, so I coded Hort Ballistic — a standalone iterative solver that runs entirely on the wrist.

I’ve implemented the core engine and profiles, but I’m at the stage where I need to decide what additional data is most critical for the main display. I'd love to get your advice.

What’s already under the hood:

• Numerical Integration Solver: 10-meter step trajectory simulation (not a simple lookup table).
• Profiles: Support for 3 Rifles and up to 5 Ammo.
• PRS Quick-Grid: Dedicated mode with 5 customizable distances on one screen.
• Spin Drift: Modeled based on twist rate and direction.
• Manual Environment Entry: I don't trust internal watch sensors for $T$ and $P$ (body heat issues), so weather is fully manual for maximum precision.
• Optics: Global MRAD (MIL) and MOA toggle.
•  

My question to you: What else should I display on the main result screen? I have a bit of space left and I'm debating between:

1. Velocity at Target: To keep an eye on energy.
2. Transonic/Subsonic distance: A warning for when the bullet starts to destabilize.
3. Flight Time: For those who track moving targets.

If you were in the dirt, which of these (or something else entirely) would you want to see at a glance without scrolling?

I really want to make this a "no-brainer" tool for the precision community, so any feedback is more than welcome!