Launch HN: Plum Mail (YC S20) – Email alternative for group conversations
Today we're launching Plum Mail in early access. You can join our Wait List to be one of the early users by emailing yesplease@plummail.co.
Email is disorganised, instant messaging is distracting and group chats are hard to keep track of. But email is great, because everyone has an email address. Why can’t we build an awesome messaging platform that lets us keep our email addresses? Our insight: keep the email address but replace the emails with something better.
The first thing we want to fix is group conversations. Conversations between three or more people in email get messy quickly. We can solve that with the ability to break off-topic messages out into sub-threads or the ability to conclude a thread. We’re working on the ability to highlight text and pin it to a noticeboard so important pieces of information don’t get lost in high message volume.
To help solve the issue of distraction created by platforms such as Slack, we’re introducing features like inbox delay, group chat message rate limits, and a complete lack of notification noises. Our design philosophy is respect and simplicity. We do not want to nudge you to check your inbox with things like red dots or read receipts.
We are also offering greater control over adding and removing people from conversation threads. Here’s a demo video showing some of this in action: https://www.youtube.com/watch?v=Yf-82ychDgA&t=6s
Peter and I started Plum Mail because we had these problems with email and IM ourselves. Group chats quickly get out of hand. We find it really hard to organise our annual ski trips with friends in Whatsapp. Half our mates just want to share hilarious GIFs that smother the conversation we’re trying to have about dates or hotels or ski hire. I love a funny GIF as much as the next guy so we probably just need to think about where the funny GIFs live and where the details about our hotel reservations live. i.e, not on top of each other.
We also have 12 months' experience working exclusively on passwordless authentication technologies in our company DID.app. We realised that the marriage of passwordless authentication with a common messaging platform could be a happy one.
Our vision for Plum Mail is to position it alongside other premium inbox products on the market to people that care about new features enabling them to have great quality conversations online. However, Plum Mail will remain open and accessible to all at some level so that users can enjoy the freedom of writing to anyone (whether they’re a user or not) whilst enjoying the clear benefits of messaging inside a common system instead of over email protocol.
We would love to hear your thoughts. In particular, what do you dislike about either email or instant messaging? Anything goes! This feels to us like an opportunity to re-imagine how communication online can work.
67 comments
[ 3.0 ms ] story [ 109 ms ] threadWas pulling my hair out trying to coordinate tasks in applying for a mortgage between me, my wife, the banker, the insurance company and the title people. I thought to myself it'd be great to have something like shared inbox but for personal use.
Would love to test this
When your main inbox is also your second factor of authentication for many services, your backup to your work accounts, and a repository of lots of financial and medical information, it's too scary to share with a cloud service. You could have 100% great intentions and still get hacked.
Messages within Plum Mail, are stored on our servers. Central coordination is what enables us to offer features like concluding a conversation and pins that show the same state to all participants.
It is a fair concern, one that always needs to be considered when using a cloud service, it is certainly possible to have the convenience of Plum Mail for some conversations and keep financial/medical sent directly to your email for peace of mind.
However this approach allows us to have features that would not be possible in just emails, but still have fallback interactions via emails to users not yet on the platform.
The people I know who don't use Slack yet are mostly older and mostly use Outlook. I think they'd be confused and irritating if we sent them emails with the frequency of chat.
Especially phone email notifications are not tuned to correctly handle instant messages.
I have often dreamed of a similar concept, but have never been able to work the UX out in my mind. Hopefully you have. Best of luck!
We're planning daily digest emails to group together multiple messages with individual reply buttons.
Showed it and explained it to my gran and she seemed to get it just fine. This is a woman that couldn't understand why her iPad wasn't charging until I explained it did actually need plugging into the wall. lol.
I think anyone would get confused and irritated by some weird confusion over email and Plum Mail. I think the next step is to ship v1 and see how users get on with it. I'll try to remember to report back what we learn.
Email is like one of the most common used identity, if not "the" most common used one, for web/cloud services. It's used as identity for roughly half of services in the wild, yet they don't put email/mail in their names, or emphasize that they are email alternatives.
You said emails are not the _core_ mechanism within the app. Maybe besides using them as identities, you also use emails for other, "non-core" way? Can you clarify on that? Maybe it's only me but it really confuses me that you emphasize email in such a way but only use them as identities.
We toyed with using the word 'messenger' but that's much less representative of the longform way in which Plum Mail nudges you to write. Messengers are synchronous, one liner, emojis etc.
At least with the word mail in the name, anyone hearing about it for the first time can have a pretty good guess at what it does. The technicality of using the email address as the identifier and passwordless authentication etc is important (but probably only really interesting to a technical audience).
Thoughts?
The format in Plum Mail is more longform rather than chat as such. Delta Chat is a cool service.
So you can stay within your email to take part in that conversation or you can access it in Plum Mail for the full feature set.
I've been thinking lately that the ability to send messages is perhaps the less interesting role of email. The real value comes from providing globally unique, federated identities. It's not perfect but it's pretty dang good.
If for no other reason, this is why Slack or any other closed system will never supplant email. Even the biggest walled gardens like GOOG and FB bow to the power of email identities in the end, as the preferred (maybe even only) way to recover an account.
We hope people will like being able to keep using their email address but get more features they are used to in other more modern platforms.
You're trying to fix the very thing I hate about email - It sucks when it involves more than a single entity, be it conversations, sharing stuff. It's only good when it's a single email (login, newsletter, etc).
* The features you're advertising are compelling! Pinning and conclusions are very interesting.
* As I read through this announcement, perused the website, and watched the demo on YouTube I was nearly driven to madness trying to understand how Plum Mail relates to email. It's not email, but it uses email addresses, has an inbox, and lets me email people. The cognitive dissonance I experienced reminded me of the old SNL sketch That's Not Yogurt[1]. If this truly isn't email, I suggest trying to be crisper about what why that's the case.
[1] https://www.nbc.com/saturday-night-live/video/thats-not-yogu...
We start by saying it's not email because it's easy to think plum mail is yet another email client, which it isn't.
plum mail hosts the conversations so it can manage the state of pinning, conclusions etc.
email addresses are just a user identifier it will email people if they are not on plum mail, so we don't require someone to be on plum mail for you to start talking to them.
Email as a protocol I suppose. On top of which some other protocol implemented to provide additional features.
Thanks for doing it.
Definitely agree that communication software can be improved.
Still, there’s a first time for everything and I hope the video can be succeeded by a V2 in fairly short order.
Thanks for your congratulations.
Regarding the video, may I suggest that you use the first 10-seconds as the “trailer” for the service. The trailer should cover the top-5 unique features —- your service’s USP —- and dive into each feature one by one for the rest of the video. This way, you’ve hooked users of all attention spans to view the rest of your video. This is similar to an executive summary, only in video form!
Good luck. I’ll sign up for an invite.
1. https://twitter.com/_adontai/status/1296512040442433538?s=21
Update: punctuation and minor clarification
Disclaimer: I work on it!
Free to all (system is open to all) with premium features for a modest fee.
- Will I be able to see who has notifications on or off?
- Relatedly, if someone has notifications off, is there way a way to notify them anyway?
Say for example during the branding discussion they've decided to use Pears instead of Plums, and they want to bring you back into the conversation to make sure that you won't veto that choice before they get too far along.
- If someone who is not on plummail signs up, will the conversations they were previously included in be in their inbox?
- You should put an invite link on the bottom of the fallback emails, or at least have it on by default and allow the sender to turn it off.
- When you added gary@example.co there didn't seem to be any validation. That's obviously not a valid address, so when/how would you be notified that the message failed? Would there be a way to fix the email and resend?
- When someone is added to the conversation I assume they get the full history? What if they're not plummail users? Is there any indication that you're sending to a non-plummail user so you know that they aren't seeing the whole context? Or a away to send them the full context?
- How do you get my inbound email? Do I forward it from gmail to you? Do you act as my MX recipient?
As of now you will not, but we have been asked this question by other users and are looking for feedback on the right way forward.
> Relatedly, if someone has notifications off, is there way a way to notify them anyway?
We want to introduce @mentions so that in larger group conversations you can highlight messages for a particular participant, this would notify that user even if they were not receiving notifications for every message.
> If someone who is not on plummail signs up, will the conversations they were previously included in be in their inbox?
Yes
> You should put an invite link on the bottom of the fallback emails
All fallback emails allow a user, new or otherwise, to immediately access that conversation on plum mail.
> so when/how would you be notified that the message failed? Would there be a way to fix the email and resend?
If we get a bounce back from an email address you will be able to see that in the conversation.
> When someone is added to the conversation I assume they get the full history?
Correct, if they are added to a conversation with history, they will be able to access the conversation from the fallback message this will give access to all previous messages.
> How do you get my inbound email? Do I forward it from gmail to you? Do you act as my MX recipient?
For now we don't handle inbound emails sent directly to your inbox. plum mail is the place for your group conversations that benefit from our unique features. We don't see much value in forwarding other transactional emails into plum mail. But we might look into it in the future.
Zulip and others can only be used within one team, we want to build a system that can be used for all conversations, hence the fallback emails sent to people not yet on plum mail.
We also are trying to choose features that encourage less frequent, more productive conversations, not be just another chat interface
Also, its trivial to have multiple teams on the same Zulip org, people are just subscribed to different sets of streams. So, say you have two teams: mobile and desktop, for example. You can have streams prefixed with that name:
#mobile-hangout #mobile-issues #mobile-support
OR
#m-hangout #m-issues #m-support
Good conventions for stream naming makes it really natural for multiple mostly isolated teams to exist on the same Zulip org, and share some streams like #announce, #general, etc that everyone is subscribed to.
The skimming you mention is the level of efficiency we are trying to get to. i.e. surfacing the key pieces of information.
I'll try to be really clear about what Plum Mail is and is not! We haven't done a great job of communicating this thus far.
Plum Mail is NOT an email client.
Plum Mail IS a communication platform using a central server similar to how an instant chat platform works.
Where we differ is that Plum Mail isn't a 'walled garden' where you need to invite users in to use it.
Users are identified in the system by their email address. If you write to someone that is not a Plum Mail user, then we send that message out as an email to that user with an option to reply. That reply button gives the user immediate access to Plum Mail in order to write back to you. We're doing this passwordlessly. Right at the genesis of this idea we didn't want to build a system that required you to invite all your friends to it before it became useful.
Revenue wise, referencing the above point, Plum Mail has to be free. We will offer premium features for a modest fee.
I'd like the same to be true for the quote. So much easier than writing 'I'll reply in line' and the copy/pasting all the time.