title: iOS recurring subscription policy for service, not content
body: <p>Apologies in advance for a policy, rather than a programming question, but given the paucity of information available online I hope I can be forgiven for asking it here.</p>
  
  <p>I would like to use the new recurring subscriptions from Apple in an iOS app. I have coded payments before and have no problems there, however nowhere can I find guidance on what is allowed under the new subscription type. The implication 'seems' to be that there is no special guidance, however all the discussions I can find are talking about 'content' providers rather than service providers.</p>
  
  <p>I would like to use the recurring subscription for a <strong>service</strong> that people subscribe to. I am not offering any content per se.</p>
  
  <p>Using the old non-renewing subscription type (that is really so broken it isn't worth using) I'm 99% sure the app would be accepted, but all the talk of content providers has me worried that Apple really don't want SAAS providers to use the recurring subscription model and want to restrict it to publishers of content.</p>
  
  <p>Does anyone have experience with using the new payment model for software as a service?</p>
  
  <p>I'd love to get some better idea as to whether it's viable or not before we build a whole payment solution around the concept!</p>