Novruz Veliev

AI is great at producing a first landing-page draft. The last mile is still human: make the promise specific, make the CTA match the next action, remove repeated filler, add a link or table only when it helps a visitor decide, preview the whole page, and export the reviewed HTML.

HtmlDrag gives teams a visual working copy for that focused pass. Keep the HTML that already works instead of restarting the page because one visible decision needs correction.

Hey everyone,

I'm Novruz, a QA engineer. My job is unglamorous: I click every path a real user might take through an app, then write down exactly what breaks and the steps to reproduce it.

Lately I've been doing that specifically for apps built with Lovable, Bolt, Cursor and Claude. What surprised me is how repetitive the failures are. Across very different products, the same four keep showing up. The signup or password reset email never actually arrives. A form fails silently, so the user thinks they saved something and they didn't. One account can see another account's data by changing a number in the URL. On mobile you land on a screen with no visible way back.

None of these show up while the maker is clicking through their own happy path. They show up on the second user.

Doing one of these because I get more from reading what others are building than from any newsletter.

I'll start.