[andybak]

MacOS/iOS only without even a "coming soon on..." message.

I wouldn't bind myself to a mail client that tied me to a specific hardware vendor. Even if I was Apple only (which I'm not) I don't want to be in that position again.

[zwily]

If it’s just a client and not a service, why would you care?

[andybak]

Because switching a mail client that has a very specific workflow and set of features is a huge shift and you have to change a ton of habits and relearn muscle memory. It's worse than switching browsers because browsers don't embody as much workflow (and tend to be fairly similar to each other)

Been there with Google Inbox. I want one client that is going to stick around and works on all my devices.

[zwily]

I feel that with Inbox... still miss it. That said, if something comes along that is as good, I'll still switch back. (And maybe Big Mail will do that?)

[OJFord]

In general you might because of sinking the purchase cost, but in this case it's a subscription, so all I (not GP) can think of is the inertia and inconvenience of switching mail client if you only really wanted to switch (or add an) OS.

[smoldesu]

Same here. You're welcome to make a Mac-exclusive mail client, but you're gonna have a damn hard time making anyone care about it when only 7% of the active computer-using market is capable of installing your app...

[aldanor]

There's tons of brilliant native non-free Mac apps, so what?

Why would you need to make anyone outside of Mac/iOS world care about it in order for your app to succeed?

[smoldesu]

Love it or lump it, that's where the users are. Limiting your userbase inherently gimps the value proposition of your application, which is especially an issue when your program is something as simple as an email client.

[ilogik]

it's also an iOS client