Congrats on the launch, and welcome to HN. This is a real problem and it is good to see more teams taking it seriously. For a bit of context, and full disclosure that I am on the other side of this market: we built Beefree SDK around almost exactly this use case about ten years ago. We started with an embeddable email editor and expanded into popups and web pages over time, so the pain points you describe, Outlook quirks, merge tags, exports, versioning, localization, plus many others like security, scale, and collaborative editing, are all very familiar to us. I am not saying this to rain on your parade. The category has been maturing for a while now and there is genuinely room for good products in it. Honestly, HN was a big part of how we got off the ground in the early days. A launch post (https://news.ycombinator.com/item?id=8474744) is a lot of why we were able to grow and develop at all, so I have real appreciation for founders sharing their work here. Happy to compare notes any time.
mandymoorefan 1 days ago [-]
Marketing site feedback - Use of the primary color in the checkbox is confusing at a glance. I see a red like color and think "Oh they don't support s3"
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 1 days 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.
jvwww 21 hours ago [-]
Really? You couldn't write this message yourself and had to ask an LLM. At least make it less obvious.
all2 20 hours ago [-]
If you spend enough time with an LLM and aren't paying attention, you'll pick up on its mannerisms. I did this awhile ago (the "its not this, its that" thing) and someone here called me on it. After that callout, I've tried to be more aware of how much of that stuff leaches into my head and out into text.
jvwww 20 hours ago [-]
While that may be true, in this instance the whole thing is 100% AI generated and this is not someone who has just adopted the mannerisms of AI.
For instance, the usage of "Totally fair" and "The hard part", the usage of colons, which humans would use far less frequently, using the rule of threes (editable email, web page or document), etc.
Anyway, it's just lazy. This is someone trying to sell their product. They should be able to speak about it without using the exact response from an AI
christoff12 19 hours ago [-]
How would we rate this revised version on a scale from 1-10?
"""
Totally fair. You can build the first 10-minute demo with an LLM now.
The hard part is usually what comes after. You need editable state, templates, and email-safe HTML. Then come export pipelines, custom blocks, permissions, and all the rendering edge cases that show up with real usage.
AI 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 made a deslopper[1] tool based on a new skill[2] I saw on twitter earlier. It's still a little smelly imo, but better.
To be blunt, I would rate it a 1, a 0 if I could. I would stop reading after the third sentence. FWIW, humanizers do not work. Can they make AI text sound better - yes, but only mildly. Also, they won't trick good ai detectors, and the resulting text is still cumbersome to read.
This is what I got first time with a humanizer I built, still sounds terrible:
"Yeah, an LLM gets you the 10-minute demo now.
The expensive part is everything after, once real users depend on it. You end up maintaining editable state, templates, email-safe HTML, export pipelines, asset handling, permissions, custom blocks, and live previews. That takes months.
Structure makes AI output usable here, and it gets more important as the workflow gets automated. That's the idea behind Unlayer Elements. The LLM generates real editable components that map back into the actual email or page, and you keep editing what it makes like anything else in the tool.
I'd prototype with the LLM. I'd bring in Unlayer once that content layer becomes real infrastructure you don't want to own yourself."
all2 18 hours ago [-]
My version, off-the-cuff:
"""
Making a demo that does some things is easy. Making a demo that does all the things is hard.
We took a lot of time to make this product polished. We nailed down a lot of UX gotchas and a lot of bugs that come from poorly written back-end code.
If you don't need the polish, then a demo is more than sufficient. We built this for those who just want to ship, not fight with their agent about tech stack stuff.
"""
hanspagel 6 hours ago [-]
You are right to push back on this.
greenhat76 1 days 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 1 days ago [-]
totally agree!
leftnode 1 days ago [-]
Not the OP, nor do I have any relationship to them, but I've had to build or maintain plenty of these in my time and sure, an LLM can knock out a basic one easily, but there are so many edge cases that need to be accounted for that it gets complex quickly.
Congrats on the launch - this looks like a genuinely useful tool. I look forward to checking it out.
adeelraza 1 days ago [-]
Exactly. You realize that after going through the whole process.
Natalia724 19 hours ago [-]
I think the key issue is not whether an LLM can make a 10-minute demo, but who maintains all the edge cases afterward: template state, email-safe HTML, export, permissions, custom blocks, and previews. Which part is usually the hardest for customers to integrate today?
adeelraza 9 hours ago [-]
Yes, maintaining is the real issue. And also battle testing the quality of software.
edc88 1 days ago [-]
Congrats on the launch! Elements seems really useful and practical, what's the response been from builders so far?
adeelraza 1 days ago [-]
We’re seeing really good momentum with our open source projects. React email editor and elements.
dbbk 22 hours ago [-]
Vibe coded website that looks like it was one-shotted in 5 minutes. Doesn't even work on mobile, the copy wraps off the screen. How can we take you seriously?
m4rkuskk 21 hours ago [-]
I had to close the page after 5 seconds, seeing the AI slop.
clickety_clack 1 days ago [-]
If this can fully replace something like postmark plus do documents it could be very interesting. I might try it out in a year or so if it’s still around.
Congrats on the launch, but don't mostly people use AI now for most of the ui and frontend tasks, why would they go through all of this if they can just ask AI?
adeelraza 9 hours ago [-]
AI needs structured output and that’s exactly what Unlayer Elements provides for emails and documents. And visual builders on top of that.
iAMkenough 1 days 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 1 days 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 1 days ago [-]
hell yeah that’s what I was looking for
0xnyn 1 days ago [-]
Was ready to try this until I saw the launch video. It's pure AI slop.
If that's the first impression you're giving, you're underselling what looks like a legitimately useful product :(
adeelraza 1 days 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. But this is our launch video, completely, 100% recorded in blood and flesh of a human: https://www.youtube.com/watch?v=0HsDtNkdMpM
mchusma 1 days ago [-]
My 2 cents, all these high level videos kind of suck, even the professional ones, when they don’t show the product. Even videos I produce for this purpose! I don’t think this is that bad. I’ve seen worse.
0xnyn 1 days ago [-]
haha, fair enough 03:42 does the product justice :)
themanmaran 21 hours ago [-]
FYI we've built this internally and it was a pain, so I was excited to check out what you've built to see if it was a good fit for us.
But your landing page + video was just slop city. Removes 100% of credibility for me.
I know the advice is launch early and often, but honestly I would just point people to the github until you have something better.
cyberax 1 days ago [-]
I was interested for a few seconds, until I saw that it's a SaaS.
Sorry, but that's a no-go at this point.
adeelraza 1 days ago [-]
Fair :) We do have open-source pieces (Unlayer Elements, React Email Editor, AI Skills), but the hosted builder itself is commercial.
hokage-at-leaf 1 days ago [-]
Just went through open-source pieces. Looking good.
cyberax 1 days ago [-]
Just provide a downloadable version. Your server side should be just a glorified templating engine and a DB from consumers' point of view.
Charge for the local version, of course.
Rendered at 20:51:55 GMT+0000 (Coordinated Universal Time) with Vercel.
https://unlayer.com/pricing
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.
For instance, the usage of "Totally fair" and "The hard part", the usage of colons, which humans would use far less frequently, using the rule of threes (editable email, web page or document), etc.
Anyway, it's just lazy. This is someone trying to sell their product. They should be able to speak about it without using the exact response from an AI
"""
Totally fair. You can build the first 10-minute demo with an LLM now.
The hard part is usually what comes after. You need editable state, templates, and email-safe HTML. Then come export pipelines, custom blocks, permissions, and all the rendering edge cases that show up with real usage.
AI 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 made a deslopper[1] tool based on a new skill[2] I saw on twitter earlier. It's still a little smelly imo, but better.
---
[1] https://deslop.btst.workers.dev
[2] https://github.com/petergyang/no-ai-slop
This is what I got first time with a humanizer I built, still sounds terrible:
"Yeah, an LLM gets you the 10-minute demo now.
The expensive part is everything after, once real users depend on it. You end up maintaining editable state, templates, email-safe HTML, export pipelines, asset handling, permissions, custom blocks, and live previews. That takes months.
Structure makes AI output usable here, and it gets more important as the workflow gets automated. That's the idea behind Unlayer Elements. The LLM generates real editable components that map back into the actual email or page, and you keep editing what it makes like anything else in the tool.
I'd prototype with the LLM. I'd bring in Unlayer once that content layer becomes real infrastructure you don't want to own yourself."
""" Making a demo that does some things is easy. Making a demo that does all the things is hard.
We took a lot of time to make this product polished. We nailed down a lot of UX gotchas and a lot of bugs that come from poorly written back-end code.
If you don't need the polish, then a demo is more than sufficient. We built this for those who just want to ship, not fight with their agent about tech stack stuff. """
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.
Congrats on the launch - this looks like a genuinely useful tool. I look forward to checking it out.
If that's the first impression you're giving, you're underselling what looks like a legitimately useful product :(
But your landing page + video was just slop city. Removes 100% of credibility for me.
I know the advice is launch early and often, but honestly I would just point people to the github until you have something better.
Sorry, but that's a no-go at this point.
Charge for the local version, of course.