I design and build mobile applications for iOS and Android — from the idea to the app being downloadable on the App Store and Google Play.
The whole thing, by one person: the app itself, the API and database it runs on, the deployment pipeline, and the store submissions — signing, certificates, review. A lot of React Native work stops at the build. Mine stops when it runs on someone's phone.
Freelance developer, based in Marseille, France. Fully remote. I work in French and English.
A social network for athletes. LinkedIn ignores performance, Instagram ignores the record — Kelenz puts both in one profile: sport, positions, season stats, trophies, club history, with a full social layer on top.
I'm a competitive athlete myself, and I had nowhere to exist online as one. So I built what was missing — designed, developed and shipped alone, on iOS, Android and the web.
App Store · Google Play · kelenz.com
Mobile — React Native, Expo, expo-router, TypeScript (strict, everywhere) API — NestJS, Node.js, PostgreSQL, Drizzle ORM, WebSocket, REST Shipping — App Store and Google Play submissions, signing, certificates, review, CI/CD Infrastructure — Railway, Neon, Cloudflare R2, GitHub Actions, Sentry, PostHog
I write React Native, and I go down into native when a project calls for it — a native module, an Xcode or Gradle build that won't cooperate, an SDK with no JS binding. If you need genuinely native Swift or Kotlin work, I'll tell you so rather than sell you cross-platform.
Kelenz is my product, and client work belongs to my clients. So there are no repositories to browse on this profile — the two store listings above are the artifact. I'd rather say that plainly than open three empty repos.
Building an app from scratch, taking over an existing one, or getting a React Native project all the way through release.
- Fully remote, France and international
- French and English, meetings included
- Epitech Grande École programme, MSc, 2020–2025 · 4 years of professional experience