Congrats on your late Launch HN. Everyone's going to ask this question but, in a world of AI/LLMs, why wouldn't I just build it myself in 10 min
adeelraza 31 minutes ago [-]
Totally fair. You can build the first 10-minute demo with an LLM now.
The hard part is usually what comes after: editable state, templates, email-safe HTML, PDF/export pipelines, assets, permissions, custom blocks, previews, and all the rendering edge cases that show up once real users depend on it.
AI also makes structure more important, not less. That’s why we launched Unlayer Elements: instead of having an LLM generate a static blob of HTML, it can target structured components that map back into an editable email, web page or document.
So I'd use AI to prototype it. I'd use Unlayer when that content layer becomes production infrastructure you don't want to maintain yourself.
greenhat76 23 minutes ago [-]
I see this question a lot. Not associated with OP but most companies don't want to maintain a bunch of vibed up apps they don't understand.
I work outside of SV in the southeast and most businesses know AI is being used for products they use but they want experts in that field behind that.
adeelraza 17 minutes ago [-]
totally agree!
iAMkenough 25 minutes ago [-]
As a content creator, this intrigued me until I saw the AI-generated overview video front and center on the homepage. The subtext communicates that the product was designed for fake people standing in front of large fake touchscreens dragging fake elements around.
adeelraza 17 minutes ago [-]
Fair critique on the video :') We’re working on a studio-recorded version, but didn’t want to delay the launch, so we hacked this together as the script/placeholder for now. The demo is completely, 100% recorded in blood and flesh of a human: https://www.youtube.com/watch?v=0HsDtNkdMpM
iAMkenough 5 minutes ago [-]
hell yeah that’s what I was looking for
Rendered at 16:44:40 GMT+0000 (Coordinated Universal Time) with Vercel.
The hard part is usually what comes after: editable state, templates, email-safe HTML, PDF/export pipelines, assets, permissions, custom blocks, previews, and all the rendering edge cases that show up once real users depend on it.
AI also makes structure more important, not less. That’s why we launched Unlayer Elements: instead of having an LLM generate a static blob of HTML, it can target structured components that map back into an editable email, web page or document.
So I'd use AI to prototype it. I'd use Unlayer when that content layer becomes production infrastructure you don't want to maintain yourself.
I work outside of SV in the southeast and most businesses know AI is being used for products they use but they want experts in that field behind that.