OP mentioned on Twitter that he chose iCloud Mail as the provider. How do You handle issues with losing incoming mails? Apple very often rejects mails from financial companies or ones that contain particular words and they won't report that to You. That's the only issue that keeps me from moving from own server.
Sadly, no. It also pushed me back from using their mail services (and far more complex issue where my @iCloud alias stopped working at all, but they fixed it after a few weeks).
I don't like the fact that you need an Apple device to sign up for iCloud+ and even to initially set up email. Still, I just switched over because it seems to be the best choice for my usecase.
Important note - custom domains for iCloud is a very limited feature:
- you can't send mails from more than 3 addresses per domain
- it doesn't support catch-all
Since I am in a time of moving to other city to study on university, I decided to abandon my mail server and migrate to iCloud... so now I am moving every of my service@domain.tld to prefix+service@domain.tld (tagging system that doesn't parse properly on some sites). It's no fun, but at least I'll take off my head caring whether my server is on fire, as it's now Apple's issue.
I am not the author of the comment, but I am 19 and only communication that I am doing through mail is related with support/feedback/employment. Also after I got a job as intern webdev (I don't even like it), we've been communicating via Slack. Also I saw that friends of mine have Discord/MS Teams/Telegram(!) as main communication service in companies.
So, I am also getting a few mails per day, and most of them are invoices, notifications that I don't need to see immediately, newsletters, etc.
I am building a macOS kanban board manager, as I am sick of Trello's lack of native app and lack of native, supported apps with a great set of features. I want it to be as easiest to migrate (both in and out) and the most extendable experience for a Mac user (I also consider features like plugins, but I guess Apple will throw my app out of the App Store with that feature release, so I'll do that when I'll reach some bigger audience via App Store).
I don't have any releases yet, because it's my first that huge app. Also I've never been digging that deep into AppKit framework, so I enjoy writing this, but I also see a lot of downsides where I know that in future I will have to rewrite a few of complex core components of AppKit on my own.
It's worth mentioning that app will operate on files (like Pages, Mindnode), not on the internal database, that would be hard to reach for an user that would like to open this file with some other apps (files are SQLite databases for now), like some SQLite manager.
