Log subjective experiences (and include in Recovery score? or create separate Subjective score?)
planned (tbd)
Quinn Comendant
This may already be planned as part of the journaling feature, but since it hasn't been mentioned specifically, I'm creating this as a separate feature.
The idea is to prompt the user through a guided questionnaire every day, and generate a “subjective score” that may be used as part of the Recovery calculation – but, as @Markus Eisen points out below it should probably be a separate Subjective score and displayed as its own trends chart.
The questions presented to the user can be enabled/disabled so the user only needs to answer questions that are relevant to their training goals.
This is similar to how HRV4Training uses both HRV and subjective annotations. I'm currently using this, and log my subjective values when I do a Breath session every morning. The questions I configured are:
- How was your sleep quality last night?
- How motivated are you to train today?
- How is your current physical condition?
- How is your mental energy this morning?
- How is your muscle soreness this morning?
- How fatigued are you this morning?
- Are you currently injured?
- How would you describe your lifestyle? (Unstable/travel/stress ↔︎ Routine/can focus on training)
- Were you traveling yesterday?
- Are you sick today?
Our bodies already accurately report a “recovery score” by producing feelings of soreness, fatigue, etc., which is generally accurate – we should use it! Generating a Recovery score based only on biometric data is difficult, but by including subjective experience into its calculation we can get more useful clues as to whether and how to adjust future training. I'm not sure if it should be included as part of the Recovery score (is that how HRV4Training does it?) or to display it only as a separate Subjective score. What do you think?
Amanda
Merged in a post:
Log How You Feel After Sleeping
Z
Zadrian
I wish there was a way to manually log how I feel after sleeping. Sometimes my sleep data looks great, but I still feel bad when I wake up. I know how I feel can be affected by a lot of things, but it would be interesting to compare my actual feelings in the morning with what the data says.
Amanda
Merged in a post:
Possibility of manual assessment (0—10 scale) of subjective states
Michael
I would suggest a function in Bevel where one can enter manual values (from 0 to 10) on a daily basis -- e.g., how to self-evaluate:
• Energy level
• Mental state
• Sleep quality (subjective, in addition to the automatic data)
• Pain, well-being, motivation, etc.
It could act as flexible input fields with optional naming and icons.
The aim is to connect subjective data with the automatic measurements and create a more nuanced view of how you actually feel — not only based on HRV, strain and sleep, but also your own experience.
Amanda
Merged in a post:
Custom Mood Reasons
Simon Gilks
For example if I sleep really badly I wake up in not a very good mood but I cannot see how to input bad mood based on lack of sleep.
Or a bad mood because of feeling ill.
On the flip side good mood because of great sleep.
Michael
Thanks. I’m aware of the mood log. The others would be awesome 👏 😎
Amanda
Thanks for the suggestion Michael! We do have a way to log your Moods through Journal right now (Journal -> "..." -> Customize journal -> + Mood). For the others, we can look into the best way to integrate this.
Amanda
Merged in a post:
Personalized Health Feedback
Peter Nagy
While I find the metrics based on watch data super useful, I do not always seem to agree with the results. Eg. I get a very high sleep score but still feel sleepy, or when I get high stress scores even though I am just relaxing at home, so I do not quite understand.
To tackle these inconsistencies, I would like to suggest incorporating a daily feedback feature, where users can rate their sleep quality and overall wellness. The idea is to complement the objective sensor data with subjective user input. For instance, users could answer a few simple questions every day such as:
• How would you rate the quality of your sleep last night (1–5 stars)?
• How do you feel upon waking up (refreshed, neutral, tired)?
• How stressed did you feel today (1–5 scale)?
• How energetic do you feel right now (1–5 scale)?
• Overall, how would you rate your wellness today (1–5 scale)?
Collecting this data could help refine the models over time by better aligning the calculated metrics with user-reported experiences. Even if the subjective data is not directly used to improve the underlying algorithms, merely viewing correlations between objective and subjective metrics could provide valuable insights. When users notice discrepancies between the sensor-based scores and their own feelings, these correlations can enhance our understanding, ultimately paving the way for a more personalized assessment.
I believe that by combining objective measurement with subjective user feedback, you can not only enhance user confidence in the app but also improve the accuracy and usefulness of the health metrics provided.
Thank you for considering this suggestion!
Amanda
Merged in a post:
Rate sleep
K
Koan
It would be nice if they is a option to rate the sleep from the night before based on (for example) the motivation or how you get out of the bed. No matter if the sleep score says different because sometimes I feel less or more then my score.
I guess this would also effect the strain score in a efficient way.
Amanda
Hi Koan, this is an interesting idea to have users provide feedback on their scores. We will keep this in mind for future!
Canny AI
Merged in a post:
Estimated Recovery Score Based on User Feedback
T
Tobias Gürtler
Hello Bevel Team and Community,
I recently encountered a situation that sparked an idea for a potential new feature. Last night, I forgot to wear my Apple Watch, which resulted in no HRV and RHR data being recorded. As a result, my recovery score was missing. This got me thinking about how Bevel could still provide valuable insights even when wearable data is unavailable.
idea:
Introduce an option for users to manually input their perceived sleep quality when Bevel detects missing sleep data. This could be implemented as a simple prompt with five options (e.g., “Very Poor,” “Poor,” “Average,” “Good,” “Very Good”) asking how restful the user’s sleep felt. Based on this input, Bevel could generate an estimated recovery score.
Implementation Details:
1. Detection of Missing Data: When Bevel notices that key data such as HRV or RHR is not available, it could trigger a prompt asking about the user’s perceived sleep quality.
2. User Input Options: Present the user with a scale to rate their sleep quality. This could be in the form of a survey with descriptive labels for each rating level.
3. Estimated Recovery Score: Using the input from the user and any other available data (such as estimated sleep time from the iOS alarm), Bevel could calculate a rough recovery score.
4. Clear Labeling: In the recovery overview, the estimated score should be clearly labeled as such, with a note indicating that it is based on the user’s subjective experience rather than biometric data.
Benefits:
• Continued Insight: Users receive some feedback even when biometric data is incomplete, helping them stay engaged with their recovery process.
• User Empowerment: This feature allows users to contribute their subjective experience, which can be valuable in understanding overall recovery.
• Flexibility: It accommodates situations where wearable data might be missing due to forgetfulness or device issues.
I believe this feature would add significant value to Bevel by ensuring users can still gain insights into their recovery, even in the absence of complete data. It balances the objectivity of biometric measurements with the subjective nature of personal experience, providing a holistic view of recovery.
Looking forward to hearing thoughts from the community and the development team!
Best regards
Grey
Thanks for the feedback! We've been thinking about this for some time. It's definitely doable, but will require some time to think of the right UX.
I'll add it to the roadmap.
Load More
→