3 ms·
The canonical MVP strategy for a web application is to create a mock website Note the web application text. Codo is a desktop application and therefor the MVP
by abraham 17y ago
The canonical MVP strategy for a web application is to create a mock website Note the web application text.
Codo is a desktop application and therefor the MVP is a desktop application. Prototyping a web application for a desktop application usually requires a complete rewrite not iteration.
MVP in general seems suspect and something hackers should avoid.
Example: Feature: (deploy first, code later) A link to a new feature in a web application may be provided in a prominent location on an existing website. The feature is not implemented, rather an apology, mock-up, or marketing page is provided. Clicks of the link are recorded and provide an indication as to the demand for the feature in the customer base.
- wgj 17y agoI understand the difference in web vs. desktop. In this case, the intent as it relates to MVP is the same. The example given measured market interest without a prototype, so there is no iterative deployment issue. I can understand the apprehension about MVP. As a coder myself, it is not an obvious approach (vs. putting out an actual beta) and I've not yet tried it. I'm interested in other people's stories and experiences though, and I'm not inclined to downmod a constructive conversation about it.