blocks|key|1608403|text|鉴于robotmedia的图书馆您链接已经有7个月没有更新了(在撰写本报告时)，并明确指出它只支持V1和V2+of+GooglePlay+In-App+and，我建议使用目前运行在V3上的Google实现，原因很简单，因为更新周期比较明显。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1608404|V3+提高可用性使整个系统更易于与应用程序集成，因此，在可靠性方面，我认为您不太可能在更简单的实现中引入自己的bug。|1608405|有大量资源向您展示如何通过Google库设置和获取应用程序计费，并与Android协同工作。(RobotMedia本身也是他们的版本的教程)。|1608406|您可以阅读有关在应用程序计费中实现Google服务的相关内容。|1608407|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/robotmedia/AndroidBillingLibrary|1|http://developer.android.com/google/play/billing/index.html|2|http://developer.android.com/google/play/billing/api.html^0|1D|5|2I|2|D|3|0|2M|8|1|0|3|5|2|0|0|E|B|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@$9|12|A|13|1|14]|$9|15|A|16|1|17]]|E|$]]|$1|F|3|G|5|6|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|H|3|I|5|6|7|1C|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|L|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]|T|$5|O|P|Q|E|$R|U]]|V|$5|O|P|Q|E|$R|W]]]]

Given that robotmedia's <a href="https://github.com/robotmedia/AndroidBillingLibrary" rel="nofollow">library</a> you link to hasn't been updated for 7 months (At time of writing), and specifically states it only supports V1 and V2 of GooglePlay In-App Purchase, I would suggest the <a href="http://developer.android.com/google/play/billing/index.html" rel="nofollow">Google implementation</a> which currently runs on V3, simply because of the more apparent update cycle.

V3 <a href="http://developer.android.com/google/play/billing/api.html" rel="nofollow">improves the usability</a> making the whole system much easier to integrate with your application, so in terms of reliability I would put forward that you are less likely to introduce bugs of your own in a simpler implementation.

There are plenty of resources showing you how to set up and get In App Billing working with Android through the Google Play libraries. (RobotMedia also as a tutorial themselves for their version).

You can read about implementing Google Play Services In App Billing <a href="http://developer.android.com/google/play/billing/billing_integrate.html" rel="nofollow">here</a>.

blocks|key|1329457|text|我想还有更好的替代robotmedia或经典实现的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1329458|OpenIAB支持Google，亚马逊，SamsungApps，Yandex.Store，Appland，并基于谷歌v3+API。|offset|length|1329459|由于v3的原因，库存由Appstore管理，所以即使在崩溃或网络连接不良的情况下，您也不会丢失您的产品。|1329460|简单的一步一步如何正确的GitHub+https://github.com/onepf/OpenIAB的问题和答案也在GitHub上。|1329461|entityMap|0|LINK|mutability|MUTABLE|url|http://www.onepf.org/openiab|1|https://github.com/onepf/OpenIAB|2|https://github.com/onepf/OpenIAB/issues?direction=desc&sort=updated&state=open^0|0|0|7|0|0|0|J|W|1|1N|6|2|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]|$D|15|E|16|1|17]]|A|$]]|$1|J|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]|T|$5|M|N|O|A|$P|U]]]]

I guess there are better alternatives to robotmedia or classic implementation.

<a href="http://www.onepf.org/openiab" rel="nofollow">OpenIAB</a> supports Google Play, Amazon, SamsungApps, Yandex.Store, Appland and based on Google v3 API. 

Because of v3 inventory is managed by Appstore so you wouldn't lose your purchase even after crash or on poor internet connection

Simple step-by-step how-to is right on GitHub <a href="https://github.com/onepf/OpenIAB" rel="nofollow">https://github.com/onepf/OpenIAB</a> 
Questions and answers are also on <a href="https://github.com/onepf/OpenIAB/issues?direction=desc&amp;sort=updated&amp;state=open" rel="nofollow">GitHub</a>

blocks|key|609519|text|不是的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|609520|我写的，我不会用它作为一个新的应用程序。|609521|尽管如此，如果我必须为Android开发一个需要应用程序内计费的新应用程序，我可能会更新这个库。|609522|遗憾的是，我没有预见到这种情况会很快发生。|609523|无论您使用什么，请确保它是构建在版本3API之上的。|609524|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

No.

I wrote it and I wouldn't use it for a new app.

That said, if I had to develop a new app for Android that required in-app billing, I would probably update the library.

Sadly, I don't foresee this happening anytime soon.

Whatever you use make sure it's built on top of the version 3 API.

I have one, simple question: Is robotmedia's inAppBilling <a href="https://github.com/robotmedia/AndroidBillingLibrary" rel="nofollow">library</a> reliable and eligible to use, or would you rather suggest me classic inAppBilling <a href="http://developer.android.com/google/play/billing/index.html" rel="nofollow">imlementation</a>?

AndroidBillingLibrary's reliability

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个简单的问题:robotmedia的inAppBilling 是否可靠并有资格使用，还是您更愿意建议我使用经典的inAppBilling ？

问AndroidBillingLibrary的可靠性
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问AndroidBillingLibrary的可靠性EN