... have a multi-step onboarding wizard in Next.js that ends on a generated result page. All my checks passed. Then I finished the flow by hand, pressed the browser Back button on the result page, and landed in onboarding again, not on the main screen a finished user should return to. The cause was one word. Each navigation in the wizard used router.push, which adds a new entry to the browser s history. So the whole wizard stayed ... ... history stack, and Back

... FinderGit 0.58.0: back, forward, and the keyboard Your Mac already knows how to go back

... recently ran into a really annoying bug where a user completed a setup flow landed on the final success screen and then instinctually hit the browser's Back button only to get shoved right back

... Someone cancelled last year. No drama, no complaint. Just gone. They came back eight months later. I asked why they left and why they returned. The answer was the same thing both times. They needed something I did not have, then they did not need it anymore, then they needed it again. Their business changed. My product did not. They were not a bad fit. They were a fit for a version of their company that no longer existed ... ... been thinking about churn as rejection. Sometimes it is just timing. Has a customer ever come back

... everyone! Hypership Day is back on Friday, November 6 , and if you missed the first one, it's the only day on Product Hunt where one product can launch over and over. Here's how the day runs: - Launch in the morning like you would on any other day. - People file requests on your launch: what they want fixed, changed or added. - Ship them. Every request you ship earns points on top of your votes, and the new version goes ... ... straight back

... everyone, Roy here, one of Radar's makers. We first launched here in May, and since then Radar has been installed more than 25,000 times. Today we're back with AI investigations: click Investigate on a failing Kubernetes workload and the agent you already use (Claude Code, Codex, Cursor or OpenCode) digs in, read-only, and comes back

... improve our day 7 and day 30 retention, we set up a automated re engagement email sequence highlighting key features users hadn't tried yet. While a tiny percentage opened and clicked back into the app, the unsubscribe rate was surprisingly high. It pushed us to question whether email drips are still effective for bringing dormant users back

... more sessions at once, so terminal hangs and crashes show up way more often than I'd like. claude --resume looks like it should help, but it doesn't always pull the whole history back. I've stopped relying on it. Our workaround is small. Every time the agent finishes a reply, a Stop hook writes a little card for that terminal pane, holding my last instruction, the tail of the agent's answer, the working folder, and the path ... ... decisions or mistakes, we put it in the project's memory files. That's the only place I trust the next session to look. What do you do when a session dies on you? How do you pick things back

... bringing back something I shelved a couple years ago. My first-ever real-ass startup an online arcade!! I was 21 fresh out of uni, broke, and working as an accountant. I barely knew anything about coding, so I hired an agency to help build what I had in mind. $15,000 later I learned Figma, how to code, found my way around AWS, worked with pixel artists and 3D artists, learned to QA, manage different personalities, kept everyone ... ... tried again with Astra? And tbh I've literally never had this much fun using AI. I'm taking my old game assets and giving them a second life, trying ideas I couldn't pull off on my own back

... later. Maybe you set sessions to 30 days because users hated logging in again. Maybe your permission model started with 3 simple roles and somehow turned into 14 roles nobody fully understands. Or maybe you stored something that, looking back, you probably shouldn t have stored at all. That s the tricky part about auth decisions. Most bad ones don t look bad when you make them. They work. You ship. You move on. Then more features get built around ... ... architecture decisions that cause the most trouble. It s the small defaults nobody thought much about. A token lifetime. A copied refresh flow. A recovery method that accidentally became the easiest way around everything else. If you could go back

... linked tables and automated rules. A week later I noticed I was actively avoiding opening the app because taking a two line note required filling out four different property tags. I ended up wiping the whole workspace and moving back to basic text pages with bullet points. Removing all the fancy automation made updating my notes feel effortless again. What feature finally made you settle on your primary workspace app instead of constantly switching back

... about stability. In fact, she told me multiple times before this that if she had known I was the type to start a business, she wouldn't have married me. Naturally... I started one anyway. So back in early November, when this AI email app idea popped into my head, I had to calm her down immediately. Luckily(?), I was unemployed and had been for a very long time. Looking back

... integrate some sort of tracking :D Comment from Nika(@busmark_w_nika): @raffay_sajjad  Is your tool online? Where can we find it? Comment from Nika(@busmark_w_nika): @oshylabs  But how can I know "came backs" from the Chrome web store page? Comment from Nika(@busmark_w_nika): @oshylabs  I am not in the phase of creating the webpage yet, but will be doing that soon. So let's see how it goes :D Comment from ... ... becomes a "new problem" for you in a good way Comment from Sabber Ahamed(@sabber_ahamed): @busmark_w_nika   @abdullah_javaid3  the random-id-on-activation trick is the right call. weekly active hides exactly the churn-vs

