Hey folks - I'm curious what is the primary reason you launch on PH. Is it to get initial traction, or is it feedback? I've launched a couple of products on PH and I've definitely seen an SEO benefit, my search rankings went up both the times and I got new backlinks. I've not yet seen high intent users coming through, is it dependent on the launch category positioning?
I've recently been recommended various new tools like Warp (terminal) and Zed (IDE). They are both quite intriguing, as I expect both could help speed up my development workflow. However, actually switching to them seems to be a huge lift. I've downloaded and explored the two apps, but the thought of figuring out which current habits can be replicated vs. which ones I should completely relearn with the new app's tools is quite daunting. As a result, I haven't re-opened them... I think the ProductHunt community would lean on the side of more experimental and motivated to try new things. How many new products do you try? How many end up sticking? Do you also feel the obstacles I've mentioned above and what ends up pushing you over that activation energy?
There was a lot of talk in 2023 and 2024 about startups using a one-time payment model, but earlier this year, I started to see founders going back to subscriptions. What do you think?
We launched our community platform on product hunt, I then realized that it would make more sense to ask this question in the community. Community builders are using different tools to manage their communities. Engagement is an important metric to check the health of the community, so which of the below features is the most important or do you think the combination of these features will help you build engagement. Please comment with your thoughts that are not limited to features listed in the poll
We are have different reasons for doing the things we are doing, It would be really helpful to share what is your "why" for being here? What fuels you to do the things you are doing, what is your motivation or goal so to speak. Lets share and discuss perspectives!
It used to be fashionable to be "in stealth," but then our collective wisdom shifted to "launch early and launch often." In my experience, there are two good reasons for this:
The first reason is that it's often more important to figure out whether people want what you're building than it is to figure out whether you can build the best possible version of it. Launching early gives you the opportunity to either pivot or iterate quickly. Launching is learning.
I ve been testing a safety check for an AI app by running a script of test messages many times against the model. Every run was fine until it wasn t: after a day of repeated runs, calls started failing with 429 errors, and waiting 60 seconds between retries stopped helping.
I assumed the limit was per minute. It wasn t. On the free plan for the model I use, the limits are 30 requests a minute, 1,000 requests a day, 8,000 tokens a minute and 200,000 tokens a day. I believe I hit the daily cap, because the app itself also stopped generating responses at the same time. My tests and the app share one account, so they share one budget.
What I m changing: run tests in small batches, never repeat full runs, and plan a backup provider so a quota problem doesn t become an outage.
How do you keep testing from eating your production quota? Separate accounts, a cheaper model for tests, or something else?
