I just read this story, and there is some missing analysis here that is wanting.
There is a simple reason why these "subscriptions" are rejected, and why Zinio, WSJ and Amazon Kindle apps sail right along.
Here's the deal. Apple allows app developers to use a "pay once" or "subscription" system using iTunes, where customers do not need to re-enter purchasing information. This type of application is NO PROBLEM for Apple. Approval all but guaranteed. Apple keeps 30% and developers keep 70% as usual. If you wish to take customer billing information, however... Apple REQUIRES that you NOT do it through the application itself, but on the Internet where Safari is tasked with handling the proper encryption and giving users the feedback that their information transaction is secure. WSJ allows people to login to their EXISTING subscription from their website or set-up elsewhere. To my knowledge, the WSJ iPad app DOES NOT request that you enter billing information through the app itself. Likewise, Zinio allows people to setup subscriptions OUTSIDE of the app itself.
Solution... give your app its own protocol, so that after billing through Safari on your website, customers can be directed back to your app without a hitch. Super-easy. Using cookies, you can even determine whether your app is even installed. Sure, its an extra step, but its not rocket-science.
I have a hardtime understanding why this seems so obtuse. It is also my understanding that Android Marketplace has the same requirement that apps DO NOT directly record critical credit card information directly. This is a basic security requirement in place to protect consumers from potential fraud and abuse in ways they simply cannot track or easily understand. Browsers have a very basic and easy and standard method of showing "secure" transactions and detecting "phishing" of information. Apps do not. So, no "in app" subscriptions or billing of ANY kind.
Times can get around Apple's rejection by simply sending users to its website to set-up a subscription, then allowing those users to access those services independently from the iPad. iTunes/AppStore are the ONLY applications able to take credit card info directly inside of the app (and use the same interface to do it).
All said... I need to research this more to be accurate, but this seems like the most basic message here. I feel like Times is trying to bully Apple into allowing it to do something no one else is doing, and that Apple (as usual) is not providing clear instruction to people. You'd think there'd be a developer relations manager for high-profile rejections or communication. Why do these people feel like they're "reaching out" and not getting anywhere? Are they lying? I know of at least one developer that got Apple to change its policy simply because they felt the restriction was boneheaded, and pretended to not understand Apple's requested change and resubmission. I don't think that reaction is uncommon.
~ CB
There is a simple reason why these "subscriptions" are rejected, and why Zinio, WSJ and Amazon Kindle apps sail right along.
Here's the deal. Apple allows app developers to use a "pay once" or "subscription" system using iTunes, where customers do not need to re-enter purchasing information. This type of application is NO PROBLEM for Apple. Approval all but guaranteed. Apple keeps 30% and developers keep 70% as usual. If you wish to take customer billing information, however... Apple REQUIRES that you NOT do it through the application itself, but on the Internet where Safari is tasked with handling the proper encryption and giving users the feedback that their information transaction is secure. WSJ allows people to login to their EXISTING subscription from their website or set-up elsewhere. To my knowledge, the WSJ iPad app DOES NOT request that you enter billing information through the app itself. Likewise, Zinio allows people to setup subscriptions OUTSIDE of the app itself.
Solution... give your app its own protocol, so that after billing through Safari on your website, customers can be directed back to your app without a hitch. Super-easy. Using cookies, you can even determine whether your app is even installed. Sure, its an extra step, but its not rocket-science.
I have a hardtime understanding why this seems so obtuse. It is also my understanding that Android Marketplace has the same requirement that apps DO NOT directly record critical credit card information directly. This is a basic security requirement in place to protect consumers from potential fraud and abuse in ways they simply cannot track or easily understand. Browsers have a very basic and easy and standard method of showing "secure" transactions and detecting "phishing" of information. Apps do not. So, no "in app" subscriptions or billing of ANY kind.
Times can get around Apple's rejection by simply sending users to its website to set-up a subscription, then allowing those users to access those services independently from the iPad. iTunes/AppStore are the ONLY applications able to take credit card info directly inside of the app (and use the same interface to do it).
All said... I need to research this more to be accurate, but this seems like the most basic message here. I feel like Times is trying to bully Apple into allowing it to do something no one else is doing, and that Apple (as usual) is not providing clear instruction to people. You'd think there'd be a developer relations manager for high-profile rejections or communication. Why do these people feel like they're "reaching out" and not getting anywhere? Are they lying? I know of at least one developer that got Apple to change its policy simply because they felt the restriction was boneheaded, and pretended to not understand Apple's requested change and resubmission. I don't think that reaction is uncommon.
~ CB







