3 ms·

I love the concept of simple tech which does 1-2 things well, and have built some apps myself following a similar philosophy. However, there is always _some_ c

by hi_hi 2y ago

I love the concept of simple tech which does 1-2 things well, and have built some apps myself following a similar philosophy. However, there is always _some_ complexity when introducing a new solution. The simplest solution is generally what people already know and are comfortable with. With that in mind, what benefits does this provide over something like Slack or Discord for small teams? I get those aren't email, but I'd assume the protocol isn't the selling point? As someone who struggles to answer this question myself, I'm genuinely interested in hearing the process which led to this being created.

cade 2y ago
The short story is that Good Enough has put a handful of (hopefully) delightful things into the world: https://goodenough.us/ https://goodenough.us/ Putting things into the world means getting emails. Being a team means juggling said emails about things amongst several people. Enter the Shared Fastmail Account. "Oh! A new email. Click. Oh, this isn’t really for me. Mark as unread. Or did someone else already read this, mark as unread, and think it was for me? I guess I will go talk to..." And, you know, two dozen variations on that theme. It sucked as a way to work together. what benefits does this provide over something like Slack or Discord for small teams? We use Slack at Good Enough. It’s nifty. We even have a Jelly + Slack integration (and we use that too)! That said, the problem I described isn’t really solved by Slack. (Maybe Discord if you’re in a space that can funnel interactions there, but obviously there’s a lot of businesses who aren’t, and there’s a lot of drawbacks to using Discord as your only communication medium.) Email is still widely used and wildly useful. We think being able to collaborate on emails as a team, with clear expectations about who is handling what and visibility on all the back and forth, is really helpful. We’ve been using it to scratch our own itch from day one, and we suspect it will be of interest to others as well! Let me know if any of that didn’t make sense or you have any other questions.
- hi_hi 2y ago
  Thank you for the detailed reply. I now understand how this is specific to solving the problems of a shared email inbox. This isn't a problem I've had to deal with before, but indeed it appears to be a sufficiently painful problem to solve for. I wish you the best of luck, and continue the good fight to simplify.

by hi_hi 2y ago

cade 2y ago

The short story is that Good Enough has put a handful of (hopefully) delightful things into the world: https://goodenough.us/ https://goodenough.us/ Putting things into the world means getting emails. Being a team means juggling said emails about things amongst several people. Enter the Shared Fastmail Account. "Oh! A new email. Click. Oh, this isn’t really for me. Mark as unread. Or did someone else already read this, mark as unread, and think it was for me? I guess I will go talk to..." And, you know, two dozen variations on that theme. It sucked as a way to work together. what benefits does this provide over something like Slack or Discord for small teams? We use Slack at Good Enough. It’s nifty. We even have a Jelly + Slack integration (and we use that too)! That said, the problem I described isn’t really solved by Slack. (Maybe Discord if you’re in a space that can funnel interactions there, but obviously there’s a lot of businesses who aren’t, and there’s a lot of drawbacks to using Discord as your only communication medium.) Email is still widely used and wildly useful. We think being able to collaborate on emails as a team, with clear expectations about who is handling what and visibility on all the back and forth, is really helpful. We’ve been using it to scratch our own itch from day one, and we suspect it will be of interest to others as well! Let me know if any of that didn’t make sense or you have any other questions.

hi_hi 2y ago
Thank you for the detailed reply. I now understand how this is specific to solving the problems of a shared email inbox. This isn't a problem I've had to deal with before, but indeed it appears to be a sufficiently painful problem to solve for. I wish you the best of luck, and continue the good fight to simplify.