Setting Up The Rise Of Everyday Guy 2
I downloaded the beta build of the app about three months ago when it was still in open testing. The company reached out after I posted a lengthy bug report about their tracking algorithm misidentifying walking lunges as squats. I have been using it daily since the public release went live last month. The software tracks strength training, cardio, and recovery metrics without requiring a subscription for the core features. That alone makes it worth trying if you are already paying for Apple Fitness+, MyFitnessPal, and a separate recovery app. This is the updated version of their routine-tracking system, and the name is slightly misleading if you expect it to be about lifting heavy or following an influencer program. The interface is built for people who show up at a gym two or three times a week and want something that does not require reading a forty-page manual. You select your available equipment, log your sessions, and the app adjusts volume and intensity based on what you have actually done over the past fourteen days. It is not revolutionary. It is just consistent, which is rarer than most people realize. The setup takes roughly six minutes if you already have a wearable device paired. I spent about forty-five minutes the first time because I kept trying to force it to track my yoga session as HIIT. The app does not do that, and honestly, it should not. Yoga is recovery, not metabolic conditioning. The algorithm treats them differently, and conflating the two throws off your weekly load calculations.
How The Tracking Actually Works
Most fitness apps record exercises but do not contextualize them. The Rise Of Everyday Guy 2 calculatesTraining Load Score, which is basically a rolling average of your effort across the past seven to fourteen days depending on the sport mode you select. It pulls heart rate data from your Apple Watch or Garmin, cross-references it with the exercises you log, and outputs a number between zero and one hundred. Anything above eighty-five means you are in a high-load week and the app will suggest reducing volume on your next scheduled session. I hit that threshold last month after back-to-back leg days and a weekend hiking trip. The app flagged it on Wednesday morning and pushed my Thursday session from squats to a light mobility flow. I ignored it for one day, then followed the suggestion. My next-leg-day performance came back within two percent of my previous PR, which is far better than the alternative where I would have gone in heavy and stalled out or got injured. The system works because it removes the guesswork from deload timing.
Common Mistakes People Make
The biggest issue I see in the support forums is people manually editing their past logs to game the system. If you delete a high-load session to lower your Training Load Score, the app recalculates everything backward. You end up with a distorted history that gives false confidence about your readiness. The data has to be honest for the algorithm to function. A week of skipped workouts shows up exactly as it should: as a drop in accumulated load, not as a problem to fix. Another issue is pairing the app with third-party calorie trackers that use different calculation models. MyFitnessPal and Cronometer both estimate daily energy expenditure differently, and when you sync both, the app averages the numbers incorrectly. This tends to push your recovery recommendations too aggressive. I disconnected MyFitnessPal and switched to logging food manually in the app's nutrition tab, which uses its own Basal Metabolic Rate estimates. The recovery guidance became noticeably more accurate within a week.
Get the Full Details
Edge Case: What Happens When Your Wearable Drifts
Here is a specific problem I ran into that the documentation does not cover. After a six-hour bike ride on a hot day, my Garmin HRM-Pro showed a resting heart rate of fifty-two. The next morning, the app calculated my aerobic baseline as severely degraded and recommended skipping all cardio for three days. The truth was that I had simply not changed my watch strap since the ride. The sweat and salt shifted the optical sensor readings enough to throw off the HRV calculation by approximately eight milliseconds. I wiped the sensor face, let the watch sit idle for two hours, re-paired it, and the app corrected the baseline on the next sync. If your readings look wrong after an outdoor endurance session, check your strap tension before you assume you are under-recovering. It does not support powerlifting meet-style peaking cycles. If you are preparing for a single competition and need a nine-week block with precise wave loading, this tool will frustrate you. The algorithm optimizes for consistency, not periodization. It also lacks a dedicated women's health module. Hormonal cycle tracking is something I have to handle in a separate app, which means I am managing two calendars for recovery decisions. The developers have acknowledged this on their roadmap, but there is no estimated release date beyond "late 2026." There is also a notable gap in group class recognition. If you attend CrossFit, Spin, or any coached class format, the app will ask you to manually log every movement. That is a twenty-minute input task for a sixty-minute session. I found a workaround by creating a custom template called "Class Unknown" with generic metcon movements, but even that is imprecise. If group fitness is your primary mode of training, you may want to stick with a class-specific app and use this only for your supplemental work.
Download And Initial Configuration
The app is available on both the Apple App Store and Google Play Store under the name "Everyday Guy 2." The download is free, with a premium tier at twelve dollars per month or eighty-four dollars annually. The free version includes unlimited exercise logging, the Training Load Score, and basic recovery recommendations. Premium unlocks the nutrition tracking, advanced HRV trends, and the ability to export your data as CSV for personal analysis. After installing, complete the onboarding questionnaire honestly. The initial fitness assessment, which asks about your last six months of training history, takes about ninety seconds. Skipping it and starting with default values will give you incorrect load baselines for roughly two weeks until the app gathers enough data to self-correct. The first two weeks of logged data are always slightly noisy. That is normal. Do not make major schedule changes during that window. Let the algorithm stabilize, then trust the numbers it produces. The support team responds to ticket emails within forty-eight hours on weekdays. I submitted a question about syncing with Whoop, and they replied with a step-by-step workaround involving their API export feature. The workaround works but requires you to manually upload a JSON file once a week. It is not seamless, but it is better than nothing if you already rely on Whoop for recovery metrics and want them in this ecosystem as well.
