Changes between Version 11 and Version 12 of IABTransactionsDetector


Ignore:
Timestamp:
Jul 18, 2016, 8:12:26 AM (3 years ago)
Author:
gandrade
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IABTransactionsDetector

    v11 v12  
    99
    1010=== Project Description ===
    11    * Phase1: IAB code migration engine: create a Web page with two boxes and a button in the middle of them. The left box is an input box where the developer pastes the source code of it’s Android App with Google  IAB “calls”. After pressing  the button, the engine inserts the OpenIAB code in the right box. He then can copy that code to their IDE. [[BR]]
     11   * Phase 1: IAB code migration engine: create a Web page with two boxes and a button in the middle of them. The left box is an input box where the developer pastes the source code of it’s Android App with Google  IAB “calls”. After pressing  the button, the engine inserts the OpenIAB code in the right box. He then can copy that code to their IDE. [[BR]]
    1212
    1313   * Phase 2: Develop an import mechanism to import the SKUs (items bought inside the App) into our platform. The import mechanism an work in one of the following ways: 1) CSV exportation in Google Play backoffice and importation in Aptoide backoffice 2) API calls from Aptoide to Play to retrieve the existent SKUs 3) scraping of the Play backoffice with the Developer credentials.  The proof of concept consists in retrieving the SKUs in one of the ways.