I asked Claude to build me a landing page. It took 40 seconds.
Getting it live took 3 hours.
Not because I'm bad at tech. Because the entire hand...
For further actions, you may consider blocking this person and/or reporting abuse
The "deploy hell loop" framing is spot on. The gap between "AI handed me the code" and "it's actually live" is where the real friction lives — and it's not a code quality problem, it's a deployment UX problem. The Chrome extension approach is clever: embedding the deploy flow where the conversation already happened removes the context switch entirely. Have you thought about a /deploy endpoint or a Vercel integration that Claude could call directly from the chat?
Exactly. That context switch is the killer.
A direct deploy endpoint is definitely something I’ve been thinking about. The tricky part is making it feel safe and predictable, because people need to preview what is about to go live before an AI agent pushes it somewhere.
A Vercel integration could make a lot of sense too, especially for users already in that ecosystem. For now, I started with the Chrome extension because it keeps the flow inside the chat and gives the user one last review step before deploy.
i totally get your frustration with the deployment process-it's often way more complicated than it should be. moonshift simplifies that by letting you get a full next.js + postgres + auth build deployed in about 7 minutes. you own the code on your github, and it's a flat per-build cost. how about a free run to try it out, no strings attached?
Totally agree that the deployment layer needs to get simpler. Moonshift sounds like it’s tackling a bigger full-stack use case, which is really interesting.
My pain point here was even more basic: someone has a single HTML page from Claude or ChatGPT and just needs a live URL without setting up a repo, terminal, framework, or environment.
Happy to check out Moonshift though. The more tools that reduce deployment friction, the better.
Yep, this is painfully relatable. Making the page is the easy part now, but getting it live can still turn into a weird maze of tabs, docs, and outdated tutorials. Pretty cool that you just built the thing you wished existed. Do you reckon this becomes built into AI tools eventually?
Yep, I think some version of this definitely becomes built in eventually.
But my guess is AI tools will solve the basic version first, like publish this as a temporary page or export to a simple host. The messy part is still everything around real deployment: previewing mobile before it goes live, choosing Netlify vs GitHub vs FTP, reusing your own hosting, keeping history, not losing the final URL, that kind of thing.
That is the gap I kept running into. AI had already solved creating the page. I just wanted the last mile to feel as simple as the prompt that created it.
Whenever I start a new project, one of the first tasks is deploying!
Same ❤️
Been there. Spent way more time fighting deployment tools than actually building. Worst is when the tutorial shows a button that doesn't exist anymore.
That outdated tutorial problem is so real.
You start with a simple goal: get this page online. Then suddenly you’re decoding UI changes, old docs, random menu names, and missing buttons.
That was exactly the moment I realized the issue wasn’t building the page anymore. It was all the tiny assumptions hidden in the deploy process.
Super relatable. AI speeds up page writing, but deployment setup always costs most of the actual working time.
Exactly. The code generation part feels almost instant now, but the setup around deployment still has all the old friction.
That was the weird realization for me. I was not spending 3 hours building the page. I was spending 3 hours turning a finished page into a URL I could actually share.
That gap feels small until you hit it over and over. Then it becomes the most annoying part of the workflow.