Android SDK Migration Guide
Comparison¶
This section provides a comparison between different version of SDKs. This overview provides key insights for developers, identifying areas that have significant changes and need careful consideration.
Note
While there are multiple versions of our SDK available, please use the latest version of the SDKs rather than maintenance SDKs. Maintenance versions only provide support and will eventually be deprecated. The latest SDK adopts an aligned architecture, with no extra dependencies, and offers enhanced stability for optimal performance.
Feature |
Android Kotlin | Android Android |
|---|---|---|
| Package | com.amplitude:analytics-android | com.amplitude:android-sdk |
| SSL Pinning | TBD | Supported. Check here for the setup. |
| Configuration | Configuration is implemented by the configuration object. Configurations need to be passed into Amplitude Object during initialization. More configurations. | Support explicity setter methods. More configurations. |
| Logger provider | ConsoleLoggerProvider() by default. Fully customizable. | Amplitude Logger. Not customizable. |
| Storage Provider | InMemoryStorageProvider() by default. File storage. Fully customizable. | SQLite Database. |
| Customization | Plugins | Middelware |
| Server Endpoint | HTTP V2 API | HTTP V1 API |
| Batch API | Supported, with configuration. | Not supported. |
Data migration¶
Existing maintenance SDK data (events, user/device ID) can be moved to the latest SDK by setting migrateLegacyData to true in the Configuration. Learn more in Github.
amplitude = Amplitude(
Configuration(
...
migrateLegacyData = true,
)
)
Configuration configuration = new Configuration("AMPLITUDE_API_KEY", getApplicationContext());
configuration.setMigrateLegacyData(true);
Amplitude amplitude = new Amplitude(configuration);