... became inevitable. VC interest went from red hot to chilled. Someone told me that if you re building a Google feature, it won t be long before Google builds it. They did. So did Superhuman, Read AI and plenty of others. If I did it again, I d find something harder to replicate by going deeper, perhaps rethinking the calendar altogether rather than building an agent on top of it. 2. Pay yourself properly. There is already so much going ... ... market: I speak Portuguese, Mariana is Portuguese and my wife is Brazilian. We ran a test in Portuguese. We recruited 100s of Brazilian users in three weeks, mainly thanks to Ting on WhatsApp. IYKYK . December Based on competitors

... most of the boxes I once set for myself. Now I m in a more interesting phase: working on the things I genuinely want to exist. One lesson came the hard way. Yes, you can build alone. I did plenty of that during Covid and eventually found myself practically scratching the walls from loneliness :)). Remote work is great, but I still believe the best companies are built by people who spend real time together. Sitting across a table, challenging each ...

... tools we simply can t imagine our day without. If I had to pick a few AI tools that have become part of my daily workflow, these would be: ChatGPT + Claude summarising and improving text (and Codex in VS Code for coding) Grammarly AI correcting and improving my English Figma with its AI prompting helps me a lot with improving my graphic design ideas Google Gemini for note-taking from Google Meet, plus AI features in Google Sheets and Docs ... ... These are the ones I use the most, but I m sure there are plenty

... than three years, quietly discovering incredible products, supporting makers, and thinking, "Maybe one day I'll build something of my own." For a long time, that felt unrealistic. My background is in Civil Engineering, not software development. I had plenty of ideas but very little coding knowledge, so building software always seemed out of reach. Then AI changed the way I learned. Instead of waiting until I knew everything, I started learning by building. It hasn't been easy - there ... ... have been bugs, confusing AI outputs, and plenty

... Launching on the 10th of Aug. and doing the last round of prep. I've read plenty of "how to launch" advice, but most of it is written by people selling launch services. I'd rather hear from makers who've actually been through it. Two specific questions: 1. What did you spend time on before launch day that you'd skip if you did it again? 2. What did you almost not bother with that ended up mattering ...

... about where their files are stored afterward. That made me wonder whether modern browser technologies have reached the point where many of these tasks can happen directly on the user's device instead. Building around that idea came with plenty of technical challenges, but it also changed how I think about privacy, performance, and user experience. I'm curious how other makers think about this. If you've built browser-based applications, what challenges surprised you? Do you prefer local ...

... 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 is to design for the exit. Concretely, that means three things. Point users back at real people, not deeper into the app. The most valuable thing an emotional AI can do isn't be a better listener than your friends ... ... more durable one), but because it's the only version of emotional AI I can look at and believe is actually helping. The regulation is going to keep coming. California and China won't be the last. And plenty

... wondering what I'd actually gained. A cohort, a demo day, advice that sounded great in a room and fell apart back at my laptop. Nobody handed me a roadmap and even less the full journey. I also noticed plenty of tools are great at one step, validation here, an MVP builder there, but nobody stitches the whole thing together. You end up juggling five subscriptions and playing your own project manager between them. So I built this platform ...

... wondering what I'd actually gained. A cohort, a demo day, advice that sounded great in a room and fell apart back at my laptop. Nobody handed me a roadmap and even less the full journey. I also noticed plenty of tools are great at one step, validation here, an MVP builder there, but nobody stitches the whole thing together. You end up juggling five subscriptions and playing your own project manager between them. So I built this platform ...

... last week. Single digit upvotes, zero signups. Nobody was rude about it, nobody was anything about it, which is worse. Writing this up because the post mortems I've found useful were always the honest ones, and there are plenty of the other kind. What I got wrong I launched to nobody. I made this account and launched days later. No audience, no comment history, no reason for a single person to care that I'd turned up. The product ...

... Getting started, Authentication, The tabs, Drill-ins & scan, Live & reliable, Themes, Configuration, Scripting, plus a reference pair for every CLI flag and every keybind. https://gfazioli.github.io/octos... The octoscope guide Writing it was its own bug hunt. Plenty of what octoscope does was documented nowhere: the order it searches for your token and the scopes each kind needs, the work filters on the Repos tab, the full config key list with valid values, what the rate-limit chip ...

... intentional while still keeping it fun. Building PairUp has taught me a lot already from WebRTC and real-time systems to SEO, AI moderation, performance optimization, and the challenges of growing a startup with limited resources. There have been plenty of late nights, bugs that took days to solve, and moments where I questioned whether I was on the right path but seeing real people use something you've built makes it worthwhile. I'm here to learn from other ...

