3 ms·
IMO the most important thing is to separate your email templates from your code base from the very beginning. Use a templating system from one of the external p
by brightball 6y ago
IMO the most important thing is to separate your email templates from your code base from the very beginning. Use a templating system from one of the external providers or something like SendWithUs.
Email is an afterthought that grows as your product grows. Untangling later becomes a big time sink.
- troygoode 6y agoIf you like SendWithUs (which the company has pivoted away from in favor of their new product, Dyspatch), I think you'd love the templating system we've built: https://www.courier.com https://www.courier.com
- brightball 6y agoI'll check it out, thanks! EDIT: After a quick look, I like what I see in general. The biggest suggestion that I would make and the part of SendWithUs that really appealed to me was the recipient focus of the interface. Being able to look to a specific user, see what had been sent to them, delivery status, resend it if necessary, etc. That was a very appealing and useful way to deal with the email logs from my perspective.
- troygoode 6y agoGreat feedback! We're starting to work on our recipient UI very soon. FYI you _can_ filter the logs page by recipient already, though that isn't as convenient for sure.