01 / MISTRAL AI · NATIVE PLATFORM
Le Chat
Three months on Le Chat mobile during hypergrowth: native file-preview module, share intent, iOS widgets and an Android tile.
49PRs merged in 3 months
~60 %of the work in native
Seven senior React Native engineers, already used to working together. You talk directly to the people who write the code.
already in the repos of
One technical decision, one measurable product result.
01 / MISTRAL AI · NATIVE PLATFORM
Three months on Le Chat mobile during hypergrowth: native file-preview module, share intent, iOS widgets and an Android tile.
49PRs merged in 3 months
~60 %of the work in native
02 / SEPHORA · MULTI-COUNTRY MONOREPO
One monorepo, three apps for Europe and the Middle East. Each country gets its typed settings on launch, LTR and RTL alike.
60app variants, one repo
0per-country forks
03 / NACON · IOT + BLE
The companion app for a PlayStation controller: an offline-first TypeScript core on Expo and a full BLE stack, iOS and Android.
BLE ↔ RNtype-safe protocol
iOS + Androidone Expo codebase
One senior, a pair or a squad: the size follows the problem, and the format comes after the diagnosis.
01
Product and technical scoping, Expo / React Native architecture, design system, backend integrations, native modules when needed, CI/CD, App Store and Google Play, monitoring and handover.
02
Critical apps, crashes, slowness, unstable releases, prototypes that became products too fast, AI-generated apps. Short diagnosis, profiling, instrumentation, corrective PRs and a stabilisation plan.
03
Monorepo, design system, modularisation, TypeScript migration, Expo and New Architecture, CI/CD, technical governance, mentoring and handover.
04
Swift / Kotlin, BLE, camera, third-party SDKs, Android performance, lists, cold start, animations, store release, complex debugging, architecture audit or training.
Mount01 · week 0
Five days in your code. A written diagnosis, 3 pages max.
Ship02 · weeks 1 → N
PRs in your repo, a demo every week.
Unmount03 · end of mission
Runbooks and handover: your team carries on without us.
AI-native. We code with AI every day, framed by one senior and reviewed by another. See how we take over a vibe-coded app
100%senior engineers on your project
Any one of us can carry your mission. Nothing ships without another senior’s review.
★★★★★5/5 · 38 reviews on Malt and LinkedIn
Expo, Reanimated, Gesture Handler, Bottom Sheet… We contribute to the libraries you already use, and we publish our own.
Every repo of the collective carries it in its README: the code was reviewed by a senior.
The French-language React Native podcast hosted by David: Doctolib, Alan, Christopher Chedeau (co-creator of React Native)… All seven of us have been on it.
The normal questions to ask before letting an external team touch a production app.
A collective of seniors already used to working together. No middle layer between you and the engineers working in your codebase.
Yes. Rescue and scale missions are designed precisely for existing codebases: diagnosis, profiling, prioritisation, fixes and a long-term trajectory.
No. A mission can be carried by a single expert, a pair or a squad of two to four profiles. The size follows the problem.
Yes. Native modules, BLE, camera, third-party SDKs, performance, hardware integrations and platform issues are part of the interventions described on this page.
With a 30-minute conversation, then if the context calls for it, a short diagnosis of the repo and the metrics. Scope and format come after.
An app that crashes, a migration dragging on, a monorepo to structure, a stubborn native module or simply a product to launch fast. We’ll tell you what we would tackle first — and whether we’re the right fit.
Book the diagnosis