The baseline has moved fast this year. AI-generated UI is good enough now that for a lot of products the core screens come out clean on the first pass , dashboard, settings, checkout, all serviceable. That used to be weeks of work for a solo maker. It isn't anymore, and I don't think that's a bad thing.

I'm a UX designer, mostly on complex, high-trust products, and here's where I think it currently stops: AI generates screens, but product experience lives in the sequence between them. The happy path is basically solved. What doesn't come out of a prompt is what happens when someone is confused, hesitant, or something broke empty states, the permission ask that feels invasive, the error that doesn't say what to do next, the ability to undo something. None of those are visual problems, so a tool optimizing for a good-looking screen has no reason to raise them.

I used to skip writing down anything because it was just me and i had everything in my head. But then i took a short break recently and completely forgot why i made certain decisions in the code. Spent hours trying to figure out my own stuff.

Now i just leave quick notes on things that aren't super obvious. Nothing fancy just a line or two so future me doesn't get stuck.

Where do you draw the line between useful notes and just wasting time on docs?

I always thought documenting things was useless if you re building alone

But after stepping away from my app for a couple weeks I came back and had no idea why I set up parts of the product the way I did.

Lately I started taking 30 seconds to write down the reasoning behind tricky decisions. It already saved me a bunch of headache this week.

Curious how other solo builders handle this do you bother writing stuff down or just rely on your commit history?

I m a UI/UX designer and recently started exploring how AI can help bridge the gap between a Figma design and a more functional prototype.

Traditionally, I d create the UI in Figma and then build interactions separately. With the newer AI tools, I m curious how designers are changing this workflow.

For those who work with AI-assisted prototyping:

• How do you go from Figma designs to functional prototypes?

• Which parts of the process does AI handle well?

• Where do you still prefer traditional Figma prototyping?

• Have you found any tools that preserve the original design particularly well?

We almost ran into a major incident recently because a new service silent inherited a production config without anyone explicitly setting it. Because everything seemed to be working normally, nobody realized logging was completely turned off until weeks later.

It made me realize how dangerous "smart defaults" can be when they hide implicit decisions.

Have you ever been burned by a default config that seemed convenient until it silently broke something?

Had five Chrome instances connected to one automation session today. Had to stop and explicitly ask which one was actually signed into the right accounts before doing anything, since picking wrong here does not throw an error, it just quietly acts under the wrong identity.

Never actually happened to me, caught it every time by asking first. But it feels like the kind of mistake that only needs to happen once to be expensive, a post, a purchase, or a message sent from the wrong account with nothing in the UI warning you before it's too late.

If you build or use browser agents across multiple profiles or environments, how do you avoid that. A hard confirmation step, distinct profile naming, something else?

I initially thought of AI as a way to save time on the work I already had. Lately, I am spending some of that saved time doing things I would previously have left alone because I didn't have the skills, budget, or time for them.

For me, that has meant:

• Building automation scripts, including one to generate release notes

• Creating workflows using tools like Zapier

• Putting together working prototypes before building the final version