Reported by: kenn
Date: 13.4.2026, 16:37:01
Description
Title: Suggestions & UX Improvements (Passkey issue, formatting, chart labels, real-time updates, GitHub setup confusion, admin UX, and feature request)
Description:
Hi! First of all, thank you for building Healthlog—it’s a very useful app. I’d like to share some suggestions and usability issues I encountered while using it as a regular (non-technical) user.
1. Passkey Registration Fails
Suggestion:
- Provide clearer error messages
- Add debugging or guidance so users understand what went wrong
2. Number Formatting Confusion (Decimals vs Commas)
Suggestion:
- Add a setting for number format (e.g.,
1,000.50 vs 1.000,50)
- Or automatically detect based on user locale
3. Chart Labels (7P, 30P, 90P, All)
- Labels like
7P, 30P, 90P, All are unclear.
- It is not obvious what “P” means.
Suggestion:
4. Dashboard Not Updating in Real-Time
- After adding a new measurement, the dashboard does not update automatically.
- I have to manually refresh the page to see changes.
Suggestion:
- Implement real-time updates or auto-refresh after data changes
5. GitHub Issue Submission Setup Confusion (Non-Technical User Issue)
-
It was not clear to me that I needed to enter the project’s official GitHub repository here.
-
As a regular user (not a developer), I assumed the feature would work out of the box.
-
When I tried submitting feedback, it initially appeared to do nothing, which made me think it was broken.
-
Later I discovered it requires GitHub integration setup (token + repository), and I had to troubleshoot it myself.
Suggestion:
- Make it clear that this requires developer configuration, not user setup
- Add UI guidance when GitHub integration is not configured
- Disable or clearly mark the feature if it is not ready instead of allowing silent failure
- Ideally, users should NOT need to configure repository or token at all
Important UX Note:
As a non-technical user, I expected to simply submit feedback directly without setting up GitHub infrastructure. This part is currently too complex for regular users.
6. Feedback Submission is Too Complex for Regular Users
- From a regular user perspective, submitting feedback is currently too complicated.
- I had to check browser console errors, troubleshoot the issue, and even use ChatGPT to understand what was wrong.
- I also had to create and configure a GitHub repository and token just to make bug reporting work.
Suggestion:
-
Provide a simple built-in feedback system where users can submit reports without:
- GitHub accounts
- repositories
- tokens
-
The app should handle issue creation automatically in the background
-
Alternatively, provide a pre-configured default repository maintained by the developer
Goal:
Make feedback submission accessible and simple for non-technical users.
7. Admin Console Save Feedback
-
The admin console does show a success message when saving succeeds, which is good.
-
However, when saving fails:
- No error message is shown
- No input fields are highlighted
- No clear indication that something went wrong is displayed
Suggestion:
- Keep success message (good UX)
- Add error messages for failures (e.g., “Failed to save settings”)
- Highlight invalid fields in red
- Add loading indicator during save operation
8. Feature Request: Blood Sugar Tracking
- It would be very helpful to add support for recording blood sugar levels.
- This would make the app more useful for users tracking diabetes or metabolic health.
Suggestion:
- Add a blood sugar measurement type (e.g., mg/dL or mmol/L support)
- Include it in charts and history views like other metrics
Thank you again for your work on this project. These improvements would make the app much more intuitive and user-friendly, especially for non-technical and first-time users.
Created via HealthLog bug report
Reported by: kenn
Date: 13.4.2026, 16:37:01
Description
Title: Suggestions & UX Improvements (Passkey issue, formatting, chart labels, real-time updates, GitHub setup confusion, admin UX, and feature request)
Description:
Hi! First of all, thank you for building Healthlog—it’s a very useful app. I’d like to share some suggestions and usability issues I encountered while using it as a regular (non-technical) user.
1. Passkey Registration Fails
The passkey feature consistently fails during setup.
It shows:
Suggestion:
2. Number Formatting Confusion (Decimals vs Commas)
Number formatting is confusing for users from different regions.
Example:
70,570.5Suggestion:
1,000.50vs1.000,50)3. Chart Labels (7P, 30P, 90P, All)
7P,30P,90P,Allare unclear.Suggestion:
Replace with clearer labels:
Or explicitly label as “Days”
4. Dashboard Not Updating in Real-Time
Suggestion:
5. GitHub Issue Submission Setup Confusion (Non-Technical User Issue)
It was not clear to me that I needed to enter the project’s official GitHub repository here.
As a regular user (not a developer), I assumed the feature would work out of the box.
When I tried submitting feedback, it initially appeared to do nothing, which made me think it was broken.
Later I discovered it requires GitHub integration setup (token + repository), and I had to troubleshoot it myself.
Suggestion:
Important UX Note:
As a non-technical user, I expected to simply submit feedback directly without setting up GitHub infrastructure. This part is currently too complex for regular users.
6. Feedback Submission is Too Complex for Regular Users
Suggestion:
Provide a simple built-in feedback system where users can submit reports without:
The app should handle issue creation automatically in the background
Alternatively, provide a pre-configured default repository maintained by the developer
Goal:
Make feedback submission accessible and simple for non-technical users.
7. Admin Console Save Feedback
The admin console does show a success message when saving succeeds, which is good.
However, when saving fails:
Suggestion:
8. Feature Request: Blood Sugar Tracking
Suggestion:
Thank you again for your work on this project. These improvements would make the app much more intuitive and user-friendly, especially for non-technical and first-time users.
Created via HealthLog bug report