One Platform Foundation: AppDF and OpenIAB Overview
Hello!
Having visited YaC, I became interested in the OnePF project and, in order to deepen my knowledge of it, I went to Habr.
To my surprise, I found about him only one mention, and even then in passing.
Once such a thing, I decided to figure it out myself and share with the readers of Habr.
Any Android developer has probably heard about the “zoo” of Android devices, but not everyone pays attention that the same is happening with Android markets. Many do not notice this, because only Google Play is limited, but the guys from OnePF summed up the statistics , which shows that the lone share of application downloads is occupied by alternative Google Play-markets. Consequently, neglecting them, the developer misses the audience and benefits.
')
Of course, you can manually add your game to a particular market, but with a large number of markets with different requirements, this turns into a headache ...
It is this problem that the OnePF developers have tried to automate and solve.
One Platform Foundation is a project that develops standard mechanisms and tools for comfortable work with a variety of Android markets. At the moment, the project is being actively developed and already has two interesting solutions:
App Description File is a special file format containing a description, applications, screenshots, icons and, in fact, the application itself in the format of APK.
In fact, the .appdf file is a regular ZIP archive in which the description.xml file is located. It contains meta-information, as well as links to files in the archive.
The main section description.xml describes:
Full specification of the format posted on the link .
No need to write all this manually. On the OnePF website, you can find the convenient AppDF Editor tool, with which you can quickly prepare your application for publication.
Currently, AppDF already supports:
The following markets are also actively working on the implementation:
In general, a convenient tool for those who publish their application in a variety of markets.
The second project Open In-App Billing is a library allowing the developer to abstract from the In-App device of purchases of a specific market.
How the library works:
OpenIAB does not implement the logic of in-app purchases, it only proxies calls to the necessary market.
The project works with all the markets that support In-App purchases:
An example of working with all markets that currently support In-app purchases can be found here .
I think this library will help reduce the time to develop In-App purchases for each individual market. Moreover, the further they will be more and more.
Despite the fact that there are not so many supported systems, the project is actively developing and is aimed at the overall benefit, since the market will benefit from the standardization of these technologies.
Let's hope that the major market players will pay attention to him and will cooperate with him for the benefit of universal Android-happiness.
Developers want to achieve our plans and that did not work out .
Good luck!
Having visited YaC, I became interested in the OnePF project and, in order to deepen my knowledge of it, I went to Habr.
To my surprise, I found about him only one mention, and even then in passing.
Once such a thing, I decided to figure it out myself and share with the readers of Habr.
Any Android developer has probably heard about the “zoo” of Android devices, but not everyone pays attention that the same is happening with Android markets. Many do not notice this, because only Google Play is limited, but the guys from OnePF summed up the statistics , which shows that the lone share of application downloads is occupied by alternative Google Play-markets. Consequently, neglecting them, the developer misses the audience and benefits.
')
Of course, you can manually add your game to a particular market, but with a large number of markets with different requirements, this turns into a headache ...
It is this problem that the OnePF developers have tried to automate and solve.
One Platform Foundation is a project that develops standard mechanisms and tools for comfortable work with a variety of Android markets. At the moment, the project is being actively developed and already has two interesting solutions:
- AppDF is a standardized file format for universal loading of applications in the Android Store.
- OpenIAB is a library for transparent work with different In-App Billing systems.
AppDF
App Description File is a special file format containing a description, applications, screenshots, icons and, in fact, the application itself in the format of APK.
In fact, the .appdf file is a regular ZIP archive in which the description.xml file is located. It contains meta-information, as well as links to files in the archive.
The main section description.xml describes:
- Application Information
- Images
- Age requirement
- Price
- Regional settings
- Requirements
- Instructions for testing
- Market-specific data
Full specification of the format posted on the link .
No need to write all this manually. On the OnePF website, you can find the convenient AppDF Editor tool, with which you can quickly prepare your application for publication.
Currently, AppDF already supports:
The following markets are also actively working on the implementation:
In general, a convenient tool for those who publish their application in a variety of markets.
Openiab
The second project Open In-App Billing is a library allowing the developer to abstract from the In-App device of purchases of a specific market.
How the library works:
- The developer integrates the library into its program code.
- Writing client code to work with in-app purchases using an API very similar to the Google Play IAB API
- OpenIAB identifies the market from which the application was installed.
- The library redirects the request using the specific market IAB API.
OpenIAB does not implement the logic of in-app purchases, it only proxies calls to the necessary market.
The project works with all the markets that support In-App purchases:
- Google play
- Amazon AppStore
- Samsung apps
- SK-Telecom T-Store
An example of working with all markets that currently support In-app purchases can be found here .
I think this library will help reduce the time to develop In-App purchases for each individual market. Moreover, the further they will be more and more.
Results
Despite the fact that there are not so many supported systems, the project is actively developing and is aimed at the overall benefit, since the market will benefit from the standardization of these technologies.
Let's hope that the major market players will pay attention to him and will cooperate with him for the benefit of universal Android-happiness.
Developers want to achieve our plans and that did not work out .
Good luck!
useful links
Source: https://habr.com/ru/post/196378/
All Articles