Speed improvements

• The KPIs and KPVs tabs on the roster have been optimized to reduce loading times by about ~95%.
• Group profile reports were optimized to reduce loading times by about ~80%.

Workout sheet fixes

• The workout sheet was improved to eliminate a glitch where the data would sometimes revert to a previous state while entering data (especially when working fast).
• The backend was also optimized to be able to keep up with rapid changes to the workout sheet, and to eliminate errors resulting from multiple updates in quick succession.
• The workout sheet should feel faster and less glitchy, even for power users.

Improved roster management

• Coaches sometimes had trouble with duplicate athlete entries on the roster. We've added some additional validations and constraints that should prevent this from happening.
• Athletes would occasionally have trouble signing up for a team if they already had a FYTT account. The team URL signup flow has been improved to reduce confusion for both coaches and athletes.

API changes/additions

• New mutation endpoints were added to the API that allow you to create and update KPIs and KPVs. See documentation for the endpoints here: modifyKpis and modifyKpvs.
• The existing mutation endpoints for adding KPI and KPV measurements where changed to modifyKpiMeasurements and modifyKpvMeasurements to better reflect their functions (the old endpoints will remain functional as aliases for these new endpoints).

Email deliverability improvements

• Some organizations were experiencing issues with FYTT emails landing in athletes' spam folders. We've fixed our domain settings so that emails are now fully verified and authenticated, which should drastically improve deliverability.

Updated API with improved documentation

• You can now query additional athlete data, including KPI measurements, KPV measurements, and session data for both recorded sessions and scheduled sessions.
• Using the KPI and KPV mutations you can now update or delete existing measurements in addition to creating new measurements.
• The API docs were completely rebuilt from the ground up to provide improved documentation on how to utilize the new API queries and mutations. See the new docs here.

Date range and metric sorting for Athlete Profiles

• Athlete Profiles now have a date range input that allows you to specify the date range to be used for the report. Report sections now only show data from within the selected range.
• The metrics for each section can now be sorted, so you have control over the order they appear on the graph. This is particularly helpful for the radar graph.

Inverted option for Percentile Assessments

• Percentile Assessments now have an option to invert the percentile calculations. For example, if the original percentile calculation resulted in a value of 20th percentile, it would be inverted to be 80th. This is helpful where a low percentile rank equates to better performance. e.g., sprint time, lap time, etc. The effect is that all percentile calculations can now be "normalized" for easy comparison.