Unreliable predictions
I had high hopes for this app. The UI design is very nice and it seems to function very well on both my iPhone and Apple Watch BUT the predictions for battery life are WAY off because it only looks at the power usage for the past 12 hours or so. Like take my Apple Watch Ultra for example. It can go about 2 days (48 hours) on a full charge. When I woke up this morning, it said I had 183 hours of battery life (because I had been sleeping and using hardly any power) and then after an hour and a half of being awake it now says 77 hours of battery remaining and this will continue to drop as the day goes on until I sleep and then it will shoot back up to 100+ hours. It’s useless. I have another battery tracking app called “Battery Grapher” which is way more basic, it doesn’t have the beautiful UI design of this app but the predictions are WAY more accurate because it actually learns your usage patterns and stores this data so that it can accurately predict your battery life. It’s so much more accurate and doesn’t have wild swings in its predictions because it’s actually learning instead of just estimating battery life based on your recent usage with no logic. I really hope the developer can fix this because it’s actually a really nice app but the one thing that it is designed to do, it does very poorly.
Show more
more contrast needed, bad readability at the watch
So fare a good app, but it‘s not good to read, every thing is to small and the background should be black and the text white.
Thanks
Thanks
Not 100% worth $3…
So I’ve only used the app for about 20 minutes now, and I’ve noticed that the dead time gets cut off on the widget, it bothers me so much. It says “05:…”. So I know that’s probably fixable, and if this app ever gets big, that should be fixed before a ton of people rate badly.
UPDATE: Developer fixed the problem, responded to me (which was nice)
UPDATE: Developer fixed the problem, responded to me (which was nice)
Show more
Response from developer
Hello, Thank you for your comment and for noticing this bug. It is now fixed with version 1.1. Best regards
