There used to be a lot less expectation of post-sale maintenance of consumer software in the era where sales rather than subscriptions were the norm. There was also tolerance for higher up-front prices, and for much of that period sales depended on marketing through and validation by a narrow set of relatively trusted discovery channels, which customer the perceived risk to buyers. Now everything is untrusted, no one wants to pay much upfront but everyone expects ongoing support over they've got the thing. I’m not saying subscription is the only thing that works, but it's pretty easy to see that the calculus facing the average vendor has shifted tremendously over time.

It's a bunch of things. In the old days, if you bought software in a box for your OS (let's say DOS), you didn't expect it to need to be updated. It also continued to work just fine and maybe you didn't update your OS that frequently or had security issues to worry about. Nowadays, iOS gets updated every year and APIs get deprecated, and users update, so you have to maintain the app after initially shipping it.

A lot of people also expect the software to add features over time. In the old days, you'd ship a brand new major version and charge people for that and stop working on the old one. With the App Store, I suppose you could technically abandon the old version and sell a whole new version, but then all your old users will be annoyed if the app is removed from the store or no longer works when they update their OS. You could gate new features behind a paywall, and I know some apps do this, but then it adds to the complexity of the app as you have to worry about features that work for some users but not others.

I think people also expect software nowadays to be cheap or free, I think due to large corporations being able to fund free stuff (say gmail) by other means (say ads or tracking users). That means users would balk if you asked them to pay $50 for your little calendar app, so if you did ask for a one-time payment, it would be $5-$10, which is nowhere near enough to recoup whatever time you spent, unless you hit it big. Hitting it big nowadays with an app is difficult since there's so much competition in the App Stores and everyone has raced to the bottom to sell apps for pennies.

how many accounts do you have, my guy?

I cannot remember off the top of my head the exact number and am clearly too lazy to google it but there is a specific length of time in which, if no new noises pass through, the human brain processes it as a pause/silence.

I want to say 300ms which would coincide with your 500ms example

there are a lot of apps that do this though… eg. git tower. Sketch. Etc. Not saying that I like it or anything. Maybe its the combination of local first + an app that seems to be trivial (I am sure it was not but if you hear "daily planner" I think its reasonable to assume that its less complex than a git client and/or an app like Sketch).

I have a fully offline app and I offer the users two options (in addition of using a "basic" version for free)

- monthly subscription

- or pay one time fee of ~ 6-month subscription and own it forever

To be honest, in this case the subscription is cheaper for the average user, because most cancel in under six months.

One way of looking at is that subscription software helps align developer interests with dedicated users. It's easier to retain users than it is to get new users, so developers are incentivized to build features/make improvements for existing users to keep them as happy users. In a pay once upfront model developers are essentially only incentivized to build features that attract new users.