Thanks for your feedbacks.
I agree, I never use km/h for running, but some people are requesting that...
It's not a huge work to add it, so I will probably put new metrics for that to mix min/km and km/h on the same screen if they want.
iOS15 and watchOS 8 have added a lot of enhancements in SwiftUI. It makes the code more concise and readable, it brings new features and reduces the gap with UIKit.
It also brings the new Swift concurrency framework to a lot of existing APIs. It can help to make the code easier to maintain.
If it becomes too complex to maintain backward compatibility, I will force upgrade to iOS15/watchOS8.
And iOS16 and watchOS9 are coming in 6 monthes ...
I agree, I never use km/h for running, but some people are requesting that...
It's not a huge work to add it, so I will probably put new metrics for that to mix min/km and km/h on the same screen if they want.
iOS15 and watchOS 8 have added a lot of enhancements in SwiftUI. It makes the code more concise and readable, it brings new features and reduces the gap with UIKit.
It also brings the new Swift concurrency framework to a lot of existing APIs. It can help to make the code easier to maintain.
If it becomes too complex to maintain backward compatibility, I will force upgrade to iOS15/watchOS8.
And iOS16 and watchOS9 are coming in 6 monthes ...