Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Resend (YC W23) – Email API for developers using React

resend.com

Post reply on HN
Print view View original

101–110 of 277 posts

Re: Launch HN: Resend (YC W23) – Email API for developers using React

#102

Post by roflyear »

BowBun wrote: post #100
iamacyborg wrote: post #89

> Poor observability: Most tools keep you in the dark without knowing what really happened after you sent an email. Resend exposes all the events associated with your email via webhooks. I can't think of a single email platform I've used as an email marketer/crm marketer for a decade that didn't expose a full event stream for all emails.

Sendgrid doesn't log sent email bodies, as a simple example. Think harder!

Their webhook doesn't send the full body? I'm sure you at least get the data if not the exact data sent...

Re: Launch HN: Resend (YC W23) – Email API for developers using React

#103

Post by geekrax »

benatkin wrote: post #93

> We need to stop developing emails like it's 2010 and rethink how email can be done in 2023 and beyond. Do you have any awareness of how tacky this sounds?

Not sure if you are actually developing the emails or not, but from a front-end developer's perspective, I hate to touch my email templates codebase because it has to be coded in certain way that works with the email provider.

I cannot see what the end result is going to look like until I actually send out a test email and see it in my email clients. This DX indeed feels like 2010 if you compare it with today's DX for developing websites.

Re: Launch HN: Resend (YC W23) – Email API for developers using React

#104

Post by benatkin »

geekrax wrote: post #103
benatkin wrote: post #93

> We need to stop developing emails like it's 2010 and rethink how email can be done in 2023 and beyond. Do you have any awareness of how tacky this sounds?

Not sure if you are actually developing the emails or not, but from a front-end developer's perspective, I hate to touch my email templates codebase because it has to be coded in certain way that works with the email provider. I cannot see what the end result is going to look like until I actually send out a test email and see it in my email clients. This DX indeed feels like 2010 if you compare it with today's DX fo…

Yes, I am.

So this is like Litmus?

Re: Launch HN: Resend (YC W23) – Email API for developers using React

#105

Post by aj462 »

ctas wrote: post #70
geuis wrote: post #68

Which existing providers are you using on the backend for delivery? Mailgun, Sendgrid? I ask because it takes a long time to build up trust reputation among the major email providers to help ensure deliverability.

Looks like they're using AWS SES. From personal experience, none of them (SES, Mailgun, Sengrid) are suited for critical, transactional emails. I'm working in the same space and we're running our own backend.

@ctas since you're running your own backend, how did you solve the reputation problem to ensure good deliverability? I would have thought that using a dedicated IP on an existing provider like Sendgrid would be the best solution for critical transactional email.

Re: Launch HN: Resend (YC W23) – Email API for developers using React

#106

Post by joshmanders »

confoundcofound wrote: post #87
joshmanders wrote: post #83

Please for the love of god do not decide for me where I want to be. I signed up, confirmed my email, opened the app and was browsing through it and was on settings tab when I got a phone call. During that call I had to look up something so I opened a new tab. After the call I went back to resend's UI to watch it blink and all of the sudden I'm on the dashboard again. So I tested it, I went to the settings page again,…

Could you not find a million other ways to provide this feedback less abrasively? People like you unnecessarily exacerbate the stress of launching a new endeavor.

I'm sorry was I not asked to give feedback on a launch post? Did you not see this line:

> I would love to hear your ideas, experiences, and feedback on any and all of the above.

Re: Launch HN: Resend (YC W23) – Email API for developers using React

#107

Post by zenorocha »

perpil wrote: post #73

Watch your free tier very closely. An unfortunate part of being in the email business is that spammers and phishers are always looking for free ways to send their emails on ips with a good reputation. It quickly becomes a game of cat and mouse which detracts from the business, so make sure you have a effective strategy to prevent misuse when allowing customizable emails with a generous free tier.

Thanks a lot for the advice here. That's definitely an area where we spend a lot of time and one of the reasons why we've been under a private beta for the last six months.

Re: Launch HN: Resend (YC W23) – Email API for developers using React

#108

Post by zenorocha »

dazbradbury wrote: post #99

As soon as you support inbound email handling we'll definitely give it a go. Mailgun have some critical blockers (and potential security vulnerabilities) that have meant we're looking for an alternative to switch to ASAP. Ideally by then you'll have migration guides from every big provider and so it will be even easier! Thanks for innovating in this space - it's much needed!

Roger that.

Adding support for inbound emails is definitely on our roadmap.

Great idea on the migration guides!

Re: Launch HN: Resend (YC W23) – Email API for developers using React

#109

Post by satvikpendem »

geoffeg wrote: post #75
paxys wrote: post #16

Help me understand the React selling point. Existing email sending software supports text and HTML because that's what email is . No email client out there supports JavaScript, virtual DOMs, event loops, SSR or any such fancy web technology. Instead of hand-crafting an HTML template with etc I'm supposed to use your custom React components ( ...) which you will promptly compile down to the tags I mentioned above. So.…

I was in a meeting a while back where a team that was tasked with standing up a few dozen completely static websites was discussing what React components to use. I asked why they were using any front-end JS framework at all and not just creating static html sites, maybe using a generator like Hugo or Eleventy if they wanted to templatize. The answer was that they didn't know how to create plain html sites without JS.…

Because I want to write JS(X) instead of having to suffer through learning yet another templating DSL. I don't understand why this si so hard for people to understand, templating languages suck.
Post reply on HN