Site is extremly buggy and keeps crashing
#4
FitDay Member
Join Date: Jan 2013
Posts: 6
same here
I have used both Firefox and Google Chrome, but it doesn't make any difference. It is nearly unusable, and I switch to classic every time I want to enter new data. It's full of bugs and it also keeps telling me it can't retrieve data...
#5
FitDay Member
Join Date: Feb 2013
Posts: 2
same here
I went with the free version to test if I should buy the premium, but with the response on the web pages here I can not use this service. It is extremly slow and ends up crashing. It seems that it may have to do with loading ads and javascript when loading the "add Food". Both Chrome and Firefox
#8
FitDay Member
Join Date: Feb 2012
Posts: 5
Aside from when the entire page was down (like it was 11 or so hours ago) I've never had any problems using the 'classic' page. Fitday 2 is where it is terribly slow (even when things are working well) and often throwing a bunch of errors.
#9
FitDay Member
Join Date: Jan 2013
Posts: 1
Journal tab in Fitday Classic won’t load today
The Journal tab in Fitday Classic won’t load. Every other tab is working except that one.
I prefer Fitday Classic because Fitday 2 is incredibly slow and cumbersome. And I record my stairclimbing religiously in that journal so I rely on it.
Like others, I find Fitday is intermittently reliable. It is frequently “tired” and crashes and won’t display pages. It is REALLY FRUSTRATING.
I prefer Fitday Classic because Fitday 2 is incredibly slow and cumbersome. And I record my stairclimbing religiously in that journal so I rely on it.
Like others, I find Fitday is intermittently reliable. It is frequently “tired” and crashes and won’t display pages. It is REALLY FRUSTRATING.
#10
FitDay Premium Member
Join Date: Jan 2013
Posts: 10
Concur: Fitday 2 is not ready for primetime
They keep changing it before it is even stable at one version state. Features appear and disappear without warning, much like Facebook.
The difference here is that those of us who are paying for this service, and footing at least some of the bill for it, should not have to be subjected to the kind of on-the-fly programming that users of free services have to put up with.
A real premium service should be subjected to adequate testing before changes are implemented. Users should be notified when feature changes are done AND feature changes should be rolled out in sets, not individually.
The difference here is that those of us who are paying for this service, and footing at least some of the bill for it, should not have to be subjected to the kind of on-the-fly programming that users of free services have to put up with.
A real premium service should be subjected to adequate testing before changes are implemented. Users should be notified when feature changes are done AND feature changes should be rolled out in sets, not individually.