2 ms·
> Target the largest customer base, so they get 30% of the biggest potential income. That means selling at a low price, because most customers will only pay low
by georgespencer 9y ago
> Target the largest customer base, so they get 30% of the biggest potential income. That means selling at a low price, because most customers will only pay low prices, and all customers prefer low prices. This teaches customers that software’s average value is low.
Can someone explain to me this logic? It seems faulty. Put it this way: if it were somehow possible to make more money as a developer in the App store, how would removing Apple's 30% cut make it more feasible? Apple and developers have a shared incentive to make as much money as possible, but developers control pricing and who they target. Apple is just along for the ride.
> Build a universal app (iPhone and iPad versions, in the same package) to increase the attractiveness and convenience of owning multiple iOS devices. You’ll earn a “+” in your app’s buy-button on the Store. This teaches customers that supporting multiple devices isn’t something to pay extra for.
This is better, and fairer, than the alternative. My iPad and my iPhone run the same operating system. Why should I pay twice for the same functionality across both of them? If Apple didn't do this people would be writing articles lamenting the fact that they want to make their 30% cut twice.
> Also include an Apple Watch version within the iPhone app. As above.
I would be happy to pay to unlock Apple Watch functionality in apps. I'm not sure that Apple prevents that from happening. But I agree with the author here provided the extra functionality is not simply "notifications" but something meaningful and unique to the watch's hardware.
> Provide regular updates, at no cost; so much so that there’s no mechanism for paid upgrades at all. This teaches customers that they should expect free upgrades for life, no matter how little they paid for the software initially.
There is a mechanism for a paid update, which is to simply state end of life for an app and release a new one (a la Tweetbot). Another way of looking at this is: Apple is encouraging developers to release new apps at full price once they feel that they have something new to launch, OR to use subscription pricing or quasi subscription pricing like Marco does with Overcast.
> Make exactly one sale of an app per person, ever, regardless of the number of devices they own, how often the app has been updated since they last used it, and so on. This also teaches customers that they’re entitled to come back to a free app at any point in the future, no matter how long ago they paid for it.
That seems fair to me as a consumer. If I bought something a year ago and want to re-install it, why shouldn't I? Wouldn't it seem unfair to not be able to use something I paid for?
> Ideally, make exactly one sale of an app per family. This reinforces the commodification of software; it’s to be shared around.
"Ideally" = Apple does not enforce this.
> Sell only through their store, with their distribution mechanism, their product page design and user flow, and their 30% cut — which doesn’t provide for marketing or discovery of any kind beyond searchability, and the very small chance of being featured in some way. The majority of customers probably have no idea that the price they pay for an app is almost 43% higher than the amount the developer will receive, before tax (i.e. that Apple takes 30% off the top).
Which has done more for the security and quality of the software which is available to consumers. (And that's also a reason affluent middle class folks flock to iOS.) And Apple allows search marketing and of course doesn't stop developers from marketing in Google, Bing, on TV, etc. which is where the majority of installs are driven for most app-centric startups I know.
- Ensorceled 9y agoYour reply sort of proves the point of the article ... > Put it this way: if it were somehow possible to make more money as a developer in the App store, how would removing Apple's 30% cut make it more feasible? 30% is a pretty hefty percentage. It's the weakest point in the article but imagine if I just cut your salary by 30%, is your job still worthwhile? > My iPad and my iPhone run the same operating system. Why should I pay twice for the same functionality across both of them? Except it's not the same functionality. Try Evernote for instance ... does it LOOK like the same functionality? That's a lot of developer effort you can't recoup. You've just diminished all that extra work to support both modalities with a wave of your hand. > That seems fair to me as a consumer. If I bought something a year ago and want to re-install it, why shouldn't I? Wouldn't it seem unfair to not be able to use something I paid for? That thing you paid for 5 years ago no longer exists, the software you bought 5 years ago can't even RUN on your new iPhone, what you are getting, for free, is the thing the developer made this year, with actual work, which looks like the thing you bought 5 years ago. > "Ideally" = Apple does not enforce [family sharing]. But they do encourage it. It's part of the diminishing effect. That you can opt out as a developer doesn't change that.
- georgespencer 9y ago> 30% is a pretty hefty percentage. It's the weakest point in the article but imagine if I just cut your salary by 30%, is your job still worthwhile? I'm unclear how this is a response to my response to OP. OP is saying that Apple forces developers to target the biggest possible audience by taking 30%. I'm arguing that Apple is agnostic and that if there's a way for developers to make more money in a niche then Apple is happy with that. And you can always price your software at +30%. > Except it's not the same functionality. Try Evernote for instance ... does it LOOK like the same functionality? That's a lot of developer effort you can't recoup. You've just diminished all that extra work to support both modalities with a wave of your hand. That's a distinction which isn't made in the article. Autolayout makes it trivial to support the same functionality across both devices. If you want to introduce new functionality with the iPad then have a separate app. I believe you're still entitled to do precisely that. > That thing you paid for 5 years ago no longer exists, the software you bought 5 years ago can't even RUN on your new iPhone, what you are getting, for free, is the thing the developer made this year, with actual work, which looks like the thing you bought 5 years ago. I don't understand this I'm afraid. If you're discussing the fact that apps sometimes need to be updated to keep running on the new versions of iOS then that's just part of the cost of business, but plenty of developers choose to not do this. Again, nobody is forcing developers to do this. Nobody is not buying your app because they think it might not be supported in five years time. > But they do encourage it. It's part of the diminishing effect. That you can opt out as a developer doesn't change that. It's only a diminishing effect on consumers if Apple encourages developers to do it and they do it. There's nothing forcing developers to do it. They're choosing to. They only have themselves to blame.