添加inApp功能——这需要多大的努力
我开发了一个应用程序，为某些设备提供分析功能。我正在考虑一种方法，其中基本版本仅允许有限的分析，并且可以通过 inApp 购买附加功能。最多 2 个应用内插件。
由于到目前为止我从未做过 inApp，所以我想问一下将 inApp 添加到完成的应用程序中需要付出多少努力，包括测试/设置测试购买等。假设可购买的插件结构已经准备好。
另外，当我们这样做时，在这些情况下（不是游戏！）inApp 的体验是什么（如果有的话）。假设完整版售价 70 美元，而最基本的版本售价 10 美元。是提供完整版本更好还是采用应用程序内方法更好？你的经验是什么？
非常感谢
I have developed an app which provides analysis functionality for certain devices. I am thinking about an approach where the basic version only allows limited analysis and one may buy additional functionality through inApp. At maximum 2 inApp addons.
Since I have never done inApp so far I would like to ask how much effort is it to add inApp including the testing/setting up test purchases etc to a finished app. Assuming that the purchasable addon structures are already prepared.
Also, while we are at it, what is the experience with inApp in these cases (not games!) if there is any. Let's say the full version would cost $70 while the most basic costs $10. Is it better to just offer the full version or do the inApp approach? What is your experience?
Many thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这是一个很难回答的问题，因为这在很大程度上取决于您拥有多少/什么样的体验，以及应用内体验的设计方式。我的经验是，这并不简单，StoreKit API 是使用起来不太直观的 API 之一，iTunes 配置和审批过程复杂且不直观，并且 测试是皮塔饼。
因此，大部分开销都在于让您了解一切如何工作以及如何测试。但实现 StoreKit API 的实际代码并不复杂，并且有一些 良好的样板代码，您可以使用它来开始。
由于困难的部分是第一次做，所以第二次做就会容易得多，尽管测试总是很痛苦。我会给自己一周的时间来第一次开发和测试它，并假设您会花一些时间来调整流程。
最后一件事 - 如果您决定 在您自己的服务器上验证商店收据，至少再假设几天来开发、集成和测试它。
This is a tough question to answer, because it depends a lot on how much/what kind of experience you have, and how the in-app experience is designed. My experience is that it's not trivial, the StoreKit API is one of the less intuitive to work with, the iTunes configuration and approval process is complicated and unintuitive, and testing is a PITA.
So most of the overhead is in getting your head around how everything works and how to test. But the actual code to implement the StoreKit API isn't complicated, and there's some good boilerplate code out there you can use to start with.
Since the tough part is doing it the first time, it's a lot easier the second time you do it, though testing is always a pain. I'd give yourself a solid week to develop and test it the first time, and assume you'll spend some time after that tweaking the flow.
One last thing--if you decide to verify store receipts on your own server, assume another few days at least to develop, integrate, and test that.