As I added in the content section, I think that SaaS providers have the leeway to pass along the "Apple tax" to iOS users and thus embarrass Apple a little bit here. I'd like to see a service at least try to make an "iOS plan" - if a service is normally $10/mo, create a separate plan (that would be the only way of accessing the content for iOS users) that costs enough to offset Apple's take. This plan would cost the same both on the service provider's website and in the app, and would be the only way of accessing the service's content in the app, meeting Apple's rules... it would just be conspicuously more expensive than the version for all other platforms.
I'm not normally the self-promoting or blogging type, but since I'm an enthusiastic user of many of these iOS services (Rdio, Netflix, Audible, The Economist...), I expounded a little bit here: http://www.thetechbastard.com/post/3326771970/a-hypothetical...
That's an interesting way to get around Apple. I wonder if it will hold. You're basically saying that if you want iOS accessibility, you pay 43% more. So maybe WSJ has a newspaper version, a newspaper plus digital (including android, any non iOS device), and then a newspaper plus digital plus iOS plan.
Wonder if there's also another way to get around it, maybe by just jacking up the rate 43% everywhere to please Apple, but maybe giving some other type of promotion (loyalty points, coupons, free stuff) for people that don't use iOS. Maybe you could give 3 months free or something as a credit for anyone who doesn't use iOS?
Given the level of detail Apple has provided, it sounds like either option could work.
While the OP comes across as a tad hyperbolic, this is what I've thought for a long time: if a business is dependent on the good graces of the provider of a platform it's built on, it simply does not have a working model. It happened before with Facebook credits, and Apple making a similar move is no surprise to me.
"... they will need to give Apple 30% of their subscription revenue for all customers that want to access SalesForce via mobile."
Wow, a huge post based on this flawed understanding. It isn't 30% of every customer that accesses the mobile app, it's 30% of each client that signs up via the mobile app.
The rules are pretty simple. If you offer subscription service purchasing elsewhere, like your website, you also must offer it in your app via in-app purchase. If a person finds your service by installing the mobile app and then decides to sign up, using the now required in-app purchase ability, Apple gets 30%.
...and if your profit margin is close to that 30%, as it is with many businesses, you are now required (should you choose to develop an app for iOS) to sell your product to users whom you have to support and stand a very good chance of gaining nothing from.
In other words, such a business would be required to offer an option to hand off all of its profit to Apple, should it choose to offer a native iOS app. Apple gets a better experience for its customers, and the third party gets more customers it gets zero profit from. I can understand if such a business would find this unacceptable. (And look at it from a user's perspective: if given two options, one-click billing through Apple or time-consuming credit card entry through a web portal, which do you suppose the majority of users will take?)
So how exactly is that understanding flawed?
Edit: More details added, and some wording correction.
Wow, a huge post based on this flawed understanding.
That's about 80% of the entries from this blog that make it on the front page of HN. It's a great blog for gauging general developer perception and dissatisfaction, but that doesn't mean that the opinions expressed are actually true. (Signals all stations to prepare for downvotes.)
Apple is notorious for ripping businesses built on their platforms out from under the people that created them. It has happened with OS X by them taking a popular 3rd party utility/app and integrating the idea/look/feel directly with no attribution. It has happened with iOS, and now it is just coming to a point where Apple is flat out saying that if you make money on our platform, regardless if the value is outside of iOS, we want a cut if you want to be on it at all.
I think someone should directly ask them what their policy is on SaaS subscriptions, because you could easily make a case either way from the press release.
But I agree with the article, if Apple's intent is to get into the SaaS revenue stream, it's a major issue. I have clients who have been considering moving to platforms that include mobile apps on iOS devices, and that 30% Apple iTunes cut will get passed right on to them. Not to mention the hassle of having to create and manage purchases for individual iTunes accounts for each device.
HP has a great opportunity here to loudly announce that they are going to be SaaS friendly, and I think this could be the turning point on iOS's market share.
You can ask Apple what their policy on SaaS subscriptions is today, but it doesn't really matter. If Apple decides going after the SaaS revenue stream is in their interest, that policy will change tomorrow.
Apple does not demand 30% of out-of-app sales, just that out-of-app sales are not cheaper than in-app sales.
And as far as I read the release, SaaS is not concerned. Unless you're using Apples subscription mechanism, you're not offering a subscription in-app. So if you simply use a web API, that's not a subscription.
Can Apple change that at any time? Yes. Closed platforms take power from developers and give it to the platform vendor - in exchange for (often) a bigger pie to get your slice from.
Is the OP yet another pageview troll? Yes. Posting blatantly false information in the headline seems to indicate that.
>And as far as I read the release, SaaS is not concerned. Unless you're using Apples subscription mechanism, you're not offering a subscription in-app. So if you simply use a web API, that's not a subscription.
That's the point that you're missing. If you offer subscriptions or purchases out-of-app for use by the app, You are REQUIRED to offer subscriptions or purchases in-app as well for the same price and minus Apple's 30% cut.
Section 11.13 of the approval guidelines read:
"Apps can read or play approved content (magazines, newspapers, books, audio, music, video) that is sold outside of the app, for which Apple will not receive any portion of the revenues, provided that the same content is also offered in the app using IAP at the same price or less than it is offered outside the app. This applies to both purchased content and subscriptions."
So the whole question comes down to whether SAAS counts as a subscription, content, or otherwise.
Apple has suggested that if you offer subscriptions (or purchases) outside of your app that you need to do it inside your app. At the same price. Hence the whole drama over Kindle--the purchases are done on the Amazon website but Apple has stated they want 30%.
I'm starting to see a whole bunch of posts/comments about people reacting to losing 30% of their SaaS software revenue but no one seems to be calling out the Apple contract specifically lists content as defined as magazines, newspapers, books, audio, music, video. So I don't see where the SaaS angst is coming from.
Apple can charge 30% for apps and content because the ENTIRE product is being delivered on iOS. They can't charge that cut for SaaS because only a subset of the product is being delivered.
Could Apple attempt to take a cut from SaaS products if a user signed up from within your app IN THE FUTURE...sure, but I doubt they'd be stupid enough to try for 30%. Should Apple be compensated in some way for hosting/downloading your mobile app for your SaaS backend...maybe, and I'd be prepared to pay some commission if it drove signups, it might just be a tad lower than 30% though.
The argument in your last paragraph is almost exactly what everyone said about Apple's approach to subscriptions. "Apple would be crazy to demand 30% from publishers and distributors. Amazon can't afford 30%!"
Yet here we are today, wondering just how the hell everyone is going to carve 30% out of their business model. Anyone who thinks that task is anything even approaching trivial has never run a business.
affecting companies like Amazon, and companies like SalesForce that have made a significant investment iOS investment, one has to wonder whether building iPhone apps is safe
This. iOS remains, by the numbers, one of the worst places for freelance developers to spend their time. Profits are diminutive in the average case, and app store policies impose additional risks that have forced entire shops to leave the iOS ecosystem or change how they do business inside it.
If this is true, this will be a very unfair policy coming from Apple. This will be the divorce between web apps and iOS. I can see HP/Microsoft/Google/etc opening their doors to free SaaS.
Apple is getting greedy and capricious, and when this happens no good will come from it.
APIs for software services make this whole thing even more complicated. Some company has a web service offering which they charge $10/month for. They also have a web API, which allows 3rd-party developers to write apps for the service. Case (1): The services writes an iOS app to access their service. Case (2): A third party comes along and writes an iOS app for the service, using the service's API.
If it's true that in (1), they have to offer an IAP-way for users to purchase a subscription, what does that say about (2)? The third-party developer has no way of adding IAP to their app (it's not their company and the API doesn't expose such functionality).
Under these (more and more crazy sounding) rules, is (2) still required to pay the 30%? And given that it's impossible for (2) to have an IAP subscription option, maybe (2) isn't even allowed to exist? But if it is, then the service company could just pay 3rd-party developers to write apps for their service to add value for their subscribers without having to deal with the 30% stuff.
I'm confused by how far-reaching this is. Let's take Netflix: I currently subscribe to netflix via their website and consume it via multiple channels, including the iPad. What, if anything, is Apple asking netflix to do? It sounds like: provide a link in the app to subscribe to netflix, which must cost the same as signing up elsewhere, and pass 30% of the $18 a month to Apple.
The example of SalesForce in the article sounds wrong. Apple's 30% fee on subscriptions does not apply to ALL subscription revenue of a publisher, just to the subscriptions of users who found the publisher in the App Store. Quote: "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". If this is true, there is nothing unfair about it.
This assumes that every business model has a 30% margin they can give up to an "agent"; in this scenario, Apple. Many, many businesses operate on less than 30% margins.
Because of this, offering an iOS app becomes a loss leader. No, 100% of your user base will not sign up through iOS, but the 30% commission to Apple will dilute your margins on non-iOS sales. The net effect is that any company who operates a direct sales model will see a dilution of their margins, and must bet on the fact that in-app subscriptions will compensate for this in increased sales. There are many scenarios where this makes absolutely no sense.
The press release begins by referring to "publishers of content-based apps", and uses "publishers" throughout. I think it is pretty clear that they are not talking about SaaS.
The article also fails to understand that it is not taking cut of revenue from existing subscribers: only those that sign up through an iOS application.
I'm inclined to believe you as it regards Apple's policies as of today. As regards the future policies about non-content SaaS apps, suffice it to say that there is non-zero informational value in this announcement.
What would a "content-free" app look like? Aren't all apps, by definition, based on content?
I'm not meaning to be cute or trite -- I'm genuinely confused from the press release which category of apps will fall under these new rules. Which is why we'll need to wait for the legalese in the iOS developer terms to understand what this _really_ means.
Just 4-5 years ago most Telco's were building portals and walled gardens where they were licensing the content themselves (or even had teams creating it in house) and selling it in various ways to their customer base. So never mind a 30% cut, they were competing with content producers. If you were trying to sell content the Telco was hoping to sell forget a 30% cut, you couldn't even get on their platform and you earned a big fat $0.
If you really were lucky they'd decide to let you on but would take a 50/50 or 60/40 revenue share.
30% is starting to seem not so bad...compared to that at least.
I think they need to just offer a "iPhone connectivity" option for extra $$$. Then they need to offer that and only that via the appstore in app purchase on the phone.
I'm assuming that if you decide to sell your SaaS via the AppStore, you can't move your customer data outside of it should you choose to discontinue offering your AppStore interface?
So anyone who purchased a recurring subscription via the AppStore would be lost (would have to be prompted to re-purchase) should you leave the AppStore?
If so, then iOS definitely doesn't seem like a good investment for a SaaS business.
Sounds pretty similar to Apple's earlier attitude about 3rd party developers being parasites on 'their' platform. While (of course) they do own it, the 3rd Party developers are partners that add value, not parasites.
[+] [-] saturdaysaint|15 years ago|reply
I'm not normally the self-promoting or blogging type, but since I'm an enthusiastic user of many of these iOS services (Rdio, Netflix, Audible, The Economist...), I expounded a little bit here: http://www.thetechbastard.com/post/3326771970/a-hypothetical...
[+] [-] akashs|15 years ago|reply
Wonder if there's also another way to get around it, maybe by just jacking up the rate 43% everywhere to please Apple, but maybe giving some other type of promotion (loyalty points, coupons, free stuff) for people that don't use iOS. Maybe you could give 3 months free or something as a credit for anyone who doesn't use iOS?
Given the level of detail Apple has provided, it sounds like either option could work.
Edit: changed 30% to 43%
[+] [-] dazzla|15 years ago|reply
[+] [-] kbutler|15 years ago|reply
And why exactly would Apple choose to allow this?
[+] [-] mithaler|15 years ago|reply
[+] [-] scrrr|15 years ago|reply
[+] [-] YooLi|15 years ago|reply
Wow, a huge post based on this flawed understanding. It isn't 30% of every customer that accesses the mobile app, it's 30% of each client that signs up via the mobile app.
The rules are pretty simple. If you offer subscription service purchasing elsewhere, like your website, you also must offer it in your app via in-app purchase. If a person finds your service by installing the mobile app and then decides to sign up, using the now required in-app purchase ability, Apple gets 30%.
[+] [-] mithaler|15 years ago|reply
In other words, such a business would be required to offer an option to hand off all of its profit to Apple, should it choose to offer a native iOS app. Apple gets a better experience for its customers, and the third party gets more customers it gets zero profit from. I can understand if such a business would find this unacceptable. (And look at it from a user's perspective: if given two options, one-click billing through Apple or time-consuming credit card entry through a web portal, which do you suppose the majority of users will take?)
So how exactly is that understanding flawed?
Edit: More details added, and some wording correction.
[+] [-] stcredzero|15 years ago|reply
That's about 80% of the entries from this blog that make it on the front page of HN. It's a great blog for gauging general developer perception and dissatisfaction, but that doesn't mean that the opinions expressed are actually true. (Signals all stations to prepare for downvotes.)
[+] [-] chapel|15 years ago|reply
[+] [-] ghurlman|15 years ago|reply
Citation?
[+] [-] loewenskind|15 years ago|reply
[+] [-] russnewcomer|15 years ago|reply
I think someone should directly ask them what their policy is on SaaS subscriptions, because you could easily make a case either way from the press release.
But I agree with the article, if Apple's intent is to get into the SaaS revenue stream, it's a major issue. I have clients who have been considering moving to platforms that include mobile apps on iOS devices, and that 30% Apple iTunes cut will get passed right on to them. Not to mention the hassle of having to create and manage purchases for individual iTunes accounts for each device.
HP has a great opportunity here to loudly announce that they are going to be SaaS friendly, and I think this could be the turning point on iOS's market share.
[+] [-] towelrod|15 years ago|reply
Anyway, Apple clearly wants this to apply to XaaS, where X = anything and S = subscription. Or by this time next year, Xaa$.
[+] [-] fpgeek|15 years ago|reply
[+] [-] groby_b|15 years ago|reply
Apple does not demand 30% of out-of-app sales, just that out-of-app sales are not cheaper than in-app sales.
And as far as I read the release, SaaS is not concerned. Unless you're using Apples subscription mechanism, you're not offering a subscription in-app. So if you simply use a web API, that's not a subscription.
Can Apple change that at any time? Yes. Closed platforms take power from developers and give it to the platform vendor - in exchange for (often) a bigger pie to get your slice from.
Is the OP yet another pageview troll? Yes. Posting blatantly false information in the headline seems to indicate that.
[+] [-] allwein|15 years ago|reply
That's the point that you're missing. If you offer subscriptions or purchases out-of-app for use by the app, You are REQUIRED to offer subscriptions or purchases in-app as well for the same price and minus Apple's 30% cut.
Section 11.13 of the approval guidelines read: "Apps can read or play approved content (magazines, newspapers, books, audio, music, video) that is sold outside of the app, for which Apple will not receive any portion of the revenues, provided that the same content is also offered in the app using IAP at the same price or less than it is offered outside the app. This applies to both purchased content and subscriptions."
So the whole question comes down to whether SAAS counts as a subscription, content, or otherwise.
[+] [-] portman|15 years ago|reply
By this rule, all apps that offer subscriptions must additionally implement Apple's subscription mechanism.
This is what the OP (and everyone else) is reacting to.
[+] [-] jonknee|15 years ago|reply
[+] [-] lshepstone|15 years ago|reply
Apple can charge 30% for apps and content because the ENTIRE product is being delivered on iOS. They can't charge that cut for SaaS because only a subset of the product is being delivered.
Could Apple attempt to take a cut from SaaS products if a user signed up from within your app IN THE FUTURE...sure, but I doubt they'd be stupid enough to try for 30%. Should Apple be compensated in some way for hosting/downloading your mobile app for your SaaS backend...maybe, and I'd be prepared to pay some commission if it drove signups, it might just be a tad lower than 30% though.
[+] [-] bradleyland|15 years ago|reply
Yet here we are today, wondering just how the hell everyone is going to carve 30% out of their business model. Anyone who thinks that task is anything even approaching trivial has never run a business.
[+] [-] codingthewheel|15 years ago|reply
This. iOS remains, by the numbers, one of the worst places for freelance developers to spend their time. Profits are diminutive in the average case, and app store policies impose additional risks that have forced entire shops to leave the iOS ecosystem or change how they do business inside it.
[+] [-] phatbyte|15 years ago|reply
Apple is getting greedy and capricious, and when this happens no good will come from it.
[+] [-] vegashacker|15 years ago|reply
If it's true that in (1), they have to offer an IAP-way for users to purchase a subscription, what does that say about (2)? The third-party developer has no way of adding IAP to their app (it's not their company and the API doesn't expose such functionality).
Under these (more and more crazy sounding) rules, is (2) still required to pay the 30%? And given that it's impossible for (2) to have an IAP subscription option, maybe (2) isn't even allowed to exist? But if it is, then the service company could just pay 3rd-party developers to write apps for their service to add value for their subscribers without having to deal with the 30% stuff.
[+] [-] me_again|15 years ago|reply
[+] [-] bambax|15 years ago|reply
It's not technically always feasible, but most of the time it is.
[+] [-] eugmandel|15 years ago|reply
[+] [-] bradleyland|15 years ago|reply
Because of this, offering an iOS app becomes a loss leader. No, 100% of your user base will not sign up through iOS, but the 30% commission to Apple will dilute your margins on non-iOS sales. The net effect is that any company who operates a direct sales model will see a dilution of their margins, and must bet on the fact that in-app subscriptions will compensate for this in increased sales. There are many scenarios where this makes absolutely no sense.
[+] [-] callmeed|15 years ago|reply
I see a burgeoning new field: "reverse SEO" for SaaS mobile apps.
[+] [-] austintaylor|15 years ago|reply
The article also fails to understand that it is not taking cut of revenue from existing subscribers: only those that sign up through an iOS application.
[+] [-] patio11|15 years ago|reply
[+] [-] portman|15 years ago|reply
I'm not meaning to be cute or trite -- I'm genuinely confused from the press release which category of apps will fall under these new rules. Which is why we'll need to wait for the legalese in the iOS developer terms to understand what this _really_ means.
[+] [-] lshepstone|15 years ago|reply
If you really were lucky they'd decide to let you on but would take a 50/50 or 60/40 revenue share.
30% is starting to seem not so bad...compared to that at least.
[+] [-] gte910h|15 years ago|reply
[+] [-] rapind|15 years ago|reply
So anyone who purchased a recurring subscription via the AppStore would be lost (would have to be prompted to re-purchase) should you leave the AppStore?
If so, then iOS definitely doesn't seem like a good investment for a SaaS business.
[+] [-] profgarrett|15 years ago|reply
[+] [-] keeran|15 years ago|reply
If the SaaS provider isn't the supplier of the app, but they fully endorse (and promote) its use, does that create a loophole?