It’s not that is is a different ecosystem, it show shows how things can get bad very quickly. People like to say that they’ve the bridge that allows any generic IMAP/SMTP client to use their service, however what if they decide to disable the bridge? People talk a lot of shit about Microsoft and Google when it comes to email but at least those two provide email over standard protocols that can be used anywhere, not proprietary stuff. I wouldn’t be comfortable with having my email hostage to proprietary stuff like that.

No. Same BS as Proton.

The spreadsheet is very opinionated for eg. Proton fails in integration very hard because you can’t use it with a generic email client without extra steps… and in some platforms like iOS your only way to use it is by using their own app.

What do they offer?? An alternative to email that isn’t standard, not based in open and standard protocols like IMAP/SMPT at all and is incompatible with everything else out there that FYI is distributed. So this is basically another attempt at emulating Proton’s success and making email effetely less standardized. lol

📦 Zero Dependencies - Pure JavaScript, no build step required

This is really the best part. However the example does run a npm run build…

I would be great to have something that can be imported in a script tag like jquery and not something that requires npm and compilarion.