[sjroot]

This looks amazing. I am so glad that you kept it as close to the native Mail experience as possible.

My only question relates to payment. This is an app that I would gladly pay a solid price to own (in the ballpark of $50?). I would _much_ prefer that over a subscription model.

Because the site mentions eventual payment, but doesn't specify a pricing model, would you be willing to elaborate on your intentions?

[njhaveri]

Thanks! So, I don't know exactly what the pricing model will be yet, but I definitely hear your feedback on this topic, and I'm looking at pretty much every option :) My intention is to build a sustainable long-term business, and deliver a continuous/regular stream of updates (e.g. see the Release Notes at https://mimestream.com/releases), so the pricing model will need to support that goal.

[antaviana]

IMHO, if you are looking for long-term business, you need to go the subscription-only route. Probably $19/year.

Don't offer permanent licenses, it will add complexity to purchase and support. You do not want a users with a product of yours with a vulnerability they are not entitled to update.

A subscription-only model will allow you to focus on only the last build which everyone will be entitled to download, greatly simplifying your support.

You will be able to add features at your pace and will avoid the bloating that results when you compete with yourself as is the case with a permanent license model and (increasingly stupid) upgrades.

You will focus on quality not on corner case features to justify upgrades or interface revamps for the sake of it, confusing your existing user base. If you keep your quality high and the product is stable and reliable, your users will stick.

We have been selling our desktop product (in our case B2B) as subscription-only for 8 years and we couldn't be happier about the decision.

[bdcravens]

I agree with the idea of a subscription model, but $19/year is way too low.

[njhaveri]

Thanks for the feedback here, I really appreciate it! You make many solid points here, and some are totally new points I had not considered before.

[filoleg]

I think they can do a pricing model similar to what Sketch uses, but given it is an email client, I am not entirely sure of that myself (though still worth exploring).

For those unfamiliar, with Sketch, you basically have a yearly subscription and you continue receiving regular updates while you are subbed. Once your subscription expires, you get to keep the version you paid for at the beginning of your subscription period, but you stop receiving future updates (aside from security ones and such, ofc).

With Sketch it makes sense, because each year they add a cumulative of lots of new features and such, so people are motivated to renew the sub every year to get those features. With an email client, however, there isn't much in terms of "new features coming every year with updates" that people would be excited to pay the sub for on regular.

However, I still think it is worth exploring and considering as a viable possible option. With that model of "yearly sub, but you get to keep the old version once the sub expires", you allow people (who don't wanna deal with subs and just wanna use the barebones product to pay for once and forget) to experience your product and give you money. And powerusers and those who just want to support the project would be happy to pay the annual sub on regular and receive new features as they come. With that in mind, I would think a yearly $50-60 sub is pretty reasonable, but I am not an expert on pricing things like that, so take it with a grain of salt.

[dfinninger]

This is very similar to Intellij's perpetual fallback license. When you unsub, you are frozen on that point release.

I spent a while with a professional version until the community edition had some features that convinced me to move over.

[bdcravens]

I'm on board with the pricing model creating sustainability. Some guidance towards that point would be ideal, as I would be very frustrated if I invested in using a piece of software only to receive sticker shock and needing to throw that effort away. (Been burned by more than a few promising dev tools and services that did black box betas)

[rswail]

A possibility I just considered was a whitelabel option so that email vendors like Fastmail could offer it as part of their subscription... integrate to their contacts and calendars and let them to do the work of that, similar to how you're letting Google do the lifting on their side.

I pay for the following subscriptions/software as a tech user (I do some development, but most of my work is design and management):

* Fastmail business (I've got email in the archive back to 1998)

* Microsoft Office for Mac

* Dash

I see my subs as a monthly work/business cost, so I'd see Mimestream as "worth" somewhere around the $10/month price point. I'm just one data point though :)

The company I work with/for uses a combination of GSuite and things like Lucidchart/Confluence/JIRA, but that's their choice :)

[Gys]

I am not in the market for this, but would prefer a subscription model. Because a one time fee means the developer has to grow the sales constantly to keep receiving revenues. I think that gives the wrong motivation: adding features might be prefered to solving bugs. Or just stop working on it all together because the growth has stopped.