Faster with AI, quality kept.
Two things, for founders and CTOs of small teams with an app in production or in the making. I join your team to build and ship the app. And I set up an AI workflow fitted to your project, so your agents follow your conventions and your decisions rest on numbers. On Odisei Play we were two developers and a designer, shipping a release every two weeks.
Cross-platform app development, on your team.
I join your team and hold the React Native side. Architecture, code review, the features nobody wants to pick up, and the link with design. Over two and a half years in that job at Odisei Play. What breaks in BLE, in animation, or in the build, I have watched it break already.
- iOS, Android and web from one React Native codebase.
- BLE, Reanimated, video. In production, with real users.
- I led the monorepo migration: ten shared packages, a design token pipeline, a component library documented in Storybook.
A repo your agents can read.
There is a sentence in my case study: two developers cannot ship a product this size every two weeks unless the codebase itself is doing part of the work. When an agent makes a mess of a codebase, the model is rarely the problem. The repo you hand it is. That is what I come to fix. My work acts on your repo, not on your developers. I am not here to teach your team to prompt. I write the CLAUDE.md files, the rules layer, the skills and the hooks, so Claude Code, Codex or Cursor produce code that looks like yours. Is your app still in the making? The setup goes in from the first commit. And I don't start from scratch. It's the workflow I have used in production for more than two years.
- One CLAUDE.md per package. The agent loads the context of the module it works in, not the whole repo.
- Rules in one place. You change a convention once, every agent follows it.
- Skills and hooks written for your repo. What has to be checked before a commit gets checked without you.
- A weekly report that crosses PostHog and your database: what moves for your users, what breaks in the codebase, what to do next. At Odisei Play it crossed PostHog, RevenueCat and Supabase. The team used it to see whether its work moved retention and which bugs showed up, then decided what came next.
- Duration
- One to several weeks.
- You get
- The setup installed in your repo, with proof that every guard fires. And the weekly report crossing PostHog and your database, up and running.
- Price
- Fixed price, from €2,000, depending on the repo.
When I leave, the method stays.
How it works.
- Start
- We agree on a start date for your project.
- Rhythm
- Full-time or part-time, embedded in your team
- Where
- Full remote. Travel possible around Biarritz.
- Stack
- React Native, Expo, TypeScript, BLE, on-device AI
- First step
- You write to me, we get on a call, and it can be short. If I am not the right person, I will say so.
What they say.
What stands out most is how he approaches problems. Give him something hard and ambiguous, and he solves it, even when it takes extra effort. He is also an excellent teammate: he collaborates naturally and consistently found ways to help us ship faster. If you are looking for a talented, motivated engineer who sees both the technical detail and the bigger picture, Jean is your person. I would work with him again without hesitation.
Jean nous a intégré une app en React-Native avec Tailwind de manière très propre et très pro! Excellente communication, bonnes prises d'initiatives, et bon boulot 👍
Let’s talk about what you’re building.
Tell me what you are building and where it is stuck today. I read and answer myself.
Write to me