Have something to say?

Tell us how we could make the product more useful to you.

Planned

Progress: Logic to calculate daily completion rate on weekly/monthly habits

Hi, I’ve noticed that my overall metric rarely goes above 14%. I believe this is because I have several habits that are tracked monthly, and these are currently being counted in the overall daily metric. Wouldn’t it make more sense for the overall rating to reflect only the habits set on a daily basis? I’m not entirely sure how best to implement this, because if I happen to check off a few monthly habits on the same day as my daily ones, that could disproportionately inflate the metric. Maybe it would be worth considering two separate overall metrics — one for daily habits and another for the total (daily + monthly). Right now, the overall score doesn’t reflect my actual consistency in a meaningful way. Hope this suggestion makes sense Rui Correia

Rui Monopolis Manufaktura 9 months ago

10

Completed

Log Progress: Reduce Friction When Exceeding Weekly Habit Targets

Habit building is based on discovering real capacity through practice. Users often start with a low weekly target, then realize they can perform the habit more times within the same week. Current problem: For weekly habits, once the target count is reached, the habit is treated as completed. Adding additional repetitions becomes difficult and requires manual numeric input, even though exceeding the target is intentional and positive. This creates unnecessary friction when: a habit is still in the building stage, or the user performs the habit more times than planned in a given week. Request: Allow users to continue logging repetitions after reaching the weekly target using the same quick interaction (e.g., +1), without switching to keyboard input or a different flow. This change supports gradual, experience-based habit building without changing existing default behavior. Summary: Keep weekly habits active after the target is reached. Allow quick (+1) logging beyond the weekly target without restriction. Remove the requirement for keyboard-only numeric input when exceeding the target.

Ahmad 2 months ago

12