Bureaucrats, emailconfirmed
1,221
edits
→Simplicity
| Line 101: | Line 101: | ||
===Simplicity=== | ===Simplicity=== | ||
When I say simplicity I do neither mean "ease of use" or "looking shiny and smooth". The kind of simplity you should strive for is implementing only the features that are important for your idea and to implement them in a way that they work together greatly. You should not add anything because it is a nice to have or one in ten people thought it would be useful. | |||
Every time you add a feature, you need to make it fit to the rest of your product. It potentially will make it slower, less solid and more difficult to use. And keep in mind: the ressources you use to add features (you are probably student so it is: time) can't be used for refining the really crucial features. | |||
So how do you decide which features you are going to implement? | |||
I don't have any instant solution. The most important is that you keep in mind that you should create a unique, easy-to use product that does do what it does greatly. During this course you will learn how to do user research to find out about the goals ands problems of your users. Try to find out what really matters for them. If you see that you have two different groups of people, find out if they are similar enough to serve them one product. If they differ too much, say goodbye to one of them and design just for one of the groups - maybe you come back later to the other, but first concentrate on one thing. | |||
==Get to know what your users need== | ==Get to know what your users need== | ||