some settings persisting, some not
Answered
I know it was a decision in a recent update to not persist the "battery saver" setting through a power cycle. Yes other settings are persisted. I think this is a poor decision from an UX perspective. Why?
First, the UX element. It should be obvious that every setting survives a power cycle in the same way. Consistency is key, and you've just introduced inconsistency.
Second, from the rider's perspective:
If you're someone who goes on long, long rides (and let's be fair, the Karoo battery doesn't last all that long), you're going to want to save every drop of battery juice you can have. Which means you probably want your battery saver on all the time. Having to think about switching it on every day is annoying. Conversely, if it is on but you didn't mean for it to be on, it's not a big deal because the screen will turn on when necessary (turns, segments...), and it can be turned off when you need.
A counter example is in audio alerts. Why does that setting persist? If you accidentally have it off during a ride, it's more likely to do damage (missed turns, messages, segments) than the battery saver.
I think you may need to re-think this part of the UI, but I would personally prefer that my Karoo persist everything or nothing.
-
Hi bluppfisk,
Thanks for your feedback! I can see your points there and will share that with the team.
I will try to shed a little light on the logic with those, though.
The audio settings are persistent because it is considered a feature that people generally leave on all the time, or turn off permanently - you either love the beep or you don't. (and the battery save was obviously the same previously)
In contrast, most people who turned on battery save mode ended up doing so because their battery got low and the device warned them and gave them the option to enable battery save mode, so they did. Fast forward to the next time they use their device and the screen keeps turning off and they get frustrated the whole ride and send a support email later only to find out that it was just battery save - we received many many emails about that and the resounding feedback from those people was that it should not be persistent because it is a setting they'd only use out of necessity (rather than a permanent preference) so it made no sense for it to be on the next time they powered up with a full battery. After many many requests, it was changed.
Again, I totally get your points and I will forward those to the software team - I just wanted to explain why it is as it is now.
Hey Nicholas - in mentioning APN settings - those should persist unless you perform a hard reset. Simple power cycles should not impact those settings - I also responded to this point in the email thread we have going about your other question. You can reply there - thanks!
Please sign in to leave a comment.
Comments
3 comments