claude-code - 💡(How to fix) Fix UX: Usage reset time varies monthly + feedback accessibility for non-English users [1 participants]

TL;DR

To improve the user experience for non-English users, consider implementing a fixed local-time reset for usage cycles and adding an in-session feedback submission feature.

Guidance

• To address the varying reset time issue, calculate the reset time based on the user's local timezone instead of UTC, ensuring a consistent reset time each month.
• Display the next reset time prominently in the /usage output to help users plan and track their usage.
• Introduce a /feedback command or a localized feedback page to allow users to submit feedback directly from the session in their native language.
• Consider integrating a translation service to handle feedback submissions in multiple languages.

Example

// Pseudocode example of calculating reset time based on user's local timezone
resetTime = subscriptionStart + (30 days × 24 hours)
resetTimeInLocalTimezone = resetTime.convertToUserTimezone()

Notes

The solution may require significant changes to the existing system, including timezone handling and feedback submission infrastructure. Additionally, ensuring proper translation and localization of the feedback submission feature will be crucial for non-English users.

Recommendation

Apply a workaround by displaying the next reset time prominently in the /usage output and introducing a /feedback command or localized feedback page to improve the user experience for non-English users. This approach addresses the immediate concerns and provides a foundation for further improvements.