IOS 6: Higher Hanging Fruit

Re:IOS 6: Higher Hanging Fruit by duiker101 on Saturday June 02, 2012 @09:32AM (#4058019)

Let's suppose you app uses an API, or whatever other thing that you do not have control over it. You make your app and release it. Then you make a paid upgrade. After some time, that thing your app rely on gets deprecated or changes. If you push an update to only people with the a paid upgrade you screw those who have not paid, leaving them with an non working app that they might have paid for. which sucks. But if you push a free update for everyone you will screw those who paid for the upgrade. which sucks.

So, what would you do?

[ Parent | on HN ]

Re:IOS 6: Higher Hanging Fruit by acdha on Saturday June 02, 2012 @06:13PM (#4059348)

Alternate strawman: you do not use paid upgrades and at some point stop making enough money to continue developing and supporting the app and the API. All of your users are screwed , too.

It's easy to envision hypothetical situations and they're all already possible, leaving customers stuck having to gauge how serious a company is and how sustainable their business model will be. Paid upgrades don't change this situation but do offer a currently blocked way for developers to make apps with a long-term plan

[ Parent | on HN ]

Re:IOS 6: Higher Hanging Fruit by glogla on Saturday June 02, 2012 @10:02AM (#4058072)

And if you are unscrupulous, planned obsolesce combines with paid upgrades really well.

[ Parent | on HN ]