Comments

Hacker News

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?

by axa27

Congrats on the launch! Elements seems really useful and practical, what's the response been from builders so far?

by edc88

The interesting part to me is the boundary you’re drawing around AI output: agents generating structured React components that can be reviewed, versioned, and later opened in a visual builder, rather than another unowned HTML blob.

A practical launch follow-up would be to look for live conversations from teams building AI-assisted invoice, proposal, report, or email workflows and getting stuck on that handoff from generation to editable production content. With the Unlayer positioning and ideal user as input, racoonn.me can surface those timely Reddit/X threads and produce reply drafts that address the stated implementation problem before mentioning the relevant builder or Elements workflow.

That is not a substitute for docs or examples around the component model. It is the discovery-and-first-response layer for finding people who are already trying to solve the exact problem you describe.

by hohoyaya43

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?

by Natalia724

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.

by Nazzareno

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

by orliesaurus

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.

by iAMkenough

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • 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?
  • Congrats on the launch! Elements seems really useful and practical, what's the response been from builders so far?
  • The interesting part to me is the boundary you’re drawing around AI output: agents generating structured React components that can be reviewed, versioned, and later opened in a visual builder, rather than another unowned HTML blob.

    A practical launch follow-up would be to look for live conversations from teams building AI-assisted invoice, proposal, report, or email workflows and getting stuck on that handoff from generation to editable production content. With the Unlayer positioning and ideal user as input, racoonn.me can surface those timely Reddit/X threads and produce reply drafts that address the stated implementation problem before mentioning the relevant builder or Elements workflow.

    That is not a substitute for docs or examples around the component model. It is the discovery-and-first-response layer for finding people who are already trying to solve the exact problem you describe.

  • 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?
  • 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.
  • 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
  • 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"

    https://unlayer.com/pricing

  • 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.