... only to personal story (my coding skills are limited since I am trying to learn coding) :D Comment from Nika(@busmark_w_nika): @dinocorreia  To be honest, for now, I was able to find only one competitor of my product. So maybe people do not want it so much. Let's see how good I can be at selling the problem and then selling the solution :D Comment from Nika(@busmark_w_nika): @dinocorreia  I was the very ... ... What is your tool about? What does it do? :) And does it have your first initial testers? Comment from Nika(@busmark_w_nika): @abidhusain  When you describe it like this, it sounds complex. Does it have any competitors

... open a prefilled problem report. Gmail attachments are more reliable Attachment downloads no longer depend on which signed-in device is coordinating mailbox history. We also improved lease recovery when the previous primary device is no longer active. And plenty of quiet reliability work Outgoing messages include the right display name, eligible pre-delivery failures have a safely gated fallback route, stale live-mail connections recover automatically, and app updates replace outdated background services. Both the backend updates ...

... part was the scarier decision. It felt like giving away the product twice. But the people who resell them link back, talk about the brand, and effectively distribute it for me. It's still early and I'm figuring plenty out. Curious how others here think about free vs

... readriff.com Product Hunt: https://www.producthunt.com/prod... Whether you have feedback on the idea, the website, or the overall direction, I'd genuinely appreciate hearing it. Early conversations have already influenced several changes, and I'm sure there's still plenty I haven't considered. Thanks for reading; I look forward to your thoughts ...

... just days before release. Thankfully, recovery is going well, and we've used the extra time to polish the final details rather than rushing the launch. Building Kognis has been an incredible journey. There have been countless late nights, plenty of challenges, and so many lessons along the way but seeing it finally ready to launch makes it all worthwhile. Keep an eye on the Apple App Store and Google Play next week Kognis will officially be launching! I genuinely ...

... reading the code, what is the point of me approving steps? LOL. Comment from Stacy Wycoff(@stacywycof83995): @aadilghani  I don't run coding agents but I have the same read-only vs act-on-it line with FounderFlow (I'm the founder, flagging since it's relevant). Anything that's just surfacing information runs free, anything that would change something real waits for me. Your reset --hard story is exactly why I don't think "let it rip" should ... ... Same queue, totally different urgency. Telling those two apart automatically is the piece I don't have clean yet. In your setup, how are you deciding which of the 20 percent is allowed to wait for a window versus

... best model changes monthly, and rebuilding your stack every quarter has a real cost. In most platform shifts, the fast follower wins (think Apple). But this shift compounds in a way that previous ones didn't. When a competitor retools around agents, they don't get a one-time productivity bump. Their iteration speed itself changes, so the gap between you and them widens every week you wait. I've felt this firsthand. We're 3 people, and we replaced ... ... thing improving. Waiting for AI to stabilize is waiting for the ocean to finish waving. Could be wrong on timing. Distribution, enterprise moats, and a fat war chest can let slow movers coast for years, and plenty

... Ludwinowski(@anna_ludwinowski): @picspace  "What changed for the user" instead of "what did I build" is exactly the right swap! It's the same trap in enterprise IT and in most launches here, just dressed differently (feature list vs. demo). Since you mentioned the sentence changes as you learn: do you have an example of how yours shifted for picspace? Like what the early version of the problem sentence was, versus

... entire roadmap. Comment from Nolan Vu(@nolan_vu): @thenameisarian  Interesting, alternative to LinkedIn you said "Transparency, not hiding" as the positioning is sharp. The whole industry is moving toward pretending AI involvement isn't happening, so calling it out directly and making it a feature instead of a flaw flips the script in a really smart way. Recruiters needing to know what was AI vs

... both content and   product work.   2. Google Search Console I basically live in it. For anything SEO, it's the only honest source of truth   about what's actually happening vs. what I assume is happening.   3. Ahrefs keyword and competitor

... mandated it in school curriculums, but we all know how that goes. It will probably become another filler class that nobody takes seriously. And for the rest of the world, financial literacy is not taught at all. There are plenty of resources out there. Courses, apps, YouTube videos. But how many times have you started something like that and abandoned it halfway through? Not because you are lazy, but because you just do not care enough to keep going. There ...

... actual insight, and it's bigger than it looks: making the notification say why it's waiting is what turns a ping into a triage. "Done" makes you tab back to find out what "done" means. "Needs approval vs finished vs

... ability to own your data and take it anywhere on the internet. This idea wouldn't let us go. No matter how hard we tried to move on, we kept coming back. We pivoted through doubt, market pressure, and plenty of moments where the easier path was to drop the idea entirely. We thought about leaving this vision and building something else multiple times, but just couldn't. It felt like this problem mattered. We went through multiple iterations: data ... ... really sure if the market would shift but I'm not complaining that it did :D We just thought we'd build something and open source it if nobody pays for it. But we wanted to put this alternative