Hacker News new | ask | show | jobs
by wilshipley 2204 days ago
I responded to some of these in a different response, I’ll edit it a bit here, but my points are the same:

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.

Also, 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 just pay like a buck each and cancel after the first month, I’m not going to make my money back for the six years I’ve put into this app.

--

New stuff:

I’d argue that it’s much more important Apple let developers put out one-time-per-customer, timed, fully-functional demos.

Developers with successful products are already incentivized to keep updating them. What I’ve found again and again is that version two of a product will do better than version one.

Adobe’s been selling Photoshop since I was in college, and it’s not like they didn’t upgrade their app. Same with Intuit / Quicken.

-Wil

1 comments

I don’t want to hold my customers’ data for ransom and cut them off if they stop paying me my extortion money.

You don't have to, you could make it readonly when the subscription expires.

This would be what I’d aim for, absolutely.

I talked to some indies who do this for apps they sell outside the App Store, but none of them did it with App Store apps. I believe they indicated there were obstacles to doing it with the App Store (as it is). I’m definitely not an expert in this — I’ve never had a subscription app.

-Wil