Change for Change’s Sake
In the world of to-do list and productivity apps, change seems to be a constant. That goes for developers and users.
Developers work to iterate features to keep users interested and attentive. They don’t want their app to get stale because if that happens then they could be seen as less than cutting edge in the eyes of existing and potential users. So they make changes to the user experience and the user interface at varying frequencies to keep that from happening.
Users tend to get bored with apps that don’t add features or iterate regularly. They view stability as a sign of stagnation, which isn’t entirely unwarranted and shouldn’t be dismissed out of hand. A shiny new app that sports a shiny new feature that users have been clamouring for — or think that would add more value than sticking with their current app of choice — can come along and draw them in. Then the cycle of adapting to a new app starts all over again, often resulting in a less productive period of time while that happens.
Developers and users need to think about whether or not they are making changes that are worthwhile for them or if they are simply making changes for just the sake of change.
In my experience, apps that want to serve their users’ productivity don’t do this. And users that want to serve their own productivity don’t change apps unless it’s a must.
You need to decide — whether you make apps or use them — which side you’re on. And if you find that you might be on the wrong side of either equation, then make sure to change that instead of your app.
Making that change will make things more productive for everyone involved over the long haul.
