A.

Samsung Blockchain Platform SDK is a superset of SDKs. It focuses to offer a friendly blockchain solution especially for mobile developers. You can use Keystore SDK if you already have DApp development experience when you need a hardware wallet. But still, you may need a deeper knownledge to use it so that Platform SDK may be a better option for beginners. The main difference is the existence of network module. Samsung Blockchain Platform SDK is available to communicate with an external blockchain node providing a payment solution. Also Samsung Blockchain Platform SDK has Cucumber(web-based DApp browser which is built using Android WebView) so it is helpful to reduce costs to build your DApp for mobile environment.

A.

Samsung Blockchain SDK: The Blockchain DApp developer needs a simple payment solution, DApp without handset limitation, integrated with various cold wallets, and a legacy player who already has an experience with e-commerce (ex. Online shopping app). Especially it can be a better option for Web based DApp partners who has a plan to integrate the service into mobile environment.

Samsung Blockchain Keystore SDK: For DApp partners who needs a key storage to directly handle it.

A.

It supports Ethereum and TRON. You can see ERC20, ERC721 and TRC10, TRC20 item information when it follows the specification.

A.

No. Samsung Blockchain Platforms SDK doesn’t have any device or region dependency.

But, please note that it needs a cold wallet so that it follows the cold wallet’s restriction.

For example, you can use your DApp integrated with SDK on ANY device released by Samsung when you connect to external cold wallet. But if you use the Samsung KeyStore, it has to be same with the KeyStore’s restriction.

A.

You need an API key for getting a permission to access Keystore. Please refer Request for API key.

Note that, in case of integrating Ledger devices, you don't need this process.

A.

Add the following to your project's gradle.properties:

android.jetifier.blacklist=bcprov