What's New in Atomic's SDK: Smaller, Faster, and More Reliable Than Ever

A Better SDK from the Ground Up

Atomic's SDK is typically the first integration point between our platform and your app. Over the last several months, our engineering team has shipped major improvements focused on what matters most: smaller binaries, faster installs, clearer compatibility, more predictable behavior across iOS and Android, and better tooling around Uplink and specialized flows.

Here's a look at what's changed and what's coming next.

A Dramatically Smaller iOS Footprint

We rebuilt two core iOS components from the ground up. Muppet, our browser automation layer responsible for opening payroll and bank sites, detecting URL changes, and scraping elements, and Quantum, the wrapper that provides the in-app browser UI and authentication glue, were previously implemented in Kotlin Multiplatform and compiled for iOS. Both are now fully native Swift and Objective-C frameworks.

The impact on binary size has been significant:

• Before (Kotlin-based): The combined Quantum, Muppet, and Transact download size came in at roughly 13+ MB, with an effective footprint of approximately 10 MB of Atomic-specific code in a real production app.
• After (native iOS): The total frameworks download for the iOS SDK stack is approximately 2.5 MB, with the effective production footprint dropping to under 1 MB.

That's roughly a 10x reduction in the real binary footprint. For teams that care about App Store download size, update size on cellular connections, and overall binary bloat, this change removes a common source of internal pushback around SDK adoption.

Clear Kotlin Compatibility on Android

We now maintain two Android targets to ensure teams aren't blocked regardless of where they are on Kotlin migration:

• Kotlin 2.x is the modern, primary target that the SDK is built around.
• Kotlin 1.9 is explicitly supported on a legacy track for teams that haven't yet made the jump.

Previously, when we moved the SDK to Kotlin 2, teams still on 1.9 couldn't upgrade to newer Atomic SDK releases. That's no longer the case. Whether your team is on the latest Kotlin version or still planning the migration, there's a clear path forward with reduced upgrade friction.

Uplink: Now Cross-Platform

Uplink, our app for automation, demos, and operations, now has full feature parity on Android. The Uplink Android app is available in the Google Play Store and mirrors the iOS functionality: scan a QR code from the Uplink console, connect to the server, and run the same web automation flows.

For teams that need to evaluate Atomic without a full embedding effort, run Android-heavy operations, or simply want consistent workflows across both platforms, this is a meaningful step forward. Flows and automations can now be validated against real Android device fleets, not just iOS.

Real-Device Testing Across Platforms

Predictable, consistent behavior across iOS and Android is something our customers depend on. To raise the bar, we now run automated tests on real iOS and Android devices in AWS Device Farm. We request specific device and OS combinations, install an instrumented app with our SDK, and run scripted flows that mimic real usage, from host app through the Atomic SDK to Transact web, browser automation, and callbacks back into the host app.

Critically, we share the same test definitions across both platforms, so iOS and Android are validated against identical behavioral expectations. We're building a growing library of bank- and payroll-specific test flows that closely match real production traffic.

The result is fewer platform-specific regressions, fewer broken edge cases, and more predictable flows across device types and OS versions.

A Stronger Web-to-Native Contract

As part of the Muppet and Quantum refactor, we built a new cross-platform test suite that loads the same Transact JavaScript and Muppet JS the web app uses, then drives every possible call from web to native SDK. This verifies that iOS and Android both implement calls the same way and that new features added on one side are present and behave identically on the other.

For teams managing releases or QA, this means more stable SDK upgrades and far fewer "this worked on iOS but fails on Android" surprises. The integration surface between your app and our SDK is now much more strictly tested, with consistent, reliable behavior when reading callbacks and events from the SDK.

Better Transparency on SDK Changes

We've introduced automated release notes that feed into internal channels and a centralized changelog. When questions come up like "When did feature X land?" or "Which version contains the fix for Y?", our team now has a single source of truth and can respond with exact versions, dates, and any required migration notes.

This should make upgrading between SDK versions smoother and conversations about fix timelines more precise.

What's Ahead

We're continuing to invest in the SDK experience with several roadmap items worth highlighting:

Android Size Analysis — We've completed detailed footprint analysis on iOS via Sentry and are extending that work to Android. Soon we'll be able to provide measured data on the exact incremental size the SDK adds to your APK or AAB, giving your team hard numbers for internal performance and security reviews.

Ionic SDK — We're building Ionic support analogous to our existing React Native and Flutter SDKs. It's a thin JavaScript wrapper that talks to our native iOS and Android SDKs with no reimplementation of core logic. If your app is built in Ionic, you'll be able to integrate Atomic using familiar patterns instead of writing your own native bridges.

Deeper Uplink and Transact Integration — Directionally, we're moving toward using the same automation core that powers Uplink inside Transact itself. Improvements to automation resilience, speed, and error handling will benefit both Uplink and the Transact flows you rely on.

If you're evaluating, integrating, or upgrading Atomic's SDKs and want specific numbers on version comparisons, size impact, or fix timelines, we can now back those conversations with concrete data and release history. To learn more, reach out to your Client Success Manager or request a demo today.