Rules For App Updates
I should probably make this a premium list, because it seems like developers don't know how to not tick off the user base (or at least the me-part of the user base) but it all seems like common sense to me.
This list brought to you by Android Auto's Boondoggle.
1. DON'T CHANGE THE INTERFACE
Odds are, if I open an app, I'm trying to do something with it, not take on extra homework on a learning curve. Opening an app and having to hunt and search for features when you're pressed for time (i.e. always, we use apps to save time and make life more convenient) is stressful.
2. If you need to change the interface, offer an optional preview
"Hi! We have a new interface we think is much better. Would you like to test it out? A) No thanks, I'm in a hurry, keep things as they were. B) Sure, let's see!"
3. After the optional preview, allow the user to revert if they don't like it
4. DO NOT CHANGE SETTINGS
I couldn't figure out why YouTube Music wasn't auto-playing songs when requested while driving. I finally found it when I took the time to go into Android Auto settings. Android Auto is generally not available when you're not connected to a car.
5. If there's a new setting due to a new feature, disable by default
Don't force things onto the user base.
No comments.