| The subscription model fails in a lot of ways, for everyone. For example, my next app is an interior design / home control app. How would the customer feel if they stopped paying and didn’t have access to their house any more? Most people would be pissed. I don’t want to hold my customers’ data for ransom and cut them off if they stop paying me my extortion money. I’m pretty sure we can do micro-subscription already — I could ask Apple to just charge $1 a month, that’s pretty micro. (I don’t think we can do pennies, yet.) But that model doesn’t really work for all types of apps. For instance, I estimate about half the people who buy version one of my app will enter their floorplan into their computer, place their furniture, be happy, and never use the app again (until I upgrade it to offer home control, as well). If those users had the option to just pay me 5 cents for the month they used the app, I’d have to get 16 million of these users to make back the money I’ve put into this app. That’s not really feasible. -— My point with the web is that pass-through web “apps” on iOS are the same as pass-through web “apps” on Android, so Apple is losing a competitive advantage if they kill of their native developers. If you’ve got Slack or Chrome or a banking app or a finance app or a health app on your iPhone, you could be running the exact same app on Android. So why did you spend extra on an iPhone? Apple needs to treat its independent, native developers better because we are the only ones who are making products that are Apple-only, and show off all the cool things iOS and macOS can do. -Wil |
That's a good point but really not "for everyone". Agreed that for a one shot app like this, pay once is the model that works. Although one could argue that you still held the customer data captive as soon as they get a new phone and the app is no longer compatible.