3 ms·
Although I truly think this is a fantastic product, both in the simplicity of the offering and the simplicity of the API, I was a little concerned about being a
by ollerac 9y ago
Although I truly think this is a fantastic product, both in the simplicity of the offering and the simplicity of the API, I was a little concerned about being able to use my own domain and phone number when sending messages, for the sake of building trust with my users. Also, I (selfishly, perhaps) have more faith in the reliability of an established service than something recently launched.
For anyone who has similar concerns and wants to use something more customizable and reliable like Mailgun/Twilio, but wants access to the same elegant API showcased here, you can use something like this (admittedly naive) implementation:
const mailgun = require('mailgun-js')({apiKey: api_key, domain: domain});
const twilio = new require('twilio')(accountSid, authToken);
export default function notify (to, msg, options) {
if (Array.isArray(to)) {
to.forEach((toSingle) => notify(toSingle, msg, options));
return;
}
if (to.includes("@")) {
mailgun.messages().send({
from: 'Your name <yourname@example.com>', // your email
to: to,
subject: options && options.subject,
text: msg
});
} else {
twilioClient.messages.create({
body: msg,
to: to,
from: '+5555555555' // your number
});
}
}
This implementation wouldn't require that much extra effort to set up initially (i.e. signing up for two API credentials instead of one and installing two packages instead of one), but it gives you a lot more flexibility to configure the from address and phone number and might help you sleep easier at night.
However, as a fellow startup founder, I think it's noble to support newer projects like this. As such, I've signed up for an account and plan to test it out for at least a month.
- kevsim 9y ago> Also, I (selfishly, perhaps) have more faith in the reliability of an established service than something recently launched. This was my thought as well. I've had a number of projects where I had to deliver large numbers of emails and SMS and the problem has never been the design of the API I used to send them. It's always about the delivery rates of those messages. Particularly with SMS we've had to be very careful with our providers, often needing to select a different one in different countries.
- igammarays 9y agoYeah, you are probably not the target market for this lovely hobby project. Email service reliability matters, and is a very difficult problem at scale. This is why my team has been working on a production-ready, enterprise version of a unified email API for about a year now, that's free for up to 100k messages/month, and has functionality that you couldn't easily build yourself, like auto-failover over multiple providers, full-text elasticsearch of your email history/logs, and a non-technical interface for your customer support team to easily view your recipients email history. Send me a tweet @flutemail if you're interested, I'll let you know when it's ready (should be in about a month).
- foxhop 9y agoCould you reach out to me? I'm in the market and would be able to beta test.
- igammarays 9y agoAwesome! Will do soon.
- josephxanderson 9y agoI would definitely like to be part of this as well. Not on Twitter so I can’t tweet you but if you could reach out to me I’d appreciate it.
- igammarays 9y agoAbsolutely. How can I reach you? Or just email isa at flutemail.com