Subscribe
Sign in
  1. Discussions
  2. Bugs & Sales: How much do you actually test your products?

Bugs & Sales: How much do you actually test your products?

Mark
6 replies
We all know they're inevitable, but here's the question: how much emphasis do you place on noticing and fixing bugs before they make their grand entrance into production? Are you part of the camp that meticulously hunts down every bug, ensuring a squeaky-clean product? Or do you think a few bugs here and there don't hurt, as long as they're not deal-breakers? Share your thoughts, experiences, and anecdotes. Also, do you think that bugs impact your sales and if so, how much? By the way, I've been doing a bit of research on products from PHunt. It's fascinating to see how many projects come out with bugs, and I'd be happy to share some stats, without mentioning any names (unless you want me to contact you in private). Have any of you discovered bugs in products on PHunt? Jump in, share your insights, thanks.

Replies

orliesaurus
I am working on a solution to help people solve bugs quick-er while testing (spoiler alert: it's listed on my twitter, but im not here to self promote)! So this is a topic close to my mind right now! I agree with the person who said not all bugs are equal. I think the issue is that most people are too close to the product to actually test it as a user
Share
Apollon Latsoudis
Well it depends on how thorough you have been in testing your product before fully launching. That is why soft launches are important. Onboard users, offer bounties for bug discovery and prioritize fixing those which are essential for a smooth user experience. You certainly cant fix them all but you can make sure that those that remain (scheduled to be fixed at a later date), will not provide any friction during the use of the software. If you opt to fix all bugs, you may miss critical deadlines or optimal launch dates. On the other hand, if you miss out critical bugs, the sales will definitetly be affected. I have at least twice seen product reviews being overwhelmingly negative for reporting user experience affecting bugs
Share
aiforme.wiki
Ah, the age-old struggle of bugs vs. perfection! Some meticulously chase every bug, aiming for a polished product, while others embrace imperfection, as long as it's not a party crasher. Now, do bugs affect sales? Absolutely! A bug can turn a celebration into chaos faster than a confetti cannon misfire. Customers' trust takes a hit, and they might leave the dance floor early. But here's the twist – not all bugs are deal-breakers. Some linger inconspicuously, like wallflowers at the party. And for the brave souls who've explored the PH realm, yes, they've stumbled upon their fair share of buggy surprises. It's a bit like a glitchy treasure hunt!
Share
Mark
@akanksha_hunts Well put, I love your reply 😁
Share
Daniel Hunt
There's at least a dozen things to optimize and bugs is only one of them! Especially for products that don't already have loads of users, it makes sense that fixing every bug isn't the top priority. I think I'm probably creating a couple of bugs on a daily basis right now but that's part of a conscious decision to ship and launch faster rather than spending too long polishing and polishing.
Share
Mark
@daniel_hunt4 I agree, based on the stage of the project we should look at the bugs in different way. But anyway, once it is published and is getting traction, testing and fixing bugs should be a regular task for any project. Some early bugs that are making user experience bad, slow or in anyway disturbed, could potentialy ruin the reputation, especially with non-tech people.
Share