Dateio provides the SDK as a prebuilt binary library via SFTP for the bank to integrate into its mobile application. On Android, the bank downloads the AAR artifacts and adds them to its Maven Local repository. On iOS, the SDK is supplied as two XCFrameworks: DateioSDKiOS.xcframework and DateioSDKShared.xcframework. SDK updates are not fetched or applied automatically. Each SDK update must be integrated, tested and shipped as part of a new banking app release. Dateio's API is versioned to maintain backwards compatibility, so banks do not need to adopt every SDK release. Updates are recommended to benefit from new features, bug fixes and security improvements.
Coordinate the tech stack and exact versions with Dateio before downloading or integrating an SDK update. The bank chooses its library and build-tool versions and must notify Dateio of planned changes in advance.
Send detailed, up-to-date project information through the feasibility form or by e-mail. Include exact current and planned versions of relevant libraries and build tools, along with platform settings. Technology names alone, such as "Kotlin", are not sufficient. Update any previously shared information that is no longer current.
At the bank's request, Dateio aligns the SDK dependencies and verifies compatibility. Agree on the target versions and scope with Dateio before proceeding.
An update may be needed even if the bank does not need new SDK features. Changes to third-party libraries, supported operating systems or the bank's build environment can require a compatible SDK version, particularly on Android. On Android, examples include upgrades to Kotlin, Jetpack Compose, Android Gradle Plugin or the target Android API level. On iOS, changes to Xcode, the deployment target or shared dependencies may also require compatibility checks. Dependency updates may be necessary to address security vulnerabilities or platform requirements.
For compatibility-only updates that do not introduce new features, Dateio can typically deliver an updated SDK within a few days after the bank and Dateio have agreed on and approved the target versions and scope. The exact timeline depends on the scope of the changes and the required compatibility checks.
Dateio aims to schedule planned SDK and dependency upgrades around the bank's normal release windows, allowing time for integration and testing. Before a planned library upgrade or the addition of a new library, Dateio notifies the bank in advance to agree on the required steps and timeline. Please share planned platform or dependency upgrades and release dates early so compatibility and migration work can be coordinated.
Dateio: SDK development and testing, binary delivery, personalized migration instructions and integration support. Dateio explains the changes and agrees on the regression-test scope with the bank.
The bank: current tech-stack details and requirements, app integration, testing within the agreed scope, internal approvals, app-store submission and rollout to users.
SDK delivery and availability to end users are separate milestones.
The few-day turnaround for compatibility-only updates described above covers Dateio's SDK delivery after the target versions and scope have been agreed and approved; it does not include the bank's integration, regression testing, approvals, app-store review or rollout. For updates introducing new features or broader migration changes, Dateio and the bank agree on an estimate for the specific scope. The production date also depends on the bank's release window and these remaining steps, so there is no single end-to-end lead time for every update.
On the bank's side, plan for mobile development coverage for each affected platform, QA coverage for the relevant flows, and a release owner to coordinate approvals and rollout. These are responsibilities, not a fixed headcount: one person may cover multiple roles, or the bank may use separate teams. Dateio provides SDK development and integration support. The required capacity and effort should be agreed during planning based on the bank's integration and release process.
The changes needed in the bank's application depend on the SDK release and how the SDK is integrated. A compatibility-only update may require only dependency or build-configuration changes, with no changes to bank-owned screens. Breaking changes may affect SDK calls, configuration, callbacks or navigation, while new features may require changes to configuration, selected screens and user flows. Not every update changes SDK screens or user flows. When their appearance or behavior does change, this may not require changes to the bank's application code. Dateio communicates what changed in each release and, before implementation, works with the bank to identify the affected configuration, screens and integration points and agree on an appropriate regression-test scope based on those changes. Dateio documents the required changes in the personalized migration guide. The regression-test scope may be broader than the screens whose code changes.
Dateio may require an SDK update when the integrated version contains a significant defect that prevents normal use, or a high-severity or critical security vulnerability. In such cases, Dateio communicates the affected versions, required action and remediation timeline. An urgent fix may need to be released outside the bank's normal release window. Platform or app-store requirements may also make an update necessary to keep the banking app compatible. For mandatory updates, agree on the rollout plan with Dateio, including how users on affected app versions will receive the update.