Bug and crash reporting tool Installed on 26M unique devices
Part of the team. Not just on the team.
How we embedded eight engineers into a global analytics company’s team, helped ship cross-platform features, improved release quality, and became a trusted part of delivery over three years.
SHORT
summary
Industry
User analytics
Location
France
Timeline
2023 – ongoing
Services
Cross-platform development
iOS development
Android development
Quality assurance
Technology
iOS — Swift
Android — Kotlin
Cross-platform — React Native, Flutter
A global customer experience company needed senior engineering capacity to support its mobile SDK across iOS, Android, React Native, Flutter, and webview integrations. We embedded directly into the client’s mobile organization and helped the team ship cross-platform features, improve testing, support customer integrations, and adapt to a new quality model without slowing delivery.
The challenge
The client’s mobile SDK spanned multiple platforms, including iOS, Android, React Native, Flutter, and webview integrations. Maintaining parity across that setup while continuing to ship required more senior engineering capacity than the client had in-house.
At the same time, the work itself was complex. Areas like the webview bridge required deep cross-platform understanding, and the client’s shift to a developer-owned quality model added further pressure on delivery and release processes.
The solution
We embedded eight engineers into the client’s mobile SDK setup and worked as part of the existing organization, not alongside it.
Our team contributed across key areas of the SDK: React Native development, Flutter support, iOS SDK work, Android SDK work, webview integration, and QA automation and developer support.
From day one, we joined the same planning, standups, technical discussions, and release processes as the client’s internal teams. We were part of weekly planning, day-to-day Slack communication, all-hands meetings, workshops, and offsites. Over time, the relationship felt less like an external engagement and more like one team delivering together.
Our impact
Cross-platform delivery support
We helped the client keep important SDK work moving across multiple platforms at once, including React Native, Flutter, iOS, Android, and webview-related functionality. We added senior capacity where it was needed most, without creating extra coordination overhead.
React Native error reporting
We developed the JavaScript error reporter for the React Native SDK from spec to production, adding an important capability to the client’s error analysis offering and taking ownership of a meaningful product area.
Webview integration in the unified SDK
We contributed to the webview layer of the client’s unified SDK, helping analytics continue across in-app web experiences. This supported one of the more technically demanding parts of the platform, where native and web tracking had to stay connected in the same session.
Support escalations resolved
We worked directly on engineer-to-engineer support. When implementation issues were escalated beyond first-line support, we joined calls with the client’s customers, diagnosed problems, and resolved the issues that reached us.
Release quality and automation
We worked directly on engineer-to-engineer support. When implementation issues were escalated beyond first-line support, we joined calls with the client’s customers, diagnosed problems, and resolved the issues that reached us.
Our tools
Jenkins
This is our go-to tool when it comes to CI/CD and build automation.
Babel
Javascript compiler that helps us develop more efficiently.
CocoaPods
We used this dependency manager on the native iOS side of the project.
Gradle
When it comes to tools that help devs develop faster, this one doesn’t disappoint.
TestRail
We use this tool to manage test cases and organize our testing.
NPM
Default package manager for the JavaScript runtime environment Node.js.
Outcome
Three years into the engagement, our team is still at the core of the project. But the clearest result is not just duration. It is trust.
We were brought into internal communication, feedback cycles, workshops, and off-sites alongside in-house staff. In day-to-day work, we’re treated as part of the team, not as a separate delivery layer on the outside. Over time, the boundary between internal and external contributors became easy to forget.
That is what made this engagement successful. We did not step in as extra hands. We embedded quickly, took ownership of complex parts of the product, supported delivery and quality at the same time, and became a reliable part of how the client’s mobile organization operated.
WANT A SOLUTION LIKE THIS ONE? — LET’S TALK
Just fill in the short form below, or skip to the bottom to arrange a chat directly with our client strategy specialist. Either way, we’ll be back in touch as soon as we can to arrange an informal call.
Don’t worry, any information you give us will only be stored for business purposes. Find out more in our Privacy Policy.
Arrange a chat with Ivor, our client strategy specialist.
More case studies
Metaswitch – a Microsoft companyCarrier-grade unified communication apps that support more than 1,000 service providers.