We know a lot of software devs, most of whom have big ideas and titanium strength opinions. So we invite you to read through our list of 20 thoughts and let us know the ones you agree with, or flame us on the ones that violate your beliefs right down to the DNA (preferably using language that doesn't read like a transcript from some Chris Rock stand-up).
1. Don't bloat your app with features. Aim for less features with more usability. Keep it skinny.
2. Don't re-invent features that already work. Improve usability to make them work better, not different for the sake of being different. Trying too hard to be different is not the same as
innovation.
3. Cool features get attention. Usable features get used. Once usable features become cool, they stay cool.
4. If you're an expert in your software, you do not represent most of your users. Who is more important, you or them?
5. Whether your software is for productivity or just for style/entertainment, user focus will be on a handful of core features only. Their life is not dedicated to your app.
6. It's very difficult to be feature rich and usability rich at the same time. Redefine feature rich as "having core features done right" instead of "having many features".
7. More features lead to a bigger learning curve. A bigger learning curve leads to greater user failure/drop-off rates and more "support tickets"! Don't drown your users or yourself in features.
8. Thousands of configuration options are overkill when most users stay close to defaults. Make smart decisions for them.
9. Over time, usability flaws and missing features will reveal themselves through user consensus. You must iterate to get it right. You're not smart enough to get it right on the first try.
10. Avoid the pressure of adding features just to create a new release. In fact, consider removing features that don't get used instead! That's probably a more valuable update.
11. Your core users would be more willing to give up features than usability - even if they don't know or admit it.
12. Advanced options add complexity and bugs to development, but will often add limited new value. Don't suck at developer ROI.
13. Technical users are better served by a plugin system than a default package overloaded with fluff. Let devs create their own amazing add-ons & fluffiness!
14. One amazing feature can trump 20 good features if it matches the users true "needs".
15. Best practices will help you do well, but won't make you perfect. Only feedback can take you to the next level. Listen up and don't be arrogant. But follow consensus and don't be a push over either.
16. Users are not stupid, but you might be if you design software optimized for you instead of them.
17. The more features you add, the greater percentage of them that will be ignored and/or suck.
18. Don't chase trends like social media too quickly, or you'll inherit the mistakes more often than the successes. Choose wisely. If you're not good at choosing wisely, follow those who
are very closely.
19. Don't be too slow to adopt components of phenomenons like Facebook! Some things can't be stopped / resistance is futile.
20. Usability pays everyone. As feature count increases, resource costs accelerate, usability decelerates. Keep costs low, usability high. Resource costs = time, money, enjoyment,
motivation.
This is a big list, bloated in fact. Did we forget that articles and lists have usability too? It would probably be more valuable with only 5 of the best thoughts featured.
Which ones are most useful and which should be tossed into an acid bath? The mic is all yours.
