关于应用内购买中的订阅问题
参加完在圣何塞举行的 iPhone 开发者大会后，我留下了比刚开始时更多的有关应用内购买的问题。这就是我想知道的：
您可以将购买设置为“订阅”类型。凉爽的。但是，它没有说明如何提供订阅服务 - 苹果如何知道每月收费一次？每周一次？每六个月一次？等等。有人告诉我，苹果并没有真正这样做——只是将其称为一种订阅类型。开发者必须是监控订阅的人，然后在到期时将它们提交给苹果 - 但这又引出了另一个问题 - 那么为什么要有订阅类型呢？如果我监控截止日期之前的天数，然后将其作为申请费用提交给苹果 - 与仅定期单独收费有什么区别？
在我看来，苹果在订阅上没有做任何事情 - 只是声明类型 - 所有工作都是由开发人员完成 - 在这种情况下，为什么称其为订阅？
有人可以向我指出一些处理应用程序订阅的代码吗？以及他们必须做什么才能将其设置为定期付款？非常感谢...
非常感谢。
和平。乔...
After attending an iPhone dev conf in San Jose - I left with more questions about In-App purchasing than when I started. Here's what I was wondering:
You can set a purchase as a type "subscription". cool. But, it doesn't say anywhere about how the subscription is serviced - how does apple know to charge once a month? once a week? one every six months? etc. I was told that apple doesn't really do that - only that it calls it a type of subscription. That the developer must be the one to monitor the subscriptions and then submit them to apple when they are due up - but this leads to another question - then why have the subscription type? If I monitor the days until it's due, then submit it to apple as an application charge - what's the difference in merely making separate charges on a regular basis?
it seems to me, apple is doing nothing on the subscriptions - only declaring the type - all the work is done by the developer - in which case, why call it a subscription?
Can someone point me to some code that handles a subscription for an app - and what they had to do to set this up for recurring payments? Would greatly appreciate it....
many thanx.
peace. JOe...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
iPhone SDK 中的订阅实际上是为了解决您无法出售虚拟积分的事实，因此您可以做的是出售订阅并在您的应用程序中免费提供数字内容（假设用户订阅了您的服务）正确的是你必须自己处理大部分逻辑
Subscriptions in the iPhone SDK really are to get around the fact that you cannot sell virtual credits, therefore what you can do is sell a subscription and make the digital content free from within your application assuming the user has a subscription to your service, you are correct in that you have to handle the majority of the logic yourself