On the topic of wattage, it's a big reason people have smart trainers so we plan to show it in our HUD soon.
We've also begun having this conversation about Spins together with Kinetic. Spins are fair for cadence measurement, but speed sensors and most smart trainers don't measure Spins directly (although the CycleOps Magnus does!). Also when we add varying resistance up and down hills, instead of varying speed like we do now, that could have a different net effect on Spins. Energy would be the equivalent accumulated metric from wattage, but that would be less meaningful to estimate from cadence sensors (and is one reason that more serious programs like Zwift don't support _only_ having a cadence sensor).
What we are batting around is going back to our old metric of "virtual kilometers", or "vkm" for short. It was an equivalent distance of riding over flat terrain at an average level of resistance, that we were calculating from our bike & sensor's crank speed. But Spins was a much more direct representation of crank rotations, and vkm could be confused with the distance you actually travel in our games, which can be wildly different depending on your avatar and other constraints.
But now with the addition of speed sensors, power meters, and smart trainers we think it might be the most fair "total" metric for all VZfit users. And because it's a fitness metric and not actual distance, hopefully people will be fine with keeping it km rather than miles, because "vm" would be a much less recognizable shorthand.
We've also begun having this conversation about Spins together with Kinetic. Spins are fair for cadence measurement, but speed sensors and most smart trainers don't measure Spins directly (although the CycleOps Magnus does!). Also when we add varying resistance up and down hills, instead of varying speed like we do now, that could have a different net effect on Spins. Energy would be the equivalent accumulated metric from wattage, but that would be less meaningful to estimate from cadence sensors (and is one reason that more serious programs like Zwift don't support _only_ having a cadence sensor).
What we are batting around is going back to our old metric of "virtual kilometers", or "vkm" for short. It was an equivalent distance of riding over flat terrain at an average level of resistance, that we were calculating from our bike & sensor's crank speed. But Spins was a much more direct representation of crank rotations, and vkm could be confused with the distance you actually travel in our games, which can be wildly different depending on your avatar and other constraints.
But now with the addition of speed sensors, power meters, and smart trainers we think it might be the most fair "total" metric for all VZfit users. And because it's a fitness metric and not actual distance, hopefully people will be fine with keeping it km rather than miles, because "vm" would be a much less recognizable shorthand.