Hey friends 🙂
did you ever want to launch but didn't do because you were not happy with your product yet?
We are at this point right now.
We are afraid that a buggy product will scare new users away.
I am seeking now for YOUR help. 👏
What do would you recommend?
Same stage, same questions :)
Our rule is:
- bug that really disrupts the user flow: crash, not saving, destroying user created content etc --> needs to be fixed
- slowness, fuzzy behaviour, timeouts... case by case but mostly: launch !
- UX improvement, beautifying... definitely on the backlog :)
I know there are different schools of thought on this; I think of it as a chart with 'critical bugs' on the x axis and 'size of launch' on the y axis.
If you're launching to thousands of users and it's really buggy, probably not the best idea since you might turn away people + you just won't have the capacity to fix all tickets.
If you have a buggy product and launch to 100-200 people, could be great to get the feedback you need to move it forward.
Depends on what kinds of bugs do you have. Definitely your app shouldn't contain critical bugs overall. Core featues should work correctly too.
Report
I wouldn't launch a buggy app. There is nothing worse than features that don't work. Instead, I would suggest focusing on a small feature, which solves a problem, making it work, and launching it ASAP.
Report
Build a bug free product. If you were a chef entering a cooking contest, you wouldn't even think about cooking a recipe if one or more essential ingredients were missing. Lunching a buggy product will waste your opportunity to make a great first impression.
Replies
Weavit
Sales Playbooks
Write Panda
Databar.ai
GoIT LMS