Wired up a connectivity check on a health app I am building and hit a gap that felt obvious once I saw it. The OS reports "connected to wifi" the moment it associates with an access point, before DNS or the actual gateway path is confirmed. So a captive portal at an airport, a hotel router with no WAN, a home router that lost its upstream link, all read as online while every real request quietly times out.
Ended up not trusting the OS flag at all. The check now does a real DNS lookup against a known host with a short timeout before marking anything online, and only flips the app into offline mode once that actually fails. Adds a few hundred milliseconds to every check, worth it for not showing a broken screen while telling the user everything is fine.
Shady guy- claims to be a top hunter but is here only for scamming genuine makers. He takes money to hunt a product with some silly claim of refunding the amount if the product doesn't make it to top 10 on the day of launch, and then will ghost you, keep shifting launch deadlines at his whim, and take no accountability after launch. And of course the money would never come back. Just wanted to beware the community before anyone considers him as a hunter.
This is also a feedback on the product hunt platform, as to how some good communities that start with good intentions, end up being gamed because of their own rules and users become victims.
I am a first time founder and planning to launch our product on product hunt. Any suggestions on the approach and also other platforms to look at for launching?
The trick is simple. Raise the price for a week or two, then relist it at the "discounted" price, which is actually just the normal price with a strikethrough next to a number that never really existed. You feel like you got a deal. You didn't.
What got me thinking about this: the products doing it best aren't obviously sketchy. Good ratings, real-looking reviews, established sellers. The fake discount is often the only tell, and most people don't check price history before buying.
Ran into something this week that's been bugging me: gave a local model the exact same prompt, replayed it twice with nothing else different, and got a correct answer once and a wrong one the second time. Not a hard edge case either a pretty basic task it clearly CAN do, it just didn't do it reliably both times.
Made me rethink something: a lot of what gets blamed on "the model isn't good enough" might actually be a consistency problem, not a capability ceiling. Those are very different things to fix capability needs a bigger/better model, consistency might just need lower temperature, better prompting, or accepting you need a verification step regardless of model size.
Curious if others building with LLMs (local or cloud, doesn't matter) have run into this do you design around inconsistency (retries, verification passes, structured output constraints), or has this mostly not been an issue for what you're building?
I ve been thinking about a problem that seems to become more difficult as products grow: adding features can make a product more capable while also making the experience harder to understand.
A product might start with one clear workflow, then gradually add dashboards, integrations, settings, automation, notifications, and other features. Eventually, the challenge isn't necessarily what should we build next? but how do we keep the main experience simple?
My instinct is to separate the core workflow from everything else and make secondary features progressively discoverable rather than putting everything in front of the user at once. But I m not sure that works equally well for every type of product.
For people who have built or redesigned products as they grew: