211–220 of 277 posts
Earlier quoted context omitted.
But the code populating and sending the email is rarely (ever?) Front end code
Sure, but presumably you want your emails to generally match the aesthetic of the rest of your product, which is easier if you can use the same tooling to make them as you do the frontend of your product.
I asked Adam to think about designing some reusable transactional email templates for Tailwind UI a few months ago. It looks like Resend would pair right up with Tailwind perfectly :)
I added Resend to my R&D to do list, and I hope to partner up soon: https://github.com/elegantframework/elegant-cli
Congratulations on the launch, and keep up the great work!
I saw that Guillermo also to note of your work, so props on that too!
Most email services assume that you are a big, US based company and care about following US anti spam laws, which require you to disclose your address in each email you send. As an Eu-based hobbyist running their services without registering an official business, I have no address that I can safely disclose and no willingness to deal with the legal system of a country that I have no interest in. What are your policies on this?
Anyway, re: the substance of your post--I've used a few email services for the handful of small web apps I develop. I'm currently on Postmark and I really like it. You state "Nobody is building an exceptional developer experience" and "There isn't a single developer-first email platform in the market today", and I have to disagree. Postmark has great developer experience. And the specific points you raise aren't much of a rebuttal:
- Templates: your own react.email project already has a Postmark integration. More generally, templating solutions don't need to be tied to the email service. I prefer to use separate libraries for rendering and then pass off the html output to the email service anyway.
- Slow performance: Postmark has excellent delivery speed.[1]
- Poor observability: Postmark (and every other service I've used) provides events.[2]
- Designed for marketers only: Postmark is clearly designed for developers, as are several other services.
I am rooting for you! But I'd also like to say that before you trash talk competitors, please be sure you have substance to back it up, because some of us actually like those competitors :).
FYI, the site is returning a 500 error currently. Anyway, re: the substance of your post--I've used a few email services for the handful of small web apps I develop. I'm currently on Postmark and I really like it. You state "Nobody is building an exceptional developer experience" and "There isn't a single developer-first email platform in the market today", and I have to disagree. Postmark has great developer experie…
This issue is only affecting the Marketing Website and Dashboard.
The Email API is up and running normally.
More updates here: https://resend-status.com
FYI, the site is returning a 500 error currently. Anyway, re: the substance of your post--I've used a few email services for the handful of small web apps I develop. I'm currently on Postmark and I really like it. You state "Nobody is building an exceptional developer experience" and "There isn't a single developer-first email platform in the market today", and I have to disagree. Postmark has great developer experie…
There’s an outage with our upstream provider (AWS Lambda): https://health.aws.amazon.com/health/status This issue is only affecting the Marketing Website and Dashboard. The Email API is up and running normally. More updates here: https://resend-status.com
That looks promising, I'm currently looking at Sendgrid and Mailgun. 2 points I would bring : - You need a cheaper plan. Mailgun have their flex plan that's 0$ for 1000 emails per month, and then 1$ for any extra 1000. It would cost more to send 50k emails, but I'm not there yet, I need a cheap starter plan with a lot less emails. My total infra cost is going to be around 30$, so I'm not going to drop an extra 66% to…
They were bought out by Private Equity a while ago so it looks like they are in the stage where the company's value is being extracted.
Earlier quoted context omitted.
I _think_ the idea is just to use React as a templating language to write HTML emails, rather than dealing with the quirks of email HTML directly; it's not about sending emails from the frontend.
But why use React to do that when you can achieve the same thing on the backend? https://mjml.io/
Earlier quoted context omitted.
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.
Maybe, but spaghetti jsx really sucks too.
Earlier quoted context omitted.
Sure, but presumably you want your emails to generally match the aesthetic of the rest of your product, which is easier if you can use the same tooling to make them as you do the frontend of your product.
React doesn't do its own styling though, and since email will not run js, you are basically talking about css at this point