|
|
|
|
|
by hgl
2319 days ago
|
|
> Even if someone does copy you, it grows the market, at least for startups. Thanks for showing me a totalizing view. This is another thing I should keep in mind. > No. If it were easy, lots of people have already done it earlier. I've never seen a pure copycat do well.
> Unless yours is a trillion dollar industry, it probably won't be tackled by someone competent. When I saw the first the argument, I was gonna say Apple is one, and it beat Xerox spectacularly (I'd hazard it was a pure copycat, the whole selling point of Mac was the GUI), but the second told me I wouldn't have such a mighty competitor since I certainly don't have an original idea like that and is definitely not in the trillion dollar industry. But I think a competitor as at much lower level of competence can still make me nervous. Let's do a thought experiment. Let's say I anticipate IPv6 support will be a highly requested feature, yet I don't really understand it well to implement related features. Should I make myself well-versed in IPv6 before release a MVP (could take a long time)? Or release it first but then spending a lot of time learning it and make users wait, giving competitors opportunities to implement it first (I think many many developers/teams are well-versed in IPv6). Making users wait is itself another concern I mentioned in the earlier reply. |
|
You could simply release it first, then add support later when there are a lot of complaints on it. My preferred approach is to avoid paid marketing until there are no more complaints, but launching should happen early to collect complaints.