Re:Subscriptions and the new In-App Purchase requirement
by greyman on Tuesday February 22, 2011 @02:51AM
(#2249161)
I was also thinking about something similar. If users find your service on your website, you should encourage them to subscribe through it, no through in-app purchase. I think all app developers should educate people about that, so the number of in-app purchases will be as low as possible, so the apple cut of all sales will not be 30%, but less.
Re:Subscriptions and the new In-App Purchase requirement
by scrod on Tuesday February 22, 2011 @02:42AM
(#2249136)
Why ask them? Just price the Apple-payment-system version 30% higher than your own and let customers see the difference.
Re:Subscriptions and the new In-App Purchase requirement
by arn on Tuesday February 22, 2011 @02:46AM
(#2249148)
You can't do this. Apple states you must price it the same.
Re:Subscriptions and the new In-App Purchase requirement
by oscardelben on Tuesday February 22, 2011 @04:41AM
(#2249334)
Or lower.
Re:Subscriptions and the new In-App Purchase requirement
by scrod on Tuesday February 22, 2011 @01:22PM
(#2250889)
Oh, too bad then.
If I develop an enterprise ipad application and track down the customers myself, it is possible to sell to them and take 100% of the revenue still?
I can do this by offering the app for free on the app store and requiring activation through my own external signup system. However, I must also offer the option to sign up using Apple's API and Apple taking 30%?
I just need to be on the phone to the customer when they download the app and ask them politely to not use the Apple method?