|
|
|
|
|
by MarceColl
3288 days ago
|
|
I don't see anything there that cannot be solved by a client. I only see a proprietary email service here, one that cannot be used with other existing solutions. Why not build this on top of the current email protocols and offer a good client for reading it and an easy way to setup a mailing list (with an easy way to browse the archives)? That way this could be used with other clients and existing mail bots. No need for another integration API or to install another bloated client.
If the user experience is really what sets this apart from mailing lists then you shouldn't have problems monetizing it. Also the point about > An email inbox is essentially just another list to manage. Twist is the same, but everyone already has an email account, why should I add yet another one? |
|