This is for reporting bugs (things that don't work), rather than feature suggestions (things that we think should be added).
- Ovulation date calculated is wrong for anyone who doesn't have a 14 day luteal phase. There should be an option to enter your luteal phase length if known. Otherwise, it is just as bad as telling everyone they should have a 28 day cycle regardless of their actual cycle length, only in this case it can get you pregnant when you don't want to be. It is consistently showing my ovulation date as being three days earlier than it really is. Luteal phase length is considered normal if it is 10-16 days, and may be longer or shorter than that (if it's shorter than normal then miscarriage is likely, for instance).
Ideally there should be the additional feature of BBT (basal body temperature) tracking to calculate individual ovulation dates, but meanwhile, ovulation dates could at least be estimated by using an average luteal phase length, for people who have done BBT tracking in the past and know how their cycles work. Clue does this. Assuming everyone has a 14 day luteal phase is not an absent feature, it's a bug.
- Pregnancy is not recognised, which means that anyone inputting past period dates which includes a gap for pregnancy will be given an incorrect average cycle length. One user reports that Fitbit has come up with an average of 104 for her cycle lengths, which is over three times as long as they should be. Again, look at Clue. There is a simple box to tick for excluding a cycle from calculations. If someone has changed their birth control in the past (you can only record current birth control) in a way that led to cycles of different lengths, that would be another reason to need it.
- It is impossible to input flow type without having to enter each period twice, and the period has to be inputted in two different screens. It's been theorised that this may be because some people get non-menstrual bleeding in between periods, but since those people are rare (spotting is more common, actual bleeding far less so), it should not be made a default that means that people end up with missing data on their cycles. Again, this will cause incorrect cycle lengths which will affect averages and predictions.
- When adjusting the length of individual periods, if they are different from the average, the slider only works if you are not adjusting it over the Sunday/Monday line. So if my period was marked as Thurs-Sun and it was actually Thurs-Mon, you can't put that in. Similarly, if my period is marked as Fri-Mon and it was actually Fri-Sun, that can't be adjusted either.
- The Windows tile went live before the Android tile did, so I input data into the Windows tile. This included answering questions about my birth control and such, inputting period dates, and inputting symptoms. All of this data was lost when moving to the Android tile and had to be inputted all over again.
- The explanation of the symbols says that a dot (or possibly multiple dots) will show up in the calendar in some way to show if symptoms have been tracked on a day. There is no sign of these in either the calendar or the trends chart.
Community Moderators ensure that conversations are friendly, factual, and on-topic. We're here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
Best Answer
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
