With so many AI tools popping up every week, I m curious:

Which ones have actually stuck around in your workflow?

• Are you using anything for image/video generation?

• Got an underrated writing or code assistant?

• Something that helps automate tedious stuff?

Would love to hear what s been useful (or surprising)!

A couple of years ago, a designer would hand off a Figma file and that was pretty much the end of their involvement. Everything after that belonged to developers, and a lot of nuance got lost in between: wrong spacing, animations that didn't quite work, "that's not how it looked in the mockup."

That line is blurring now. AI tools like Cursor, Lovable, or Claude Code let designers go beyond drawing an interface and actually build a working prototype with real code. Not production-ready, but enough to:

• Test a hypothesis in hours instead of sprints

• Show the team a clickable, living interface instead of a static image

• Shorten the distance between an idea and real user feedback

I've been working this way myself for the past year: designing and, in parallel, taking things far enough that a developer isn't left interpreting a mockup, they're refining something that's already close to functional. It changes the role itself, from "the person who draws things" to "the person who brings the product closer to reality."

I recently launched my first wellness app, Momentia, a mindful journaling app designed to help people check in with their moods quickly. It s been a rewarding (and humbling) experience, and I wanted to share a few lessons that might help other makers in this space:

1. Simplicity wins. People don t want a complicated system when it comes to journaling or mental wellness. Small, consistent actions matter more. I discovered this both in my own wellness journey and from early test users.

2. Community > marketing spend. The most valuable traction so far has come from engaging with communities like this one, not ads.

3. Your own habits matter. I ve found myself becoming the best test user using the app daily gave me insights I d never get from wireframes or specs.

4. Feedback is gold. Early testers and even casual users often highlight things I would ve missed as a builder. Just the other day, an early adopter gave me unsolicited feedback in a casual conversation and it turned out to be incredibly valuable.

Launching something in the wellness space has reminded me how important it is to keep things human and approachable. Momentia started as an idea to help me, and I can only hope it helps others, too.

When you re building a startup, nothing is ever enough.

More users, a new feature, a bug. MRR, churn. It's hustling all the time. and pretty uncomfortable sometimes.

I tend to forget the day to day, and just think about tomorrow.

Hi everyone We had some good momentum and amazing customer support during our PH launch. Now I m exploring how to keep that momentum going and actually build a community here (instead of defaulting to Slack or Discord). How do you move beyond just initial discovery and engagement?

Has anyone tried using Product Hunt itself as the community hub for your product? Any tips on how to approach this?

I ve found this community very vibrant and helpful, especially if your ICP is early stage founders and builders. I d love to learn how others have deepened that connection and grown their community right here.

Every week brings new launches, and I try a lot more tools than I keep. My filter is simple: does it replace something I already use, and do I still open it after two weeks?

For example, I tried three different note-taking apps this year. Two were beautiful but I stopped opening them after a few days. The one I kept looked plain, but it saved me time every single day.

It made me wonder if my filter is too strict, because the boring tool beat the flashy ones.

How do you decide what stays in your stack? Have you ever kept a tool that failed your usual test?

Building completely in isolation feels like a trap. As a solo builder, I want to spend my early stages connecting with people who are on the same path, rather than just silently working behind closed doors.

I'm curious about how people here cultivate meaningful connections before their big release day.

• Exchanging value: How do you approach offering help or sharing unfiltered thoughts on someone else's work without being intrusive?

• Community interaction: What are the best practices for starting real conversations in community spaces without sounding like you're trying to push something?

• Staying accountable: How do you keep in touch with peers who share similar challenges in tech and design?

For anyone who has navigated this phase successfully: What was the single most effective habit or action that helped you meet great collaborators or peers here?

A student might finish a lesson and do well on practice questions, then struggle when asked to explain the same idea aloud.
Understanding something privately and presenting it to others seem like different skills.

For people who have built or used education tools: have you found a way to help with that step?
Would you use a short spoken explanation, audience questions, peer feedback, or something else to help a student practice?

I m especially curious how you would tell whether a student understands the topic better, rather than has simply memorised a polished answer.

Most of what I build is a better version of something that already exists. My company is 22 years old, and the pattern has barely changed:

Start from a tool that I or a client already use and aren't happy with

Make it better, and price it a little below the competition

Never raise the price. I haven't once

Writing code got cheap. Checking whether it did the thing did not, and the gap between those two is where I spent a whole day.

None of what follows was broken. Every line ran as written, raised no error, and reported success. That is the part worth talking about, because I think it is the real failure mode of this era and it does not look like a bug.

One. A refresh job reported one item refreshed. I checked the field that records when a price was last written and it had not moved. The counter incremented when the call returned rather than when a value was written, so it had been reporting success for as long as it had existed. It could not have reported anything else.

Two. A refresh path read one field name while the scraper was sending a different one. One word apart. When the price failed to parse, the missing field fell back to a default meaning the product does not exist, so live and in-stock listings were stamped as dead and pulled off a storefront. There was a comment directly above it explaining that a three strike threshold protects against exactly this. The threshold does nothing, because the validity check in the same function also requires a price and there was none. One event was enough. I found it by triggering it on my own site and taking two working products down.