Ger.lv

[...] When you develop Beta version of you product, after MVP and prototype are tested and there is some insights about the [...]

[...] version of you product consider following items: primary market, initial feature set, and product experience. Pricing is not included here despite the fact that it's important, and you can start [...]

[...] fit there are more things to consider. This post primarily focuses on first versions of consumer applications and small to medium applications for businesses (i.e. without long sales cycles and [...]

[...] release the first rough version of you product consider following items: primary market, initial feature set, and product experience. Pricing is not included here despite the fact that it's important, [...]

[...] What leads us to product experience. If you don't add too many separate core features in the initial version it's you will still need to implement more of smaller features than you initially planned. [...]

[...] for error logging, and the application had great speed improvements after switching to NoSQL database). I’ve created logging library for Zend Framework, if someone is interested – check it on my [...]

[...] inspired me to refactor my code in order to support logging not in log files, but in NoSQL MongoDB database (he made an example of it, and said that his servicehttp://cloudmailin.com/ is actually [...]

[...] ) and even hardware products. Except you can't iterate or add features easily if you have hardware product. Many people confuse MVP and Beta version. MVP is just a test that there is a market for [...]

[...] where you don't have enough personal experience. This will help to shape your application initial feature set and focus on the problem. Initial feature set Don't build too much, but don't [...]

[...] , or actually taking pre-payment for your product you can start the development. Consumer vs Business product For consumer products you will need to spend more time on polishing the application. [...]