... some point this weekend, a lot of people opened Manus to get back to work and found the door locked. Not over an unpaid bill. Not over anything they did. A $2 billion acquisition came undone, compliance required a deletion, and everything they'd built there since December 29 went dark along with the account for at least two days. The short version of the news: Manus announced on August 11, 2026 that it is returning to independent operation ... ... affected users on or after December 29, 2025 was deleted on August 23 24. The restoration portal opens August 25 at 08:00 SGT. This page has two parts, in deliberate order: first, how to get your Manus data back

... everyone! We're back!!! @Creatium This time with Creatium Coach. Creatium Coach is a lifelike, multimedia coach for people with dreams and goals. Tell it what you re taking on, whether that s closing your first enterprise deal, shipping faster with AI, or learning to lead a team you just hired, and it builds you a journey and coaches you through it live. This isn t another course to click through. You get an avatar coach that talks back

... been saying AI should adapt to you since day one; this is what that looks like as a product. And frankly, a capybara has the right temperament for the job: unbothered, takes the task, does it, puts the result back where it belongs, and tells you what it did on the way out. Here are five days at the office. Example 1: A reading list that annotates itself (Notion) Everyone's Notion has a "books to read someday" table ... ... sign-in Happycapy sees only the pages you allow. It works in the open: thinking time, steps completed, which tool it's on reported as it runs. You go refill your water. By the time you're back

... still got it wrong . To everyone who upvoted and supported us along the way: it meant more than you ll know. I hope some of our lessons help you get further than we did... Three lessons I keep coming back to First, the lessons, in case you churn before reaching the timeline. 1. Simple and obvious is good. Hard to replicate is better. Ting always felt obvious to me. Why wouldn t you want to CC an AI into ... ... where mistakes and losses are discussed and owned quickly. You ll find a new speed. You can never go wrong reporting the truth. You can go very wrong reporting an abstraction. The 18-month timeline January 2025 I got back

... deal with a growing problem: AI-generated assets are created everywhere, but the final design work still needs to live in Figma. We're exploring a workflow where outputs from different AI tools can be automatically organized and pushed back into Figma, reducing manual copy-paste and file management. I'm curious: Are you using multiple AI design tools today? How much time is spent moving assets back

... quad (both always present, normalized 0 1000), verified, review, and the raw evidence behind that verdict. review is the summary: declared, returned, boxed, verified, flagged[], by_reason. image is the source size, for turning the normalized boxes back into pixels. Full shape with a worked example: https://space-ocr.com/docs#post-... The reason is that the old shape put my keys and your keys in the same object. Every value you asked for sat at the top level next to field_bboxes ... ... migrate what is stored. The new shape is built at the serving boundary by one pure function with its own tests, and stored results are converted as they are read which means results from before the change come back

... Every business I have run had a version of this. A lead who asked a good question and never heard back from me. A client who mentioned something felt off during a slow week, and I told myself I would circle back

... across 19 different companies in DTC and SaaS. If a subscription business keeps just 5% more of its customers, profits jump somewhere between 25% and 95% . That single stat pulled me into retention work years ago. I never got back out. Here's what those years taught me : most churn isn't a product problem. It's an operations problem. The right message usually existed. It just fired at the wrong time, or reached the wrong persor, or never went ... ... because someone would have had to send it by hand. Every day. Forever. Two more numbers , so you can see the size of it. A generic "we miss you" email wins back

... three different continuations. Ours is worse than a bit and no more useful. The reason we hand back is a sentence, denied from your phone plus whatever the person typed, or nothing at all when they just tapped no. Expressive and unroutable. We also proved the fix and never generalised it: there is exactly one typed third value, defer, meaning hand this back

... optimize an emotional product for time-in-app, you will build something that makes people slightly worse and your metrics slightly better. The incentives are pointed the wrong way by default. So here's the principle I keep coming back to, and the one I think outlasts every new rule that gets written: the goal of emotional AI should be to make itself less necessary over time. That sounds like heresy in a category obsessed with DAUs ... ... inside your app if they can only feel understood while they're talking to your model you haven't solved loneliness. You've made it more comfortable to stay lonely. You've built a very sophisticated waiting room. The alternative

... Product Hunt(ers) We launched Collabwriting for Teams here in 2024, hit #1 Product of the Day, and then went quiet. We went heads-down to build, and told ourselves we'd come back when we had something worth saying. Two years later, here we are. Back

... been missed. It wasn't even a hard case, the file just wasn't in the directory it happened to grep first. What was your moment? And did it actually change your workflow afterward, or did the trust creep back in after a week like it always seems to for me? Comment from Ghost Kitty(@ghost-kitty-10022100): Comment Deleted Comment from Stephanie Tang(@stephanie_t0317): Mine wasn't a catastrophic error either. It was when an AI agent silently ... ... trust, and it does not need to be a big change. So we built a check for exactly that: every "done" is compared with what really changed on the site before the owner sees it. Trust does not come back