Why do most startups remain in the plans?
To begin with, let's see how most startups are planned in the Internet now. Usually they take an already successful idea, realized somewhere in the west, and try to remake it for themselves. For example, was digg, became a portal about diapers with the possibility of voting for articles or news. Or for example web IM. What do they do with it? Well, of course, they screw up tons of options, checkboxes, ryushechek and say that now the product is suitable for everyone, due to a heap of menus, it can be customized for anyone.
Is it really so?
Unfortunately not. In fact, the abundance of settings and options "kills" the program. The fewer checkboxes and menus, the easier it is to use the program. The less time is spent searching for the desired function. Try to watch yourself, what part of the functionality for example MS Word do you use? It turns out that 20% -30%.
This is where the basic rule appears that fits very well with startups. Do as few features as possible! Your users want the software \ site \ service to work, and not a panacea for all occasions. Fight against every new feature, learn minimalism. In addition, it brings many advantages for developers: less code, easier to maintain, faster to develop.
')
In the era of web 2.0, many projects appear in beta status and this is not entirely correct. The icon says that the product is raw and barely plowing, and everything should work for you like a clock. You do not need to test the quality of the code on users, test the functionality on them. Release the project with the minimum of functions, and if you really need to gradually add new ones.
Having got rid of a heap of functions it will be easier for you to understand the performance of your idea. As soon as you remove all the tinsel, only the most necessary and important will remain. It will be easy to compare with other projects, ask friends for an opinion and so on. Think about it, if without a ryushechek your project becomes uninteresting, maybe you didn’t take that idea?
Original
Is it really so?
Unfortunately not. In fact, the abundance of settings and options "kills" the program. The fewer checkboxes and menus, the easier it is to use the program. The less time is spent searching for the desired function. Try to watch yourself, what part of the functionality for example MS Word do you use? It turns out that 20% -30%.
This is where the basic rule appears that fits very well with startups. Do as few features as possible! Your users want the software \ site \ service to work, and not a panacea for all occasions. Fight against every new feature, learn minimalism. In addition, it brings many advantages for developers: less code, easier to maintain, faster to develop.
')
In the era of web 2.0, many projects appear in beta status and this is not entirely correct. The icon says that the product is raw and barely plowing, and everything should work for you like a clock. You do not need to test the quality of the code on users, test the functionality on them. Release the project with the minimum of functions, and if you really need to gradually add new ones.
Having got rid of a heap of functions it will be easier for you to understand the performance of your idea. As soon as you remove all the tinsel, only the most necessary and important will remain. It will be easy to compare with other projects, ask friends for an opinion and so on. Think about it, if without a ryushechek your project becomes uninteresting, maybe you didn’t take that idea?
Original
Source: https://habr.com/ru/post/13477/
All Articles