An Integrated SDK (Software Development Kit) is a common requirement when developing applications. It can help developers quickly implement complex functions, such as payment, map service, and data analysis. Here comes a practical guidance of SDK Integration.
An SDK is a set of tools and libraries to help developers quickly realize certain features or services. For example:
Payment SDK: used as integrating payment functions
Map SDK: akin to mapping and navigation services provided by Google Maps.
Ads SDK: such as advertising display and monetization provided by Google AdMob or Unity Ads.
Monetization SDK: developers can profit from the silent operation of Castar SDK on the app.
A standard SDK typically includes:
Core library files (such as .jar, .aar, .framework, etc.)
Development documentation
Sample code
Sign up for a Developer Account: most SDK publishers ask developers to register an account first.
Download the SDK File: Visit the publisher’s official website or developer’s platform to download the latest version of the SDK.
Obtain the necessary authentication information, like API Key, App ID, Client Secret and so on.
The development configuration is key to successfully integrating the SDK. Please make sure that the SDK file is properly integrated into the app and configure the demanded permissions or dependencies based on the documentation. For example:
Import SDK files: add the downloaded SDK files to the app or put em into use via tools.
Accesses to Configuration: add necessary permissions (as accessing the network and reading location data) to the app according to the functional requirements of the SDK to guarantee the normal use of the features.
Platform support: Please confirm that the SDK is compatible with your development platform and targeted device and adjust the app configuration asked by the documentation, just as the lowest version of supported system or specific framework requirements.
Initialization is an essential step in the process of integration. Through initialization, the SDK can identify your application by API Key or App ID and load its service configuration. Initialization is usually done when you start to use the app. During the initializing process, please carefully read the requirements for the settings referring to the documentation. For example, some SDKs may be asked to pass the test in the mode of debug to be enabled in a test environment while this feature needs to be shut down in the process of production. Please check if the background status is updated correspondingly along with the 100% accomplishment of the initialization.
Once the integration is completed, the functionality needs to be fully tested:
After the test is accomplished, please follow the steps below:
Check whether the SDK version is up to date.
Make sure the API Key put into use is of the official version during production.
Implement the publishing settings (such as setting an app signature or whitelist) in compliance with the publisher’s asks.
Check whether the API Key is correctly configured.
Make sure that the network is appropriately connected.
Confirm that the debugging logic is consistent with the documentation example.
Check for missing necessary permissions.
Ensure that the SDK supports the current operating system version and device’s framework.
For Android users, please make sure the minSdkVersion meets the SDK demands.
I hope this guidebook will be a great favor to you! If you have any questions, please feel free to contact us anytime. You can also use the integrated Castar SDK for test meanwhile, which not only easily verifies the results of integration, but also attains benefits during operation, thereby helping your application to quickly take the leap to profitability!