Subscriptions and the new In-App Purchase requirement
marco.org
marco.org
Under the table deals would be extremely short sighted and dishonest.
I was thinking more along the lines of Amazon creating an open or liscensed API for it's ebooks, so that someone can make an app for me to log into and read books that I own. Users could still read their kindle books on their iphones, and amazon could keep it's position as the best book store for iOS users, expand to other devices, etc..
I don't think it is worth it for someone like Amazon or Pandora to stay off of Apple's platform just to give them less leverage, but I agree that they would have to be upfront about it.
And then every ISP will demand a cut of every sale that happens on the Internet part of their network. Finally, the telecos implement some good natural language processing and demand a cut of every sale you negotiate over their voice network...
...Their network, their rules...
... that will work well till the Oxygen cartel starts making demands....
> And then every ISP will demand a cut of every sale that
> happens on the Internet part of their network.
And then Apple will start collecting monthly fee just because you have iDevice.If this continues, in small steps, we'll be back at the old way, in which the content creator gets only a minimal share of the pie, and it's the distributors that get rich.
I'm all for an open, "flat", neutral infrastructure, so there is no way I'll be buying any Apple products.
Interesting. Do you mean it is more like a move to squeeze the last available dollar out of an existing business rather than a move to grow a business?
Clear heads will win this fight.
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?
You're thinking, "the performance of web apps doesn't at all compare to native apps," and you're (mostly) right. Web apps tend to feel a bit slower and less responsive. But if we can get one "hero" (i.e., popular web-only app) then people will learn to accept/ignore that the performance isn't quite the same as what they get when they download an app — and that would be good for the whole mobile web ecosystem.
And, of course, as mobile browsers (fairly quickly) advance, the performance will increase significantly and the difference will be less noticeable.
The problem is that by not making it a native app, you're cutting yourself off from "the way people get apps" for their devices. The app store is a distribution mechanism that just can't be ignored by a serious mobile developer.
I refuse to use any system where I can't get access to my data without a speed internet connection.
[1] “Our philosophy is simple—when Apple brings a new subscriber to the app, Apple earns a 30 percent share; when the publisher brings an existing or new subscriber to the app, the publisher keeps 100 percent and Apple earns nothing.”
That battle of interpretations rages on, unless I've heard different. It looks like Marco is taking the liberal interpretation (apps must accept IAP as a form of payment for any services they offer).
It seems to me this is the underlying debate.