A quick thank you to everyone here
A few weeks ago, we launched PSI Lynx on Indie Hackers and got far more feedback, comments, and product suggestions than we expected.
Some people tested the product. Some pointed out UX issues. Some challenged our assumptions. A few even became early users.
That feedback helped us improve the product much faster than we could have done alone.
Over the last few weeks we've cleaned up a lot of the user experience, improved navigation, added clearer recommendations, introduced CrUX history tracking, and expanded monitoring capabilities beyond simple Lighthouse audits.
The product is still evolving, but it's already in a much better place than it was on launch day.
If you checked PSI Lynx during the launch, feel free to take another look.
You can create an account, add a project, and see what's changed for yourself.
And if you have more feedback, feature requests, or criticism, we're still listening. That's honestly been one of the most valuable parts of building in public.
Thanks again to everyone who took the time to comment, test, and support us.
https://psilynx.com
This is exactly what I needed to read today.
I'm building Mazora (an AI product context tool), and I've posted twice on IH but got almost zero engagement. Reading this made me realize I'm doing it backwards, I'm broadcasting instead of building in public.
A few questions for you (genuinely curious):
How did you get people to actually test PSI Lynx during launch? Was it a specific post format, or did you reach out to people directly?
Did you have a clear ask? Like "I need feedback on X" vs. just "here's my product"?
How long did it take before you got your first real tester?
The reason I'm asking: I think I've been too vague about what I'm building and who I'm building it for. Your post shows that clarity + iteration + gratitude = community. I'm going to rethink my approach.
Thanks for sharing this. It's actually more valuable than any product launch post I've seen.
Thank you, and honestly, we're still figuring it out ourselves.
For us, the first users came from a few different places.
Product Hunt definitely helped. We also got surprisingly early traction from SEO. Some of our articles started ranking much faster than we expected and brought in people who were actively looking for solutions to performance monitoring and Core Web Vitals problems.
Another thing that worked well was reposting content into relevant LinkedIn groups and communities where SEO specialists, developers, and website owners already hang out.
As for feedback, I completely agree with your conclusion: you have to ask for it.
A lot of founders post "here's my product" and hope people will engage. We had much better results when we explicitly asked people to test something, share their thoughts, point out problems, or tell us what didn't make sense. People are often willing to help, but they need a reason to jump in.
And don't worry too much about low engagement at the beginning. Some of our posts got almost no traction as well. The key is staying visible, sharing what you're learning, and making it easy for people to understand who the product is for and what problem it solves.
Good luck with Mazora. Product context is a very interesting space right now, and it sounds like you're already asking the right questions.