I've just made the most difficult decision to put off my product launch until after a week later because I thought we are not ready. A few shake-ups here and there. But this, in my opinion, while it is a setback, I see it instead as an opportunity to re-evaluate what we currently have. And make sure we get it right with our launch. We're working on making our product worthy of this community. And we are working hard at it. What is a non-negotiable for product launches in your opinion? Let's hear your thoughts. UPDATE: We finally fixed the issue we had and resolved to go live this Saturday. :) I can't thank you all enough for all your amazing answers. We'll keep working hard on our product even post-launch. But of course, those early feedbacks will be vital to our growth. We are going live on PH on Saturday. Please find us here: https://www.producthunt.com/prod... Thanks for your support.
When the market meets your product for the first time, users often share feedback, either lositive or negative.
What was your experience?
How did you handle it?
Did you face a lot of quality issues? Please share!
Do you test it yourself?
Hire an expert?
Beta testing with F&F? Would appreciate any feedback about you past launches, as well any upcoming ones. You only launch once, better do it well..
As AI has become a significant part of our lives, and becoming an integral part of software products, question comes to mind - how do you test it?
Or, maybe, the more important question is - can you test it?? Well, as some of our business partners and clients have come to the point where these questions require answers, I ve taken the liberty to dive into it. Lets, first of all, set the ground here:
AI is not the only component of your product.
Its probably the most unique one, but it is surrounded by some user interface (graphic, API or SDK), it probably saves some data to some kind of a DB. All of these components require testing, otherwise your product will lose its value. Now that we ve established that, how do you test the AI component?
Well, conceptually, you can t really know if the machine is right or wrong - that is its added value, it provides something the human brain cannot.
However, you can test the AI component, by using itself as a reference.
In software testing, we usually isolate one of the variables and test the code accordingly. So, lets say your AI component is trained by a certain data set. And you inject some kind of input values to retrieve a result. You can create a matrix, combining different input values and different training data sets, isolating each one at a time, and compare the results.
The combination of the results, crossing them and comparing them, will provide you great clarity of your AI s quality. There s still much to be learned and investigated here.
We are at the beginning of the road, but its an exciting one. We will let you know how it goes - follow me for future updates. Please share your thoughts about this concept, I d really like to get some more ideas from the crowd.
Good morning fellow Hunters!
I m having a low-energy morning.
Was wandering, what makes you keep going when things get rough, and don t go your way? Please, do share.
Each MVP is an entirely different experience. I would be happy to hear about your insights, lessons and overall Do s and Dont s. Please share your stories!
Once you launch your pilot/MVP version, feedbacks start flowing in, including bugs. How often, if at all, do you release a new version to satisfy your pilot/MVP users?
Your first payment is a cause for celebration.
I d be very happy to learn at which stage along the way have you decided its time to start charging for your product s services? What made you take the leap? Please share!
Hi all,
We're having a free webinar:
Build, plan and manage your MVP: a practical guide to establish traction. Please join us on July 27th.
This is our 2nd time having this webinar, the first one received great feedback!
https://www.linkedin.com/events/...
Imagine your product is due to be launched tomorrow morning.
You re very excited, but also kinda concerned.
What would you consider as the worst outcome? Please share!
Production bugs are often inevitable, and usually result in some angry users.
While this is a mess on any step of the way, it could be devastating for a relatively new product in the market. Please share if how often does your product face such bugs, and how do you handle the situation?
How do you prevent them?
Hi founders, Does your product keep facing repeating production environment bugs? If so, I would like to meet you for a short talk, trying to learn how Production Bugs handling and prevention. Please hit me at tal@quqliteams.com
