Certainly once calendars and contacts are done, and hopefully tasks as well, that will make a more complete ecosystem that is even more attractive than just the email component!
My first reaction as I have seen this standard popping up was not "my email will be faster/better", but "I will be able to setup a nice [email protected]" email address and have both email/web integration with it.
If developers start to embrace JMAP for a derivative usage, I think it could drive the adoption.
eg say I wanted to use jmap to implement some of hey's functionality -- for instance the screener that isolates and allows ban of new emails on first contact. Rather than a client, can I have a server that listens to my fastmail inbox and (potentially) moves emails as they're delivered?
Any chance you're thinking about allowing UI space for things like that?
Question: what do you think is the rough timing on Calendar/Sharing/Contacts/Tasks to be ratified? Within the next year, 2-years, etc?
All the other major email providers are selling their own proprietary services or only offering webmail clients.
They have no interest in implementing modern open specifications. They only support things like SMTP and IMAP for legacy reasons.
Why would either of these build a bridge over their lock-in moat?
I don’t see Outlook365 or Gmail (or even Apple for its iCloud email that has a relatively smaller user base) announcing any implementations of JMAP on their services. I don’t see smaller paid email service providers announce support for it. As it stands now, I don’t see a future for JMAP outside of Fastmail.
A popular client like Mozilla Thunderbird still hasn’t started implementing JMAP [1] and one of the reasons is because…the client and server documentation for JMAP haven’t been updated for a few years. [2]
So yeah, JMAP is like IMAP, but not really. We probably need a successor to JMAP that is liked enough to be implemented by email service providers and by email clients.
[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1322991
[2]: https://github.com/jmapio/jmap/issues/323