Under the hood the frequency is also handled as numbers (0/1), there is a way for users to change the type if desired from Boolean to X Times, but complications

Under the hood the frequency is also handled as numbers (0/1), there is a way for users to change the type if desired from Boolean to X Times, but complications stem when they want to do the other way around. Some of the main pain points it might introduced are into visualizing the historical data. When you've been saying yes & No, and suddenly you want to track count, you'd see bit of inconsistency on how the data is presented. This proves hinderance to further work on finding the patterns. Hence why.. The way it is structured now, tracker is a one immutable component of type & frequency and when one of it changes, its a whole new tracker. This would simplify the experience for the user down the line. Rest assured, if this seems to be bothering users much, I'm willing to see if it could be done the other way as well.