Hi Roman, Thank you so much. 1) This is on the way. For a first version, this webapp actually wraps nicely in Cordova, and I intend to publish it in the App/P

Hi Roman, Thank you so much. 1) This is on the way. For a first version, this webapp actually wraps nicely in Cordova, and I intend to publish it in the App/Play stores. Alternatively, you will be able to install it as a PWA. Either way, you will be able to compose offline. I think it would also work well in Electron. 2) This is a bit tricky because Pony is more "email compatible" than it is email. Concretely, (i) Each message can only have one recipient. (ii) There is no subject line (iii) You send things by putting them in the Outbox and letting time pass. I've given it some thought and I think there are ways to smooth all this over and adapt it to IMAP, but I think the result might be clumsy. And there are "philosophical" considerations as well. Pony provides you with a non-instant space to communicate that is separate from the instant everything else. I think combining these two spaces would possibly take something away from the Pony experience? > The defining features of your service (daily collection / sending) By the way, while that is a feature, I don't think it's the defining feature. I think the defining feature is providing a space where people can correspond reflectively instead of reactively. When you've got an email client configured some way, you can always unconfigure it. With Pony, there is no way to make it non-instant. So unless you are rushing to make a pickup, there is reason you'd be rushing to hit send when you compose a message, or worried more messages might come and distract you. There are other apps that batch your email, but there are no apps that give you space and freedom to think like Pony.