| ▲ | orliesaurus 14 hours ago |
| 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 14 hours ago | parent | next [-] |
| 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 6 hours ago | parent [-] | | Really? You couldn't write this message yourself and had to ask an LLM. At least make it less obvious. | | |
| ▲ | all2 6 hours ago | parent [-] | | 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 6 hours ago | parent [-] | | 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 5 hours ago | parent [-] | | 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. --- [1] https://deslop.btst.workers.dev [2] https://github.com/petergyang/no-ai-slop | | |
| ▲ | jvwww 3 hours ago | parent | next [-] | | 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 4 hours ago | parent | prev [-] | | 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.
""" |
|
|
|
|
|
|
| ▲ | greenhat76 14 hours ago | parent | prev | next [-] |
| 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. |
| |
|
| ▲ | leftnode 12 hours ago | parent | prev [-] |
| 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. |
| |
