How Cross-Platform Mobile Engineering Works at CloudX
Steffan Chartrand
Hi, I'm Steffan Chartrand, and I'm a Member of Technical Staff focusing on mobile here at CloudX. When I joined the company last year, I thought of myself as an Android engineer. Today I still focus on Android, but I contribute across the entire stack. It's not just me: everyone on our team collaborates much more across language and operating system boundaries than we did in the past. We didn't intentionally set out to work this way, but it's been a natural consequence of agentic engineering, and I want to explain why.
At CloudX, our mobile engineers contribute across Android, iOS, and mobile plugin surfaces like React Native, Unity, and Flutter, while domain specialists review platform-specific work before it ships. AI makes this practical: it helps engineers build enough context to make well-scoped contributions outside their core expertise, including occasional changes in adjacent areas like backend, data, or web frontend.
The goal is not to erase platform expertise. It is to broaden context and keep SDK behavior aligned for publishers.
The Benefits of AI-enabled Collaboration
For SDK work, much of the core logic is shared conceptually: initialization, privacy, bidding, ad lifecycle, adapter orchestration, and telemetry. When engineers understand related implementations, they can spot unnecessary differences, port fixes faster, and design cleaner SDK and backend contracts.
Better code quality
- Fresh eyes catch bugs, edge cases, and anti-patterns that platform-specific tunnel vision can miss.
- Engineers bring patterns and lessons from one SDK into the other.
Shared component behavior
- Many SDK components are implemented nearly identically across Android and iOS.
- Once engineers understand the component behavior on one platform, they can often reason about the other platform much faster.
- Bugs are often mirrored across implementations, so a fix on one SDK can point directly to what to inspect on the other.
Broader shared context
- Cross-platform work spreads knowledge across Android and iOS instead of keeping context locked to one platform.
- Engineers who build a feature across both SDKs understand the full product behavior, not just one implementation.
Balanced workloads
- The team is less blocked by PTO, hiring imbalance, or platform-specific workload spikes.
- The team can respond to the highest-priority mobile work instead of being constrained by platform labels.
We've seen these effects beyond mobile, too, enough that our whole product and engineering team has adopted the title Member of Technical Staff to reflect that broader impact.
Cross-platform engineering, encouraged and enabled by AI, helps our team collaborate and share expertise. As a company, this means faster delivery, higher-quality SDKs, broader shared context, and more consistent behavior for publishers.