Pelotrak 1.5.4

Pelotrak
2 min readFeb 12, 2022

--

Previous updates here: 1.5.0, 1.5.3

Note: should the updated app hang during a data refresh or ask repeatedly for your login, please do a Full Reload (under About → Settings) to resolve any issues.

Overview

  • Allow users to select with users to follow in the activity feed
  • Pelotrak now also available in German 🇩🇪
  • Customization of insights format in sharing section
  • Lots of small fixes

Select Who To Follow In Your Feed

By default, Pelotrak automatically tracks the first 75 people you follow for the activity feed. If you have more people you follow on Peloton, you could not control who shows up in your feed. This is now fixed.

After your next data refresh, you can go to the Settings and select the users you want to follow in the feed. The list of close friends will always be a subset of the list of people in the feed.

Translations

Quietly added to one of the last releases, Pelotrak is now officially available in German. It should automatically detect if the language of your phone is set to the German region and adjust. You can also manually change it in the Settings page.

A big shout out to the users who helped with the translations, especially all the long instruction pages.

If you are interested in helping translate the app to another language, please check out the new Pelotrak translation GitHub repo: https://github.com/oskarbruening/pelotrak-translations and let Oskar know if you have any questions.

Customization of Insight Format

Previously, the location of the insights in the sharing section was very limited. Now it can be moved around, the box can be scaled, and the text size modified.

Small Fixes

  • The “hard/easy workout” insight now takes the class type into account. It previously based it simply on the heart rate across all classes. Now it is smarter: a workout is hard/easy when compared to similar workouts. If there is not enough recent data, it will continue to base it on the overall heart rates.
  • When checking whether an target metric was met or not, the total was the average of cadence and resistance: if you hit your target metrics 80% of the time on cadence and 100% or resistance, your total was 90%. But that’s wrong. Your total is where either was not met, so the total is 80%. Fixed. Thanks to the sharp eyed user John D. who noticed this.
  • The Active Recovery Output insight got skewed by spiky data. It is now a lot more accurate.
  • Infrastructure for more comprehensive data analysis.
  • More reliable connectivity when loading Peloton data.
  • Try to eliminate glitchy flicker when scrolling back up on the homepage.

--

--