Currently, people who use "Imperial" as their app system units have to enter Running FTP in seconds according to their metric pace (minutes/km), not their imperial pace (minutes/mile). This creates confusion because as an Imperial user in the US, I added my Running FTP according to my pace (7:51 min/mile - 471 seconds) and was confused when I saw my Imperial pace as 12:38 min/mile. This happens because by default, the Running FTP corresponds directly to minutes/km, and then is converted into minutes/mile. See screenshot below.
Ideally, when entering the settings for Running FTP, the app should see what units the user is using, and then immediately calculate the correct pace for both Metric and Imperial, instead of defaulting to Metric. This would prevent an Imperial user from having to enter their Running FTP according to their Metric pace.
Currently, people who use "Imperial" as their app system units have to enter Running FTP in seconds according to their metric pace (minutes/km), not their imperial pace (minutes/mile). This creates confusion because as an Imperial user in the US, I added my Running FTP according to my pace (7:51 min/mile - 471 seconds) and was confused when I saw my Imperial pace as 12:38 min/mile. This happens because by default, the Running FTP corresponds directly to minutes/km, and then is converted into minutes/mile. See screenshot below.
Ideally, when entering the settings for Running FTP, the app should see what units the user is using, and then immediately calculate the correct pace for both Metric and Imperial, instead of defaulting to Metric. This would prevent an Imperial user from having to enter their Running FTP according to their Metric pace.