Earlier quoted context omitted.
In earlier days, it was really easy to kill the Wakemate app by opening a bunch of other apps and then Android would kindly unload it from memory. The dev (There's only one between Android and BlackBerry) has fixed this in recent betas and, I believe, the current market version. I do find early AM fat finger syndrome to be the more frequent cause of data loss compared to Wakemate bugs, but they do crop up.
Do you find the beta to be worth requesting access to? I feel for the dev - I'm in similar shoes (although I do have a Blackberry co-developer, switching between those two environments is not fun). Sometimes it seems like the only similarity between Java on the two devices is the name. Hopefully they get the client where it aggressively saves regardless. That's all I ask - I hate losing data more than I hate missing…
The WakeMate: A Review after Three Months
11–15 of 15 posts
Re: The WakeMate: A Review after Three Months
#12I stopped using my wakemate after maybe 3 weeks mostly out of frustration. I was never able to score higher than 65 despite sleeping for long hours, short hours, etc. (is my sleeping really that bad every day?). The other thing that frustrated me is all the data is useless unless you tag it and create your own trends to follow, i.e. I sleep better when I [exercise]. I sleep worse when I [ate before bed]. The thing th…
I experienced all those same issues. I don't really care about my sleep score as I'm just in it to abuse my body into giving me more coding hours. Autosuggesting tags is but a feature request and some developer attention away. As far as tagging data, I thought the whole point was so that you could keep your own metrics not that you had to. The only thing they can monitor is how well you slept. It's up to the users to…
I did like tracking my own data, but I got annoyed that every day I would have to type the same tags again in order to do it:
M: [exercise][ate late][shower] Tu: [exericise][tv before bed] Wed: [tv before bed][shower] Th.. etc
It's maintainable after a few days but after a week or so you just get sick of typing it over and over.
Re: The WakeMate: A Review after Three Months
#13Earlier quoted context omitted.
Do you find the beta to be worth requesting access to? I feel for the dev - I'm in similar shoes (although I do have a Blackberry co-developer, switching between those two environments is not fun). Sometimes it seems like the only similarity between Java on the two devices is the name. Hopefully they get the client where it aggressively saves regardless. That's all I ask - I hate losing data more than I hate missing…
I find the beta group to be really good for WakeMate. There is always the risk of new bugs as well as new features. If you're super super fussed about your data, I'd say stay away but it's rare to see a regression. Big issue for me was it wouldn't store my login so I had to re-authenticate every time I opened the app to go to bed, which at 5AM when you're getting up in 90 minutes is no fun at all. I think that went a…
Re: The WakeMate: A Review after Three Months
#14Earlier quoted context omitted.
Do you find the beta to be worth requesting access to? I feel for the dev - I'm in similar shoes (although I do have a Blackberry co-developer, switching between those two environments is not fun). Sometimes it seems like the only similarity between Java on the two devices is the name. Hopefully they get the client where it aggressively saves regardless. That's all I ask - I hate losing data more than I hate missing…
I find the beta group to be really good for WakeMate. There is always the risk of new bugs as well as new features. If you're super super fussed about your data, I'd say stay away but it's rare to see a regression. Big issue for me was it wouldn't store my login so I had to re-authenticate every time I opened the app to go to bed, which at 5AM when you're getting up in 90 minutes is no fun at all. I think that went a…
Re: The WakeMate: A Review after Three Months
#15I will buy a WakeMate if they can resolve the two issues brought up in this review (not losing data and a nap feature). The only problem now is that these were the issues that they were having 3 months ago when it was released.
We are working on a nap feature and the data loss issue is fixed!