TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Best Practices for Developing MVPs

1 pointsby gerroo8 months ago
Hey!<p>I&#x27;ve been recently (2-3 months ago) affiliated with a startup at the idea stage and I&#x27;m the only developer. I developed the MVP, which is pretty much done, but the other founders are asking constantly for revising certain parts. I think we should have released the MVP within a month and iterated but I cannot seem to convince them to put this version in front of some users.<p>So my question is, What are some best practices for developing MVPs? How should a technical person communicate with non-technical founders pre, during and post developing the MVP? How is this different from iterating on an MVP?<p>I feel like I need a different process for going from 0 to 1, then iterating on an already built product with some users. What is that process?

1 comment

sherdil20228 months ago
Run - if those ‘founders’ keep insisting to revise instead of putting the current MVP in front of users. These kind of founders are useless and you should steer clear of them.<p>There are no best practices that are universally applicable. Some don’t even like the concept of MVP. But putting a product in front of users - however clunky the product is - is the best practice.<p>Get early feedback, prioritize, iterate - rinse and repeat. That is all there is to it.
评论 #41488912 未加载